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
Intermittent errors observed on GitLab Next
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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
Source not attested
Last archived state: monitoring
View archived record details
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
minorSource not attested
Last archived state: investigating
View archived record details
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.
