Chromatic had 24 outages in the last 2 years totaling 53h 10m of downtime — averaging 1 incident per month.
There were 24 Chromatic outages since October 10, 2025 totaling 53h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating intermittent build failures.
We are still investigating the intermittent build failures.
The build queue backlog is decreasing, and we're monitoring it.
We are investigating delayed builds.
We are continuing to investigate delayed builds.
We are investigating 503 and 504 errors on published Storybook MCP servers.
We're rolling out a fix for the published Storybook MCP and continuing to monitor.
Hosted Storybook went down
We are investigating degraded performance of the web app and slow builds.
A fix is in place, and we're continuing to monitor the situation.
We have identified that some UI Reviews are not opening for some accounts linked to Bitbucket repositories. Users may experience errors or blank screens when attempting to access these reviews. We are currently investigating the root cause and will provide updates as more information becomes available.
We are monitoring the situation closely as we continue our investigation. We believe it's affecting a very small subset of users.
Capture Cloud went down
We have detected an increase in build times and the number of pending builds. Our team is responding to ensure that builds in process proceed without having to be cancelled or rerun.
Our team is still working to resolve the slowdown in build progress. We will continue to update here as we make progress.
We believe we have identified the root cause of the issue and are testing fixes. We are seeing improvements in processing times and will continue to monitor and update this page.
We have seen sustained and improvement and believe that the root cause of the build time delays has been resolved. Users may see builds that were in progress during the incident continue to take extra time and occasionally timeout, but new builds should be processed quickly. If you prefer, you can cancel builds to avoid waiting and rerun them now, or you can allow them to complete or timeout at the 2 hour mark.
We have received reports that the issue with build delays is still affecting some customers. We have reopened this incident and are actively investigating. We’ll share updates here as soon as we have more information.
We believe we have identified the root cause of the issue and have implemented a fix. We are seeing improvements in processing times and will continue to monitor and update this page.
We've confirmed that build performance has returned to normal, and the earlier delays have been fully resolved. All new builds are processing as expected. If you still have builds from earlier that appear stuck or delayed, you can allow them to complete on their own. We’ll continue to monitor closely.
A fix is in place, but we are continuing to monitor extended build times for some users.
We are continuing to monitor extended build times and are actively working on a fix.
Our systems are working through the backlog of delayed builds, and timeouts may still occur. We're continuing to monitor the situation and will update as it progresses.
We are currently investigating reports of users experiencing issues with the UI Review feature in Chromatic. Our team is actively looking into the root cause and will provide updates as we learn more.
We've resolved the issue and the app experience is back to normal. If you are experiencing any further issues, please reach out to support with questions.
App recovered
Our Marketing, Documentation, and Blog pages may be experiencing degraded performance, and users may have experienced delays or disruptions when visiting these pages
We've become aware of a performance degradation in the app that is causing the duration of requests to increase. We are working on diagnosing this problem and are deploying mitigations to keep the app experience good. We'll keep this page up to date as we work through this issue.
We've seen some improvements in app performance due to our mitigations and we'll continue to work to restore performance to normal levels.
We've resolved our performance issues from this morning and the app experience is back to normal. If you are experiencing any further issues, please reach out to support with questions.
A limited subset of app IDs are unable to load their build lists and are getting 500 errors when attempting to do so. We are investigating the issue with the intent at restoring normal functionality as soon as possible. We will keep this page up to date through our efforts.
We've identified the cause of the problem and have rolled back a recent change, which we believe has resolved this issue. We will continue to monitor our rollback. If you are still experiencing any problems, please let support know via in-app chat or via [email protected]
We are noticing builds taking longer to process than usual and are investigating possible causes. Builds are still completing but we are investigating the issue to see if it is transitory or is something that we can resolve. Builds should not be failing or timing out at this time.
We believe we have resolved the slow build issue and are monitoring for more issues. We'll also be making further changes to prevent this from recurring long-term.
We received reports that the Review tab is missing from the dashboard for some users. Please note the page remains accessible via direct link. We have just deployed a fix, and the issue should be resolved.
We are currently seeing some reports of users not being able to sign into Chromatic via GitLab. We are aware of these reports and are investigating the root cause.
We are actively investigating the root cause of the issue and will provide an update as soon as we have more information.
We've identified the root cause of the issue, and our team is actively working to fix it.
We have reached out to our upstream partner and are working with them to resolve the issue affecting sign-ins to Chromatic via GitLab. Our team continues to work on a resolution, and we will provide more updates as soon as we have additional information.
GitLab has informed us that they are working to resolve an incident that is downstream of our incident. We expect that once they resolve their problem that our problem will be resolved as well. We will continue to update this update with more information.
The downstream provider has made a change that has resulted in the resolution of this issue. We are not seeing this error in our logs anymore and can confirm that customers should have no further issues with GitLab logins. If you are still experiencing issues, please reach out to support and let us know, as we now regard this issue is closed.
We are currently experiencing slower than usual page loads for account and test pages. We are working on a mitigation to return page load times to normal and will keep this page up to date as we proceed.
We have identified the cause of the slowdown and resolved the underlying issue, and will be pursuing mitigations in the future to prevent this issue from recurring in the future. If you are still experiencing issues, please reach out to your customer success manager or support.
Users that log in using their GitHub accounts are likely experiencing a problem that we believe is related to one of a few production incidents occurring at Github. See their status page: https://www.githubstatus.com/ Other integrations with GitHub are likely to be experiencing issues right now. If you believe that you are encountering a problem that is related directly to Chromatic and is not a downstream effect of the GitHub incidents, please reach out to Chromatic support.
We have confirmed that authentication with Github accounts is now working as expected on our site. Please write in to support if you have additional concerns or continue to be unable to log in.
We're currently investigating reports of GitHub status checks failing for a specific subset of customers. We will update this status page periodically with more info or as the situation develops.
We have identified the root cause and are working on a fix that we believe will resolve this incident. We will update this page with an update shortly.
We've resolved the underlying issue for this incident and have confirmed that GitHub status checks are working as expected. If you suspect you were experiencing this issue, you can push an additional commit to the affected branch to clear the check. If you are still having problems with status checks, please reach out to support in the app or at [email protected]
Currently anonymous access to any (potentially authenticated) Chromatic URL will timeout with a 504 error. This includes URLs for projects which should be public.
Note you can access projects if you are logged in at www.chromatic.com
We have identified the root cause and are working on a fix that we believe will resolve this incident. We will update this page with an update shortly.
We've resolved the underlying issue for this incident and believe all Chromatic's functionality is returned to normal. If you are continuing to have problems with accessing your Chromatic app, please reach out to support.
We are currently working through an issue with the Chromatic Figma App, which is unavailable. We will update this status page periodically with more info or as the situation develops.
We've identified the issue and are working through a fix.
We believe we have resolved the issue with the Figma integration and are monitoring to ensure that everything works as expected. We will reopen an issue if we discover additional problems.
We are noticing a delay in the processing of builds on our end. We don't expect this to cause problems with the ultimate completion of these builds or other parts of the platform and are deploying mitigations while we determine the cause.
Build times have returned to normal and we are keeping a close on our systems to ensure that we've resolved the root cause of the issue.
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.
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.