- Level
- confirmed
- Worst impact
- Degraded
- Components
- Capture Cloud
- Down Index
- 26of 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 5h 35m it lasted.
Anything that failed between 2026-11-04 22:41 UTC and 2026-11-05 04:15 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 4
- degraded
Our capture stack is experiencing slower than normal build times. We are continuing to monitor the situation closely and will provide further updates as it progresses.
provider
- degraded
We are continuing to monitor the situation regarding slower than normal build times.
provider
- degraded
Builds are resolving, but still more slowly than normal. We're continuing to investigate.
provider
- resolved
Mitigations have been deployed, and build times have returned to normal.
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-8178544ba3
Is Chromatic still down?
No, this incident was resolved 2026-11-05 04:15 UTC. For Chromatic's live state, see https://down.guide/chromatic.
How long did it last?
5h 35m, from 2026-11-04 22:41 UTC to 2026-11-05 04:15 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.