Is Chromatic Down?

No — Chromatic is up

Reachable from all 8 checked regions

Average response time: 2578ms

Last checked 5 hours ago · checks run every 6 hours

Official status page: https://status.chromatic.com

Chromatic uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

1370ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 15 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

15-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

jnb

6484ms

DNS 246ms TCP 238ms TLS 239ms TTFB 5535ms

lax

5196ms

DNS 93ms TCP 60ms TLS 61ms TTFB 4961ms

lhr

912ms

DNS 20ms TCP 82ms TLS 83ms TTFB 584ms

nrt

1613ms

DNS 126ms TCP 175ms TLS 175ms TTFB 917ms

ord

453ms

DNS 65ms TCP 22ms TLS 23ms TTFB 365ms

sin

2822ms

DNS 288ms TCP 231ms TLS 232ms TTFB 1901ms

sjc

1069ms

DNS 128ms TCP 69ms TLS 71ms TTFB 793ms

syd

2082ms

DNS 149ms TCP 194ms TLS 195ms TTFB 1307ms

What Chromatic does

Chromatic is a UI testing and review platform from the team behind Storybook, not the musical scale or the lens effect. Teams run the chromatic CLI or GitHub Action in CI to publish their Storybook, or Playwright and Cypress tests. Chromatic captures snapshots in its Capture Cloud, flags visual, interaction and accessibility changes, and hosts the published Storybook so reviewers can approve UI changes before a pull request merges.

What an outage looks like

Chromatic builds queue or run far longer than usual, the web app times out, UI Review pages show errors or blank screens, and published Storybook MCP servers return 503 or 504 errors. In CI the chromatic CLI can exit with code 3 (BUILD_FAILED, a system error), 201 (FETCH_ERROR) or 202 (GRAPHQL_ERROR), failing the job even though nothing in your components changed.

What to do about it

Check status.chromatic.com, which tracks App, Capture Cloud, SSO Authentication and Hosted Storybook. Recent slow-build incidents resolved in roughly two to five hours, so rerun failed CI jobs after the incident closes rather than accepting changes you have not reviewed. If a required check blocks an urgent merge, Chromatic's skip option marks the commit as passing without running tests. Use in-app chat for help; email is the slower fallback.

Is it down for everyone, or just you?

If this page says Chromatic is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Chromatic outage FAQ

Is Chromatic down for everyone or just me?

Check status.chromatic.com, the status page Chromatic's own docs link to, and read the incident scope. Some incidents hit only part of the customer base: slow builds on September 21, 2026 affected some customers on Capture v8 infrastructure, and a July 30, 2026 UI Review issue affected a small subset of accounts linked to Bitbucket repositories, so a green component list is not proof your account is unaffected.

Why did my Chromatic CI job fail?

The CLI exit code tells you whose problem it is. Code 1 means visual changes were found and 2 means component errors, both about your code. Code 3 is BUILD_FAILED due to a system error, 201 is an HTTP fetch error and 202 a GraphQL API error, which point at Chromatic or the network. Codes 11 and 12 mean snapshot quota or payment issues.

What does the Chromatic skip option do?

It skips Chromatic tests but marks the commit as passing. Chromatic documents it as the way to avoid blocking pull requests on required merge checks, and it takes true or a branch glob, as the --skip flag, the GitHub Action input or skip in chromatic.config.json. Skipped commits get no visual review, so rerun Chromatic on the branch once service is back.

How long do Chromatic outages usually last?

Posted incidents mostly last a few hours. Slow builds on September 23, 2026 ran from 20:10 to 22:44 UTC, and slow builds on September 21, 2026 took about five hours to fully clear. Web app and build timeouts on July 30, 2026 lasted about two and a half hours, and published Storybook MCP errors on September 4, 2026 about an hour.

How do I contact Chromatic support during an outage?

Use the in-app chat, with version numbers, logs and screenshots. Chromatic's support docs say email to support@chromatic.com works but is a last resort because replies take longer. For outage updates, the docs point to status.chromatic.com, where you can subscribe to status updates instead of waiting on a support reply.

How we measure this

We request Chromatic's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Chromatic publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Chromatic goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required