Tracebit

tracebit.com

Tracebit declares 2 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They are Amazon Web Services and HubSpot. No published changes since we first read it on Nov 6, 2026.

Subprocessors CSV · Atom DORA draft CSV what's this? · 

2 third parties.

NamePurposeLocationListed since
Amazon Web Services Cloud provider
HubSpot Communication to users

Web TechnologiesCSV · Atom

Tracebit's homepage made 148 requests to 13 domains, and 6 services controlled by another company.

Advertising (2): Google Cloud, MicrosoftAnalytics (2): LinkedIn, UnifyCookie compliance (1): CookieYesOther (1): reviewed as Video players: Vimeo

6 third parties by category: Advertising 2Analytics 2Cookie compliance 1Other 1

Third parties 6 · 65 requests
Vimeo vimeocdn.com, vimeo.com 19% of the page's requests 28
Google Cloud DoubleClick Floodlight Google Analytics Google Tag Manager 11% of the page's requests 16
CookieYes CookieYes 7% of the page's requests 11
Microsoft Microsoft Advertising 3% of the page's requests 5
LinkedIn Linkedin Insight Tag 2% of the page's requests 3
Unify Unify 1% of the page's requests 2
First party 1 · 83 requests
Tracebit Amazon CloudFront Amazon S3 Amazon Web Services HSTS HTTP/3 Microsoft Clarity Open Graph Priority Hints RSS Vimeo Webflow 56% of the page's requests 83

6 tracked companies loaded by the homepage are not in Tracebit's subprocessor list. A website can use a service without it processing customer data.

ComplianceCSV · Atom

Certified

Certifications as Tracebit's trust center lists them; reports are usually shared on request (evidence)

Service statusCSV · Atom

Aug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: before our history of this status pageSep 28: before our history of this status pageSep 29: before our history of this status pageSep 30: before our history of this status pageOct 1: before our history of this status pageOct 2: before our history of this status pageOct 3: before our history of this status pageOct 4: before our history of this status pageOct 5: before our history of this status pageOct 6: before our history of this status pageOct 7: before our history of this status pageOct 8: before our history of this status pageOct 9: before our history of this status pageOct 10: before our history of this status pageOct 11: before our history of this status pageOct 12: before our history of this status pageOct 13: before our history of this status pageOct 14: before our history of this status pageOct 15: before our history of this status pageOct 16: before our history of this status pageOct 17: before our history of this status pageOct 18: before our history of this status pageOct 19: before our history of this status pageOct 20: before our history of this status pageOct 21: before our history of this status pageOct 22: before our history of this status pageOct 23: before our history of this status pageOct 24: before our history of this status pageOct 25: before our history of this status pageOct 26: before our history of this status pageOct 27: before our history of this status pageOct 28: before our history of this status pageOct 29: before our history of this status pageOct 30: before our history of this status pageOct 31: before our history of this status pageNov 1: before our history of this status pageNov 2: before our history of this status pageNov 3: 1 incident (1 minor)Nov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reported

90 days agotoday

  • 1 incident in 9 days
  • 0 major or critical
  • 27 h 22 min typical time to resolve
BeganIncidentImpactLasted
Tracebit docs site is currently unavailableminor27 h 22 min

Incidents per month

0 2 4 Sep 2026: 0 incidents · before our history of this status page Oct 2026: 0 incidents · before our history of this status page Nov 2026: 1 incident (1 minor) · partial: our history begins Nov 3 · typical time to resolve 27 h 22 min Sep 2026Oct Nov

critical major minor no impact stated before or partly before our history

As Tracebit's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Incidents reported by Tracebit's subprocessorsCSV · Atom

4 reported incidents in the last 30 days, by 1 of the vendors Tracebit lists as a subprocessor.

A subprocessor list names a company, not the service an incident touched. This does not show that Tracebit was involved.

DateCompanyIncidentImpactLasted
HubSpotSome HubSpot tools may be unavailable for some users no impact stated51 min
HubSpotHubSpot is experiencing issues no impact stated22 min
HubSpotSome HubSpot tools may be unavailable for some users no impact stated2 h 47 min
HubSpotUpdate on PHP security vulnerability no impact stated1 h 53 min

Who is around them.

ChangesCSV · Atom

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for Tracebit's site

Tracebit transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/tracebit"><img src="https://thirdpartyindex.com/badge/tracebit.svg" alt="Tracebit transparency rating on Third Party Index" height="20"></a>
[![Tracebit transparency rating on Third Party Index](https://thirdpartyindex.com/badge/tracebit.svg)](https://thirdpartyindex.com/vendors/tracebit)