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.
May 2026
Delays in CI job processing by runners
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: investigating
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: monitoring
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: investigating
View archived record details
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.
