Chromatic incident
Users not being able to sign into Chromatic via GitLab
Resolved after 7 hours 27 minutes, on February 26, 2026.
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.
Update timeline
- 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.
- 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.
- 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.
- 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.
- 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.
Your product runs on more than Chromatic
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services