- 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 15m it lasted.
Anything that failed between 2026-09-21 18:45 UTC and 2026-09-22 00:00 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 5
- degraded
We are investigating delayed builds.
provider
- degraded
We've found that this impacts some customers on Capture v8 infrastructure. We are continuing to investigate.
provider
- degraded
We've applied a mitigation and are seeing improvement. We'll continue to monitor.
provider
- degraded
Build times for Chrome are improving, and we're continuing to monitor.
provider
- resolved
Our build systems have returned to a stable state, and we're now processing builds as 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-86f08ab125
Is Chromatic still down?
No, this incident was resolved 2026-09-22 00:00 UTC. For Chromatic's live state, see https://down.guide/chromatic.
How long did it last?
5h 15m, from 2026-09-21 18:45 UTC to 2026-09-22 00:00 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.