Chromatic incident

Users not being able to sign into Chromatic via GitLab

Minor Resolved View vendor source →

Chromatic experienced a minor incident on February 26, 2026, lasting 7h 27m. The incident has been resolved; the full update timeline is below.

Started
Feb 26, 2026, 10:30 AM UTC
Resolved
Feb 26, 2026, 05:57 PM UTC
Duration
7h 27m
Detected by Pingoru
Feb 26, 2026, 10:30 AM UTC

Update timeline

  1. investigating Feb 26, 2026, 10:30 AM UTC

    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.

  2. investigating Feb 26, 2026, 11:35 AM UTC

    We are actively investigating the root cause of the issue and will provide an update as soon as we have more information.

  3. investigating Feb 26, 2026, 01:03 PM UTC

    We've identified the root cause of the issue, and our team is actively working to fix it.

  4. investigating Feb 26, 2026, 03:26 PM UTC

    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.

  5. investigating Feb 26, 2026, 04:46 PM UTC

    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.

  6. resolved Feb 26, 2026, 05:57 PM UTC

    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.