embrace

embrace.io

embrace declares 1 subprocessor in its subprocessor list, which we last checked on Oct 29, 2026 (evidence). It is Amazon Web Services. Our recent checks could not read the list; these entries are as of Oct 29, 2026.

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

1 third party.

NamePurposeLocationListed since
Amazon Web Services Cloud providerUnited States, European Union

Web TechnologiesCSV · Atom

embrace's homepage made 60 requests to 5 domains, and 2 services controlled by another company.

Advertising (1): usually detected as Advertising: Google CloudCookie compliance (1): CookieYes

2 third parties by category: Advertising 1Cookie compliance 1

Third parties 2 · 6 requests
Google Cloud gstatic.com, fonts.googleapis.com 7% of the page's requests 4
CookieYes CookieYes 3% of the page's requests 2
First party 1 · 54 requests
embrace Amazon CloudFront Amazon Web Services Cloudflare Google Font API HTTP/3 Max Mega Menu MySQL Open Graph PHP PWA Priority Hints RSS Unpkg WP Rocket 3.24 WordPress Yoast SEO 28.8 Yoast SEO Premium 20.9 jQuery 3.7.1 jsDelivr wpBakery 90% of the page's requests 54

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

ComplianceCSV · Atom

Certified
Says it complies with

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

Service statusCSV · Atom

Aug 15: no incident reportedAug 16: no incident reportedAug 17: no incident reportedAug 18: no incident reportedAug 19: no incident reportedAug 20: no incident reportedAug 21: no incident reportedAug 22: no incident reportedAug 23: no incident reportedAug 24: no incident reportedAug 25: no incident reportedAug 26: no incident reportedAug 27: no incident reportedAug 28: no incident reportedAug 29: no incident reportedAug 30: 1 incident (1 no impact stated)Aug 31: no incident reportedSep 1: no incident reportedSep 2: no incident reportedSep 3: no incident reportedSep 4: no incident reportedSep 5: no incident reportedSep 6: no incident reportedSep 7: no incident reportedSep 8: no incident reportedSep 9: no incident reportedSep 10: no incident reportedSep 11: no incident reportedSep 12: no incident reportedSep 13: no incident reportedSep 14: no incident reportedSep 15: no incident reportedSep 16: no incident reportedSep 17: no incident reportedSep 18: no incident reportedSep 19: no incident reportedSep 20: no incident reportedSep 21: no incident reportedSep 22: no incident reportedSep 23: no incident reportedSep 24: no incident reportedSep 25: no incident reportedSep 26: no incident reportedSep 27: no incident reportedSep 28: 1 incident (1 minor)Sep 29: no incident reportedSep 30: no incident reportedOct 1: no incident reportedOct 2: no incident reportedOct 3: no incident reportedOct 4: no incident reportedOct 5: no incident reportedOct 6: no incident reportedOct 7: no incident reportedOct 8: no incident reportedOct 9: no incident reportedOct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: no incident reportedOct 15: no incident reportedOct 16: no incident reportedOct 17: no incident reportedOct 18: no incident reportedOct 19: no incident reportedOct 20: no incident reportedOct 21: no incident reportedOct 22: no incident reportedOct 23: no incident reportedOct 24: no incident reportedOct 25: no incident reportedOct 26: no incident reportedOct 27: no incident reportedOct 28: 1 incident (1 no impact stated)Oct 29: no incident reportedOct 30: no incident reportedOct 31: no incident reportedNov 1: no incident reportedNov 2: no incident reportedNov 3: 1 incident (1 critical)Nov 4: 1 incident (1 critical)Nov 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

  • 5 incidents in 90 days
  • 2 major or critical
  • 2 h 37 min typical time to resolve
  • 14 min longest major
BeganIncidentImpactLasted
Span ingestion delay in the UScritical14 min
Span ingestion delay in the US regioncritical—
Delay in queries in the USno impact stated3 h 6 min
Span ingestion delay in the EU regionminor1 h 26 min
Timeouts accessing embrace.io marketing websiteno impact stated2 h 37 min
Delay in spans ingestionminor2 h 33 min
Some customers are experiencing timeouts while querying through the dashboard.minor1 h 55 min
Some customers are experiencing event ingest delaysno impact stated3 days

Incidents per month

0 2 4 Jun 2026: 2 incidents (2 no impact stated) · partial: our history begins Jun 12 · typical time to resolve 3 days Jul 2026: 2 incidents (2 minor) · typical time to resolve 2 h 33 min Aug 2026: 1 incident (1 no impact stated) · typical time to resolve 2 h 37 min Sep 2026: 1 incident (1 minor) · typical time to resolve 1 h 26 min Oct 2026: 1 incident (1 no impact stated) · typical time to resolve 3 h 6 min Nov 2026: 2 incidents (2 critical) · typical time to resolve 14 min Jun 2026Jul Aug Sep Oct Nov

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

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

ChangesCSV · Atom

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

None since tracking began.

Rating badge for embrace's site

embrace transparency rating

It updates with the rating.

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