GitLab Outage History
Uptime record, past incidents, and downtime history for GitLab.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 56% | 25 | 11 |
| April 2026 | 90% | 30 | 3 |
| March 2026 | 100% | 31 | 0 |
| February 2026 | 100% | 5 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Elevated error ratio for web service
Started: May 21, 9:42 AM
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
May 21, 9:42 AM
Jobs not being picked up/stuck pending
Started: May 18, 11:03 AM
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
May 18, 11:03 AM
Degraded performance affecting Duo features
Started: May 15, 3:37 PM
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
May 15, 3:37 PM
Slowed pipelines and CI/CD Jobs
Started: May 13, 4:23 PM
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.
May 13, 4:23 PM
Elevated 5xx Errors on GitLab.com
Started: May 12, 9:04 PM
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.
May 12, 9:04 PM
Elevated error rates on GitLab.com
Started: May 12, 5:37 PM
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
May 12, 6:38 PM
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
May 12, 6:28 PM
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.
May 12, 6:25 PM
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.
May 12, 6:04 PM
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.
May 12, 5:56 PM
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.
May 12, 5:37 PM
500 errors accessing repositories
Started: May 11, 8:41 AM
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
May 11, 8:41 AM
Background processing delays
Started: May 7, 3:44 PM
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
May 7, 5:52 PM
monitoring
We have identified the cause of the background job processing delays. We are working to identify mitigating measures.
May 7, 4:45 PM
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.
May 7, 3:44 PM
Intermittent errors observed on GitLab Next
Started: May 6, 7:01 PM
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
May 6, 7:01 PM
April 2026
Small GitLab Hosted Runners
Started: Apr 30, 3:51 PM
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.
Apr 30, 4:38 PM
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.
Apr 30, 4:10 PM
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
Apr 30, 3:51 PM
parsing error in the vulnerability reports
Started: Apr 28, 11:05 AM
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.
Apr 28, 12:02 PM
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`.
Apr 28, 11:05 AM
Degraded performance affecting Duo features
Started: Apr 23, 8:11 AM
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
Apr 23, 10:34 AM
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
Apr 23, 9:36 AM
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
Apr 23, 8:48 AM
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
Apr 23, 8:11 AM
Increased error rates for web services
Started: Apr 23, 3:44 AM
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.
Apr 23, 3:44 AM