GitLab.com Status

GitLab.com is currently operating normally. The issue has been resolved. For more info, please see: gitlab.com/gitlab-com/gl-… status.gitlab.com

The revert MR to remove the Claude Fable was merged and deployed to production. While the GitLab.com service is back to normal, Fable remains unavailable due to an upstream suspension. Customers need continue to select a different... status.gitlab.com

Although Claude Fable is not available on GitLab.com, it still appears in the model selection menu. Customers who are currently using it should manually select a different model. Please see the notice from the upstream provider: h... status.gitlab.com

Claude Fable is not available through GitLab.com. Please see the notice from the upstream provider: status.claude.com/incidents/s9w8… status.gitlab.com

GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database and the issue should be resolved now. status.gitlab.com

GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database, and we are continuing to monitor closely. status.gitlab.com

The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently. status.gitlab.com

We changed the status title to reflect the intermittent nature of this incident. We'll share another update as soon as we have more information. status.gitlab.com

We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information. status.gitlab.com

GitLab Credits dashboards are operating normally again. The issue has been resolved. status.gitlab.com

Mitigation has been applied and GitLab Credits dashboards appear to be loading again. We’ll leave affected components marked as Partial Service Disruption as we monitor error rates closely to ensure the service remains stable. status.gitlab.com

The GitLab.com credit dashboard fails to load, displaying the error message: "An error occurred while fetching data". This issue is under investigation. status.gitlab.com

The job queue is now cleared and we do not expect any further customer impact. This is considered resolved. For more info, see: gitlab.com/gitlab-com/gl-… status.gitlab.com

Error rates have recovered back to normal levels and we started processing jobs again. We expect that the job queue should be processed over the next 30 minutes. For more info, see: gitlab.com/gitlab-com/gl-… status.gitlab.com

The change has been reverted and we are seeing that error rates are recovering. For more info, see: gitlab.com/gitlab-com/gl-… status.gitlab.com

We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: gitlab.com/gitlab-com/gl-… status.gitlab.com

We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: gitlab.com/gitlab-com/gl-… status.gitlab.com

We are investigating an issue where CI jobs are not processing. For more info, see: gitlab.com/gitlab-com/gl-… status.gitlab.com

This issue has been resolved and error rates have returned to normal. For more info: gitlab.com/gitlab-com/gl-… status.gitlab.com

Error rates have decreased significantly following the fix. We are continuing to monitor the situation. For more info: gitlab.com/gitlab-com/gl-… status.gitlab.com