User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
chromatic.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 678 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 501 ms | 0 |
| Nov 6 | 0 | 0.0 | 468 ms | 0 |
| Nov 7 | 0 | 0.0 | 582 ms | 0 |
| Nov 7 | 0 | 0.0 | 861 ms | 0 |
| Nov 7 | 0 | 0.0 | 626 ms | 0 |
| Nov 8 | 0 | 0.0 | 503 ms | 0 |
| Nov 8 | 0 | 0.0 | 798 ms | 0 |
| Nov 8 | 0 | 0.0 | 565 ms | 0 |
| Nov 8 | 0 | 0.0 | 533 ms | 0 |
| Nov 9 | 0 | 0.0 | 664 ms | 0 |
| Nov 9 | 0 | 0.0 | 463 ms | 0 |
| Nov 9 | 0 | 0.0 | 498 ms | 0 |
| Nov 9 | 0 | 0.0 | 532 ms | 0 |
| Nov 10 | 0 | 0.0 | 715 ms | 0 |
| Nov 10 | 0 | 0.0 | 493 ms | 0 |
| Nov 10 | 0 | 0.0 | 552 ms | 0 |
| Nov 10 | 0 | 0.0 | 515 ms | 0 |
| Nov 11 | 0 | 0.0 | 550 ms | 0 |
| Nov 11 | 0 | 0.0 | 524 ms | 0 |
| Nov 11 | 0 | 0.0 | 558 ms | 0 |
| Nov 11 | 0 | 0.0 | 499 ms | 0 |
| Nov 12 | 0 | 0.0 | 563 ms | 0 |
| Nov 12 | 0 | 0.0 | 483 ms | 0 |
| Nov 12 | 0 | 0.0 | 446 ms | 0 |
| Nov 12 | 0 | 0.0 | 506 ms | 0 |
| Nov 13 | 0 | 0.0 | 478 ms | 0 |
| Nov 13 | 0 | 0.0 | 465 ms | 0 |
| Nov 13 | 0 | 0.0 | 491 ms | 0 |
| Nov 13 | 0 | 0.0 | 496 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Chromatic yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Chromatic goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Chromatic alerts to Slack, Discord or a webhook — free.
Chromatic is listed in our Cloud & developer category and checked at chromatic.com. Chromatic catches visual, interaction, and accessibility issues before they ship. This enforces your UI standards, even when AI codes. Assign reviewers to speed up sign-off and provide agents with validated UI context.
Chromatic publishes an official status page at status.chromatic.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 501 ms average, 398–678 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Chromatic incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
501 ms on average over the last 24 hours (398–678 ms).
Yes, at https://status.chromatic.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Chromatic here at once, the problem is on Chromatic's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Chromatic. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.