- Status page says
- Operational since Oct 19
- Last 90 days
- 1 incidents
- Rewrites caught
- None so far
- Next deprecation
- None announced
Select a day to jump to its incidents below.
How Chroma reports incidents
Not enough incidents to compare Chroma with other vendors yet: a vendor needs 20 incidents in a year and 10 with full update detail (Chroma has 6 and 15).
Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors
Dependencies
What Chroma relies on and who relies on Chroma, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.
Chroma depends on
| Provider | Evidence | Signal |
|---|---|---|
| AWS (us-east-1) | blamed in 1 incident; named as hosting in 2; together in 1 outage event “…service experiencing intermittent failures Our infrastructure is affected by an outage in AWS: <https://health.aws.amazon.com/health/status> We are monitoring the incident and working to restore servi…” incident | Likely |
Runs in (named in its incidents): AWS us-east-1 (2).
Outage events: AWS us-east-1, May 8.
Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.
Changes and edits
Incidents Chroma rewrote or removed, and notable changes to the pages we watch.
Struck in red is what Chroma removed. Blue is what they added.
No notable changes yet. We compare every snapshot of Chroma’s status page (taken every 10 minutes) and its 3 tracked pages.
Pricing and pages we watch
| Page | Versions | Last changed | Last checked | History |
|---|---|---|---|---|
| Privacy policy (opens in new tab) | 1 | No changes yet | ||
| Subprocessors (opens in new tab) | 1 | No changes yet | ||
| Terms of service (opens in new tab) | 1 | No changes yet |
Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.
The Weekly Rewind: one short weekly email on what changed at Chroma and the other vendors we track, including silent edits. Subscribe (opens in new tab)
Incidents
15 incidents since Apr 15, 2025. Maintenance is left out.
Per year, major and critical in amber:
2025: 10 incidents, 0 major or critical; 2026: 5 incidents, 0 major or critical
Tuesday, August 18
1 incident
- unknown, 2 h 39 minIncident
Monday, June 29
1 incident
- unknown, 32 minIncident
Friday, May 8
1 incident
- unknown, 1 h 45 minIncident
Friday, March 13
1 incident
- unknown, 2 h 5 minIncident
Tuesday, January 27
1 incident
- unknown, 1 h 33 minIncident
Saturday, November 1, 2025
1 incident
- unknown, 22 minIncident
Friday, October 3, 2025
1 incident
- unknown, 1 h 13 minIncident
Sunday, September 21, 2025
1 incident
- unknown, 56 minIncident
Wednesday, August 20, 2025
1 incident
- unknown, 15 minIncident
Wednesday, August 6, 2025
1 incident
- unknown, 27 minIncident
Tuesday, June 24, 2025
1 incident
- unknown, 20 minIncident
Friday, May 30, 2025
1 incident
- unknown, 39 minIncident
Tuesday, May 6, 2025
1 incident
- unknown, 1 h 2 minIncident
Friday, April 18, 2025
1 incident
- unknown, 3 daysIncident
Tuesday, April 15, 2025
1 incident
- unknown, 1 h 30 minIncident