- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 31of 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 4h 30m it lasted.
Anything that failed between 2025-10-10 16:07 UTC and 2025-10-10 20:37 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 have received reports that SSO is failing with the message `Unknown error: An exception occurred`. We believe that we have isolated the cause of this error and are working on an immediate fix. We will keep this page up to date with the status of this incident.
provider
- resolved
We have deployed mitigations for the SSO issue and are cautiously optimistic that we have a resolution. We are continuing to monitor for recurrence or for other related problems.
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-3aba2cce28
Is Chromatic still down?
No, this incident was resolved 2025-10-10 20:37 UTC. For Chromatic's live state, see https://down.guide/chromatic.
How long did it last?
4h 30m, from 2025-10-10 16:07 UTC to 2025-10-10 20:37 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.