Chroma: Chroma embedding service experiencing intermittent failures
AWS us-east-1 outage, May 8, 2026 · 38 vendors, 43 incidents
Chroma’s incident blames AWS as the cause. (hop 1, posted +39 min vs AWS’s own post)
“…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…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>posted 00:25 UTC"]:::root
before["Posted before AWS did<br/>3 vendors, 2 blamed AWS<br/>Neon, Datadog, Convex"]:::blames
root --> before
h1["Within an hour<br/>11 vendors, 11 blamed AWS<br/>Chargebee, RudderStack, Canva, Logz.io +7"]:::blames
root --> h1
h4["1 to 4 hours later<br/>10 vendors, 9 blamed AWS<br/>Salesforce, Dropbox Sign, Klaviyo, HubSpot +6"]:::blames
root --> h4
later["Later<br/>2 vendors, 2 blamed AWS<br/>Wiz, SingleStore"]:::blames
root --> later
me["Chroma (this incident)<br/>posted +39 min"]:::me
h1 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Hosted embedding service
Timeline of updates
- identified
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 service. .
- resolved
This incident has been resolved..
Impact, status and times are the vendor’s own, as last archived. View on status.trychroma.com (opens in new tab).