Skip to main content
Chromatic

Published Storybook MCP errors

Degraded Lasted 56m · started · Chromatic's page

Level
confirmed
Worst impact
Degraded
Components
Hosted Storybook
Down Index
22of 100

What to do

  • Check whether you use Chromatic Hosted Storybook. 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 56m it lasted.

    Anything that failed between 2026-09-04 16:20 UTC and 2026-09-04 17:16 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

  1. degraded

    We are investigating 503 and 504 errors on published Storybook MCP servers.

    provider

  2. degraded

    We're rolling out a fix for the published Storybook MCP and continuing to monitor.

    provider

  3. resolved

    Published Storybook MCP has returned to normal, and requests are resolving as expected.

    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-f2d60ae77c

Is Chromatic still down?

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

How long did it last?

56m, from 2026-09-04 16:20 UTC to 2026-09-04 17:16 UTC, by the times Chromatic posted.

What was affected?

Chromatic named Hosted Storybook.

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.