Looking for an update now? Check the current status, or follow GitLab for future changes.
Building verified history12 of 24 verified daily observations collected. A percentage will appear after the minimum coverage threshold is met.
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Recorded Daily Status (Last 54 Days)
Jul 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
45 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Errors interacting with git via SSH
Source not attested
Last archived state: resolved
View archived record details
resolved
We are investigating ongoing errors when attempting to interact with repositories via SSH. HTTPS does not appear to be impacted at this time. We are investigating. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364
Elevated errors in background job processing
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We've identified a recent code change as the likely cause of elevated Sidekiq job execution errors on the low-urgency-cpu-bound shard, which may delay processing of some background jobs. Mitigations are in progress. We'll continue to update as soon as the mitigation is merged and deployed.
Claude Fable is not available through GitLab.com
minorSource not attested
Last archived state: investigating
View archived record details
investigating
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 model. We are monitoring the situation closely.
investigating
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: https://status.claude.com/incidents/s9w82lp9dcn9
investigating
Claude Fable is not available through GitLab.com. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9
Intermittent 5XX errors accessing in GitLab.com
minorSource not attested
Last archived state: investigating
View archived record details
investigating
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.
investigating
The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently.
investigating
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.
investigating
We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.
investigating
We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.
Credits Dashboard Disruption
Source not attested
Last archived state: resolved
View archived record details
resolved
The GitLab.com credit dashboard fails to load, displaying the error message: "An error occurred while fetching data". This issue is under investigation.
Issue with processing CI jobs
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
monitoring
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: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
monitoring
We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
monitoring
We are investigating an issue where CI jobs are not processing. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
Duo Agent Platform Flows not working for some projects
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
Error rates have decreased significantly following the fix. We are continuing to monitor the situation. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
monitoring
We have merged a fix for the Duo Agent Platform Flow failures and it is awaiting deployment. Deployment is expected to take several hours. We will share our next update once the deployment is complete. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
monitoring
We have identified the root cause of the recent Duo Agent Platform Flow failures and are deploying a fix. Customers should begin seeing improvements as the deployment completes. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
monitoring
We are investigating an issue where Duo Agent Platform Flows, including Duo Code Review, are not working on some projects. See issue for more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
Problem with Duo Agent Platform Flows
minorSource not attested
Last archived state: monitoring
View archived record details
monitoring
We have identified the issue and we're rolling out a fix to production. Customers should start to see improvement as deployment completes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241
monitoring
We are investigating an issue where Duo Agent Platform Flows fail to start when used with the default Docker image. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241
May 2026
Issues with GitLab Duo in merge requests
minorSource not attested
Last archived state: investigating
View archived record details
investigating
A fix has now been deployed that should remediate the errors. We will continue to monitor, and as long as error rates remain low, we will resolve the incident.
investigating
No material updates at this time. Our team is still seeing some failures which prompted additional investigation. While there has been a drop in errors, some users continue to experience issues.
investigating
After monitoring, our team is still seeing some failures which is prompting additional investigation. While there has been a drop in errors, some users continue to experience issues.
investigating
We are still monitoring the deployed fix. We will share another update once we can confirm it's fully resolved. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22228
investigating
A fix has been deployed via a revert MR. We're moving the incident to Monitoring and will share another update once we can confirm it's fully resolved.
investigating
We've identified a likely root cause for the `@GitLabDuo` access errors in merge requests and are preparing a revert MR. We'll share another update once it's deployed.
investigating
We're investigating an issue where customers using `@GitLabDuo` mentions in merge requests are receiving access errors. Impact has been reported across GitLab.com, Dedicated, and Self-Managed.
Our team is actively investigating. We'll share another update as soon as we have more information.
Git operation failed
Source not attested
Last archived state: resolved
View archived record details
resolved
We receive report regarding git operation error. Our Gitaly team is investigating the problem. See more detail: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217
