- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 25of 100
What to do
Check whether you use Chroma Cloud API. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-01-27 23:57 UTC and 2026-01-27 23:57 UTC may need a replay.Subscribe to Chroma Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=chroma works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Chroma Cloud 1
- resolved
Type: Incident Duration: 1 hour and 33 minutes Affected Components: API Jan 28, 01:30:00 GMT+0 - Resolved - This incident has been resolved. Jan 28, 00:25:46 GMT+0 - Investigating - We implemented a fix and are currently monitoring the system as health restores. Jan 27, 23:57:15 GMT+0 - Investigating - We are currently investigating this incident where Chroma Cloud is returning 504 errors at an increased rate and query latencies are degraded.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-57f5ff3f79
Is Chroma Cloud still down?
No, this incident was resolved 2026-01-27 23:57 UTC. For Chroma Cloud's live state, see https://down.guide/chroma.
How long did it last?
0m, from 2026-01-27 23:57 UTC to 2026-01-27 23:57 UTC, by the times Chroma Cloud posted.
What was affected?
Chroma Cloud named API.
What caused it?
Chroma Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Chroma Cloud's official status page, https://status.trychroma.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.