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.
July 2026
Elevated error rates on GitLab.com
minorSource not attested
Last archived state: investigating
View archived record details
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
minorSource not attested
Last archived state: investigating
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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)
minorSource not attested
Last archived state: monitoring
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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
Source not attested
Last archived state: monitoring
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
resolved
We are investigating errors with code suggestion not completing.
500 errors, CI checkout failures and slow page loads
minorSource not attested
Last archived state: monitoring
View archived record details
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.
Source not attested
Last archived state: resolved
View archived record details
resolved
We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root cause.
