GitLab Outage History
Daily status observations, past incidents, and reported issue history for GitLab.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 65.2% | 23 | 8 |
| July 2026 | 67.7% | 31 | 10 |
| June 2026 | 70% | 30 | 9 |
| May 2026 | 57.1% | 7 | 3 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 25
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
403 errors across GitLab.com
Started:
Google Compute Engine
Website
Git Operations
CI/CD
investigating
We're monitoring an incident where 403s were seen across GitLab.com. The fix for this is already in place.
More about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762
500 errors when fetching commits on GitLab.com
Started:
Google Compute Engine
Website
API
Git Operations
CI/CD
investigating
The error rate has continued to remain within normal thresholds. We're continuing to monitor the error rate.
Further developments can be read here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729
investigating
Our monitoring shows the error rate decreasing towards normal thresholds. We're continuing to monitor the incident.
More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729
investigating
Investigation for the root cause of 500 errors while fetching commits on GitLab.com is still ongoing.
More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729
investigating
We are still investigating the root cause for 500 errors while fetching commits on GitLab.com.
More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729
investigating
We are investigating an issue causing a subset of requests to GitLab.com receiving 500 errors. We will provide updates as we learn more from our investigation.
More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729
Project and Group Deletions Delayed
Started:
Google Compute Engine
Background Processing
resolved
We are currently investigating an issue affecting project and group deletions on GitLab.com.
Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date.
Elevated queue times on saas-linux-medium-arm64 runner
Started:
monitoring
The queue of pending jobs on the affected runners has returned to normal and we are monitoring recovery. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702
monitoring
The issue is mitigated and the queue of pending jobs on saas-linux-medium-arm64 is going down. We are monitoring recovery. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702
monitoring
We are seeing a growing queue of pending jobs on the saas-linux-medium-arm64 hosted runner on GitLab.com. We are rolling out a mitigation. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702
Issue with background jobs
Started:
monitoring
We have identified the cause of the issue and we are taking action to mitigate customer impact. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661
monitoring
We are investigating an issue affecting background jobs, including webhook delivery and pipelines. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661
Issues with pipelines
Started:
monitoring
We've identified a likely root cause, and the job queue has remained healthy. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
monitoring
We've disabled a worker, which should let the job queue begin recovering while we continue investigating the root cause. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
monitoring
We're investigating reports of pipelines failing and becoming stuck. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
Issues with webhook deliveries
Started:
monitoring
A fix has been deployed and checks have confirmed that unexpected IP addresses are no longer being used.
monitoring
Deployment of the fix is progressing steadily. Another update will be provided once deployed. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.
monitoring
We've traced the issue to a recent network change and are preparing a fix. Another update will be provided by 23:00 UTC.
monitoring
Our investigation is ongoing. We will provide another update by 21:00 UTC.
monitoring
We are investigating reports of webhook deliveries from GitLab.com originating from IP addresses outside our documented ranges. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.
Issue with Duo Code Review Flows
Started:
monitoring
We've identified the cause of the issue and have temporarily reverted the default Agentic Chat model to Sonnet 4.6 while we continue to investigate. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633.
monitoring
We are investigating an issue which may be affecting Duo Code Review Flows. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633
Problems related to git operations
Started:
monitoring
Restarting the affected Gitaly node relieved pressure on it, and error rates have dropped significantly. We're monitoring for continued stability. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.
monitoring
The team is still working on actions to mitigate impact from the affected Gitaly node. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
monitoring
Impact is limited to projects on a single Gitaly node. The team is currently focused on relieving pressure from the overloaded Gitaly node to mitigate impact in the affected projects. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
monitoring
The team is investigating an issue related to a Gitaly node. Customers may experience errors or slowness when performing git operations. For more info see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
July 2026
Elevated error rates on GitLab.com
Started:
investigating
We have confirmed these errors are no longer occurring. We've identified the cause of this incident and are working to prevent this from occurring in the future. We'll now move this incident to monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22579
monitoring
We observed a spike in 5xx errors on GitLab.com. These have subsided, but we are investigating the root cause.
Possible Issues Signing into GitLab.com
Started:
investigating
We're aware of previous login problems for GitLab.com and are monitoring the situation. For details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22551
monitoring
We are still monitoring the situation with possible issues logging into GitLab.com and will provide further updates when they are available.
monitoring
We are currently receiving reports and investigating issues with signing into GitLab.com. We will provide more information once it is available.
Elevated Errors Affecting GitLab Duo Custom Agents
Started:
resolved
We're investigating an issue affecting GitLab Duo Custom Agents on GitLab.com. Our team is actively working to identify the cause and restore normal service.
Degraded performance affecting package pulls from registry(packages.gitlab.com)
Started:
monitoring
Mitigation efforts remain in progress. We're continuing to monitor the implementation and will provide another update once additional progress has been made.
monitoring
There are no significant updates to share at this time. Mitigation efforts are still underway, and we will continue to provide updates as they become available.
monitoring
We have no material updates at this time. Our team remains focused on mitigation efforts and will continue to share updates as we make progress.
monitoring
We've identified the root cause of the issue and are continuing to implement mitigation measures. We'll provide additional updates as progress is made.
monitoring
Mitigation efforts are ongoing to address the issue affecting package pulls from our registry. Slow or failed Omnibus package downloads may still occur.
monitoring
No material updates to report at this time. We are continuing to investigate the current issue and engineers are working to determine remediation steps.
monitoring
Recovery efforts remain in progress for the issue impacting package pulls from our registry. Some Omnibus package downloads may continue to be slow or fail until the issue is resolved.
monitoring
Work to resolve the package registry issue is ongoing. During this time, some users may continue to experience slow or unsuccessful Omnibus package downloads.
monitoring
We continue to work on resolving the issue with package pulls from our registry. Users may still experience slow or failed Omnibus package downloads. We will share another update as soon as we have more information.
monitoring
We are investigating degraded performance affecting package pulls from our registry. Users may experience slow or failed Omnibus package downloads while we investigate. Currently, the engineering team has identified the cause of the degraded performance and is currently working to resolve the issue. Users may continue to experience slow or failed Omnibus package downloads while mitigation is in progress.
Elevated Errors Affecting AI Gateway Health Checks
Started:
resolved
We're aware of elevated errors affecting AI Gateway health checks. We've identified a likely cause and are actively working on a fix. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519
Issues deleting new MR approval rules
Started:
monitoring
The fix has been merged and we are now monitoring. If you still experience the issues, please open a ticket with support. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470
monitoring
The fix will merge as soon as it's pipeline completes. The status will change to monitoring at that time. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470
monitoring
No further updates at this time. The merge request is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470
monitoring
No updates at this time. A merge request fix has been created and is currently being worked on. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470
monitoring
A merge request fix has been created and is currently being worked on. We will update as the situation changes. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470
monitoring
The fix is still in progress, no updates at this time. More: https://gitlab.com/gitlab-org/gitlab/-/work_items/605117
monitoring
We've discovered that attempts to delete newly created MR approval rules may fail in certain cases. The cause has been identified and the fix is in the works. More: gitlab.com/gitlab-org/gitlab/-/work_items/605117
investigating
We've discovered that attempts to delete newly created MR approval rules may fail in certain cases. The cause has been identified and the fix is in the works. More: https://gitlab.com/gitlab-org/gitlab/-/work_items/605117
CI pipelines stuck in pending state
Started:
monitoring
We are continuing to investigate and look into CI pipelines being stuck in pending state.
monitoring
We are currently investigating the cause of CI pipelines being stuck in pending state. More details can be found here:
https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22433
June 2026
Code Suggestions not working
Started:
resolved
We are investigating errors with code suggestion not completing.
500 errors, CI checkout failures and slow page loads
Started:
monitoring
We have identified the issue and taken action to correct the matter and are monitoring GitLab.com. We will provide further updates as information is available or when the issue is confirmed resolved.
monitoring
We are continuing to investigate and work to resolve the degraded performance on GitLab.com
monitoring
We have identified the cause of the increased error rate and are taking corrective action and monitoring the incident.
monitoring
We are continuing to investigate and look into the increased errors on GitLab.com
monitoring
We are investigating the cause, but the symptoms are: 500 errors, CI jobs can't check out repos, slow merge request page loading, slow page loading
CI pipelines not starting on merge requests.
Started:
resolved
We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root cause.
Errors interacting with git via SSH
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Delays in CI job processing by runners
Started:
resolved
Some users may see jobs pending while waiting for runners. The team is currently working on the fix. We will update in 30 minutes. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212
GitLab Duo "Quota exceeded" Errors
Started:
investigating
The cache is refreshed for some users, and we've received confirmation from a few customers that DAP is working again for them. We're keeping a close eye on metrics before marking this as fully mitigated.
investigating
We've identified a feature flag on the Customers Portal as the likely cause of the issue affecting GitLab DAP. The flag has been disabled, and we're monitoring logs and metrics for recovery. Customers may continue to see errors due to cache duration. We'll confirm full resolution in the following updates.
investigating
Our team is continuing to investigate the issue affecting GitLab Duo Agent Platform (DAP). We don't have new information to share at this time, but work is ongoing.
investigating
We're currently investigating an issue affecting GitLab Duo. Some customers using the Duo Agent Platform (DAP) may be unable to access the service and are seeing a "Usage quota exceeded" error. Our team is actively looking into the cause.
Elevated error ratio for web service
Started:
resolved
We're investigating for the root cause of elevated error rates for webservice.
You can follow the progress and updates here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22182
Jobs not being picked up/stuck pending
Started:
resolved
We've identified the root cause of some jobs not getting picked up due to runner pool exhaustion. We're working on getting more runners added to the pool.
More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145
Degraded performance affecting Duo features
Started:
resolved
We’re investigating an issue affecting GitLab Duo Agent Platform workflows across GitLab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135
Slowed pipelines and CI/CD Jobs
Started:
monitoring
We are seeing a high backlog of jobs which may be experienced as slowed pipelines and ci/cd jobs.
We will provide more information when it is available.
Elevated 5xx Errors on GitLab.com
Started:
resolved
We are seeing an increase in 5xx errors on GitLab.com and are investigating the issue.
User may experience issues on GitLab.com. We will provide updates as we have them.
Elevated error rates on GitLab.com
Started:
monitoring
Error rates have started to lower and return to normal values and we are actively monitoring the issue.
The issue is being tracked in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22103
monitoring
We are continuing to investigate the issue.
A major Redis Sidekiq cluster outage caused widespread elevated error rates and authentication failures for git, CI runners, and web services. We've performed targeted restarts and forced resets to restore service and are now seeing a drop in error rates. We are monitoring the recovery and health of the cluster.
The issue is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22103
monitoring
We have identified the cause of the elevated error rates and are working to correct the issue.
We will continue to post updates as we have them.
monitoring
We're investigating elevated error rates on GitLab.com. Some users may experience intermittent failures or degraded performance while we work to identify the cause.
Users may experience delayed pipelines or pipelines not running.
We'll share another update as soon as we have more information.
monitoring
We are seeing elevated error rates across GitLab.com and GitLab.com services.
We are investigating the issue and will continue to update as we have more information.
monitoring
We're investigating elevated error rates on GitLab.com. Some users may experience intermittent failures or degraded performance while we work to identify the cause.
We'll share another update as soon as we have more information.
500 errors accessing repositories
Started:
resolved
We are currently investigating 500 errors when accessing repositories and Gitaly errors when pushing to a repository. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041
Background processing delays
Started:
investigating
The background job backlog has mostly cleared and merge train delays should be significantly reduced. We're keeping this incident in monitoring while we implement performance improvements. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017
monitoring
We have identified the cause of the background job processing delays. We are working to identify mitigating measures.
monitoring
We are investigating an issue background jobs being processed with delay. The problem is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017.
Intermittent errors observed on GitLab Next
Started:
resolved
A configuration update may cause some intermittent error messages on GitLab Next (Canary). We have identified the cause and the fix is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008
April 2026
Small GitLab Hosted Runners
Started:
monitoring
Our team is working on configuration changes to improve resourcing. We're still seeing a job backlog and are continuing to monitor with these changes.
monitoring
Our team has identified a resource issue that has lead to a delay in pending jobs on Small GitLab Hosted Runners. Users with CI jobs tagged for small runners (saas-linux-small-amd64) might experience some delays. Our team is continuing to work on this.
monitoring
We are currently investigating issues with hosted `saas-linux-small-amd64` GitLab runners. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21936
parsing error in the vulnerability reports
Started:
monitoring
We've identified cause of the issue and are working on resolving it. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905.
monitoring
We are currently investigating issues with dependency scanning. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905`.
Degraded performance affecting Duo features
Started:
monitoring
We have increased max concurrency and are monitoring the impact on latency. We'll further investigate segfaults, which may have contributed to this incident. More details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867
monitoring
The root cause is still under investigation. We are taking steps to address the sustained request saturation in order to mitigate latency issues. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867
monitoring
We are investigating which model and provider are causing the latency. Apdex for ai-assisted service is not stable yet. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867
monitoring
We are investigating issues related to our ai-assisted service and ai-gateway. Some users may experience higher latency or errors affecting Duo features. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867
Increased error rates for web services
Started:
investigating
We detected increased error rates for web services on gitlab.com. This recovered after 5 minutes. We're monitoring the situation to ensure the service remains stable.