- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 14of 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 15m it lasted.
Anything that failed between 2025-11-03 18:55 UTC and 2025-11-03 19:10 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
We are noticing a delay in the processing of builds on our end. We don't expect this to cause problems with the ultimate completion of these builds or other parts of the platform and are deploying mitigations while we determine the cause.
provider
- resolved
Build times have returned to normal and we are keeping a close on our systems to ensure that we've resolved the root cause of the issue.
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-18945e095b
Is Chromatic still down?
No, this incident was resolved 2025-11-03 19:10 UTC. For Chromatic's live state, see https://down.guide/chromatic.
How long did it last?
15m, from 2025-11-03 18:55 UTC to 2025-11-03 19:10 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.