- Level
- confirmed
- Worst impact
- Degraded
- Components
- Capture Cloud
- Down Index
- 13of 100
What to do
Check whether you use Chromatic Capture Cloud. 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-10-21 17:58 UTC and 2026-10-21 17:58 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 1
- resolved
Between 17:25 UTC and 17:50 UTC, builds submitted may have failed to run. We have recovered, and new builds or those submitted for rerun are succeeding. We are monitoring builds to watch for continued recovery.
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-6c725b4ce1
Is Chromatic still down?
No, this incident was resolved 2026-10-21 17:58 UTC. For Chromatic's live state, see https://down.guide/chromatic.
How long did it last?
0m, from 2026-10-21 17:58 UTC to 2026-10-21 17:58 UTC, by the times Chromatic posted.
What was affected?
Chromatic named Capture Cloud.
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.