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.
August 2026
Investigating GitLab Agent for Kubernetes (KAS) Deployment Failures
Source not attested
Last archived state: resolved
View archived record details
Google Compute EngineGitLab agent server for Kubernetes
resolved
We are currently investigating reports of deployment failures affecting GitLab Agent for Kubernetes (KAS). Our team is actively looking into the root cause and will provide updates as the investigation progresses. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777
403 errors across GitLab.com
minorSource not attested
Last archived state: investigating
View archived record details
Google Compute EngineWebsiteGit OperationsCI/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
minorSource not attested
Last archived state: investigating
View archived record details
Google Compute EngineWebsiteAPIGit OperationsCI/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
Source not attested
Last archived state: resolved
View archived record details
Google Compute EngineBackground 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
minorSource not attested
Last archived state: monitoring
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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