Skip to main content
Chromatic

Slow builds

Degraded Lasted 2h 34m · started · Chromatic's page

Level
confirmed
Worst impact
Degraded
Components
Capture Cloud
Down Index
24of 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 2h 34m it lasted.

    Anything that failed between 2026-09-23 20:10 UTC and 2026-09-23 22:44 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

  1. degraded

    We are investigating delayed builds.

    provider

  2. degraded

    We are continuing to investigate delayed builds.

    provider

  3. degraded

    Build times are improving, and we are monitoring.

    provider

  4. resolved

    Build times are stables, 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-d040670b74

Is Chromatic still down?

No, this incident was resolved 2026-09-23 22:44 UTC. For Chromatic's live state, see https://down.guide/chromatic.

How long did it last?

2h 34m, from 2026-09-23 20:10 UTC to 2026-09-23 22:44 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.