- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Chromatic. 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 41m it lasted.
Anything that failed between 2026-07-10 19:45 UTC and 2026-07-10 20:26 UTC may need a replay.Subscribe to Chromatic's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=chromatic works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Chromatic 2
- update
Capture Cloud is working, and builds are starting to process again. Our engineers have identified the root cause and are working on deploying a fix.
provider
- resolved
The issue has been identified and should now be resolved. Our engineers are working through the backlog.
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-fb80405bdf
Is Chromatic still down?
No, this incident was resolved 2026-07-10 20:26 UTC. For Chromatic's live state, see https://down.guide/chromatic.
How long did it last?
41m, from 2026-07-10 19:45 UTC to 2026-07-10 20:26 UTC, by the times Chromatic posted.
What caused it?
Chromatic hasn't published a root cause. If it does, it shows here.
Where does this come from?
Chromatic's official status page, https://status.chromatic.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.