- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 2h 27m it lasted.
Anything that failed between 2026-07-30 22:02 UTC and 2026-07-31 00:29 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 3
- update
We are investigating degraded performance of the web app and slow builds.
provider
- update
A fix is in place, and we're continuing to monitor the situation.
provider
- resolved
Service has returned to normal, and builds are resolving as expected. We'll continue to investigate root causes to prevent future recurrence.
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-139eda2249
Is Chromatic still down?
No, this incident was resolved 2026-07-31 00:29 UTC. For Chromatic's live state, see https://down.guide/chromatic.
How long did it last?
2h 27m, from 2026-07-30 22:02 UTC to 2026-07-31 00:29 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.