Chronosphere

chronosphere.io

Chronosphere declares 5 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They include Google Cloud, Slack and Zendesk. No published changes since we first read it on Sep 22, 2026. 3 tracked vendors name Chronosphere as a subprocessor, including xAI, Klaviyo and Nightfall.

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

5 third parties.

NamePurposeLocationListed since
FullStory Anonymous usage analyticsUnited States
Google, LLC. Cloud service provider, Cognitive servicesUnited States, European Union
Shortcut Internal support collaborationUnited States
Slack Technologies, Inc. Communication servicesUnited States
Zendesk, Inc. Support ticketing and customer serviceUnited States

Web TechnologiesCSV · Atom

Chronosphere's homepage made 44 requests to 4 domains, and 2 services controlled by another company.

Advertising (1): usually detected as Advertising: Google CloudOther (1): Caching: NitroPack

2 third parties by category: Advertising 1Other 1

Third parties 2 · 42 requests
NitroPack NitroPack 84% of the page's requests 37
Google Cloudsubprocessor gstatic.com 11% of the page's requests 5
First party 1 · 2 requests
Chronosphere Cloudflare Google Font API HTTP/3 LazySizes MySQL Open Graph PHP Priority Hints WP Engine WordPress Yoast SEO 5% of the page's requests 2

Subprocessor of (3)CSV · Atom

3 companies
  • Klaviyo klaviyo.com Data Analysis
  • Nightfall nightfall.ai Chronosphere is a cloud based managed observability platform, providing metrics, logs, distributed tracing, monitoring and alerting functionality used to monitor and maintain the Nightfall platform.
  • xAI x.ai Services and support

ComplianceCSV · Atom

Certified
Says it complies with

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

90 days agotoday

  • 290 incidents in 90 days
  • 3 major or critical
  • 2 h 21 min typical time to resolve
  • 17 h 51 min longest major
BeganIncidentImpactLasted
WildFire Australia Cloud Service Scheduled Maintenanceno impact stated1 h 6 min
WildFire South Korea Cloud Service Scheduled Maintenanceno impact stated1 h 1 min
WildFire India Cloud Service Scheduled Maintenanceno impact stated1 h 5 min
WildFire Saudi Arabia Cloud Service Scheduled Maintenanceno impact stated1 h 3 min
WildFire UK Cloud Service Scheduled Maintenanceno impact stated1 h 5 min
WildFire Singapore Cloud Service Scheduled Maintenanceno impact stated1 h 4 min
WildFire Delhi Cloud Service Scheduled Maintenanceno impact stated1 h 3 min
WildFire Taiwan Cloud Service Scheduled Maintenanceno impact stated1 h 7 min

Incidents per month

0 80 160 Dec 2025: 13 incidents (1 critical, 1 major, 7 minor, 4 no impact stated) · typical time to resolve 2 h 55 min Jan 2026: 8 incidents (3 major, 4 minor, 1 no impact stated) · typical time to resolve 4 h 1 min Feb 2026: 15 incidents (1 critical, 6 major, 6 minor, 2 no impact stated) · typical time to resolve 2 h 33 min Mar 2026: 23 incidents (2 critical, 4 major, 11 minor, 6 no impact stated) · typical time to resolve 6 h 21 min Apr 2026: 10 incidents (1 critical, 1 major, 7 minor, 1 no impact stated) · typical time to resolve 4 h 57 min May 2026: 12 incidents (1 critical, 3 major, 6 minor, 2 no impact stated) · typical time to resolve 4 h 5 min Jun 2026: 13 incidents (1 critical, 1 major, 8 minor, 3 no impact stated) · typical time to resolve 2 h 9 min Jul 2026: 7 incidents (2 major, 4 minor, 1 no impact stated) · typical time to resolve 7 h 55 min Aug 2026: 13 incidents (1 major, 9 minor, 3 no impact stated) · typical time to resolve 6 h 30 min Sep 2026: 9 incidents (1 critical, 3 minor, 5 no impact stated) · typical time to resolve 2 h 41 min Oct 2026: 151 incidents (1 critical, 1 major, 4 minor, 145 no impact stated) · typical time to resolve 2 h 24 min Nov 2026: 122 incidents (2 minor, 120 no impact stated) · typical time to resolve 1 h 36 min Dec 2025Jan 2026Feb Mar Apr May Jun Jul Aug Sep Oct Nov

critical major minor no impact stated

Components affected

ComponentIncidents
WildFire Finland Cloud12
WildFire Germany Cloud12
Wildfire Spain Cloud11
WildFire Australia Cloud10
WildFire EU Regulated Cloud10
WildFire France Cloud10
WildFire India Cloud10
WildFire Israel Cloud10

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

Incidents reported by Chronosphere's subprocessorsCSV · Atom

7 reported incidents in the last 30 days, by 2 of the vendors Chronosphere lists as subprocessors.

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

DateCompanyIncidentImpactLasted
ShortcutGoogle Sheets Processing Delayed minor22 min
FullstoryDelays in syncing to S3 data warehouses (EU1) minor8 h 46 min
Fullstory[Resolved] Delayed Session Data Availability (NA1 & EU1 Data Centers) no impact stated—
ShortcutSome GitHub processing delays minor19 h 18 min
ShortcutSome GitHub processing delays minor2 h 54 min
ShortcutOutgoing Webhook Delay minor52 min
ShortcutOutgoing Webhook Delay minor35 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 Chronosphere's site

Chronosphere transparency rating

It updates with the rating.

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