Unofficial GitLab Status

Investigating July 22, 2026 21:47 UTC
We are currently receiving reports and investigating issues with signing into GitLab.com. We will provide more information once it is available.

Monitoring July 22, 2026 23:08 UTC
We are still monitoring the situation with possible issues logging into GitLab.com and will provide further updates when they are available.

Monitoring July 23, 2026 00:49 UTC
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

Investigating July 17, 2026 16:10 UTC
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.

Investigating July 17, 2026 16:26 UTC
Our team is actively investigating the root cause of this issue. We'll continue to share updates as we learn more.

Investigating July 17, 2026 16:44 UTC
We continue to investigate the root cause of this issue. There are no material updates at this time, and we'll share additional information as it becomes available.

Investigating July 17, 2026 17:09 UTC
We're seeing signs of recovery, but our investigation into the root cause remains ongoing. We'll continue to provide updates as more information becomes available.

Monitoring July 17, 2026 17:22 UTC
We're seeing service recover and error rates return to expected levels. We'll continue to monitor the environment to ensure the recovery is sustained.

Resolved July 17, 2026 17:36 UTC
We've identified and mitigated the root cause of this issue. Service has remained stable throughout the monitoring period, and this incident is now resolved.

Identified July 15, 2026 14:12 UTC
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.

Identified July 15, 2026 15:33 UTC
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.

Identified July 15, 2026 16:21 UTC
Work to resolve the package registry issue is ongoing. During this time, some users may continue to experience slow or unsuccessful Omnibus package downloads.

Identified July 15, 2026 16:54 UTC
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.

Identified July 15, 2026 17:25 UTC
No material updates to report at this time. We are continuing to investigate the current issue and engineers are working to determine remediation steps.

Identified July 15, 2026 18:19 UTC
Mitigation efforts are ongoing to address the issue affecting package pulls from our registry. Slow or failed Omnibus package downloads may still occur.

Identified July 15, 2026 18:57 UTC
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.

Identified July 15, 2026 19:36 UTC
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.

Identified July 15, 2026 20:12 UTC
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.

Identified July 15, 2026 20:44 UTC
Mitigation efforts remain in progress. We're continuing to monitor the implementation and will provide another update once additional progress has been made.

Resolved July 15, 2026 21:29 UTC
Mitigation efforts have been successfully completed, and service has returned to normal. This incident has been resolved.

Investigating July 14, 2026 22:47 UTC
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

Identified July 14, 2026 23:02 UTC
We have identified the problematic change causing this behavior and are working to revert it. Details will be shared in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

Identified July 14, 2026 23:37 UTC
We're continuing to work on reverting the change causing this issue. Details will be shared in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

Identified July 15, 2026 00:00 UTC
The revert remains in progress. Additional updates will be shared in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

Monitoring July 15, 2026 00:24 UTC
Deployment for the revert has reached production. Manual verification is successful with error rates trending down. We are continuing to monitor. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

Monitoring July 15, 2026 00:37 UTC
We are monitoring the situation to ensure that services have returned to normal. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

Resolved July 15, 2026 00:47 UTC
We are seeing error rates return to normal. This issue has been resolved. Details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519

Identified July 7, 2026 17:47 UTC
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

Identified July 7, 2026 17:48 UTC
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

Identified July 7, 2026 18:35 UTC
The fix is still in progress, no updates at this time. More: https://gitlab.com/gitlab-org/gitlab/-/work_items/605117

Identified July 7, 2026 19:29 UTC
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

Identified July 7, 2026 20:00 UTC
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

Identified July 7, 2026 20:42 UTC
No further updates at this time. The merge request is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

Identified July 7, 2026 22:40 UTC
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 July 7, 2026 23:02 UTC
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

Resolved July 8, 2026 15:59 UTC
The fix has been completed in production. This incident is now resolve. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

Investigating July 1, 2026 13:14 UTC
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

Investigating July 1, 2026 13:58 UTC
We are continuing to investigate and look into CI pipelines being stuck in pending state.

Resolved July 1, 2026 14:04 UTC
Incident has now been mitigated. CI pipelines are now resuming. Engineers will continue to monitor this recovery.

Investigating June 30, 2026 21:53 UTC
We are investigating errors with code suggestion not completing.

Investigating June 30, 2026 22:08 UTC
We are continuing to investigate the issue, but it appears to be isolated to specific models and we recommend for the time being switching to Claude Sonnet 4.5 for code completion while we continue to investigate the matter. Details on how to do that can be found at https://docs.gitlab.com/user/gitlab_duo/model_selection/#select-a-model-for-a-feature

Identified June 30, 2026 23:06 UTC
We have identified the issue and are pushing a fix. While this fix is pushed we still recommend switching to Claude Sonnet 4.5 until the fix is fully pushed.

Monitoring June 30, 2026 23:30 UTC
The fix is pushed and systems appear to be operating normally. We are monitoring the situation to ensure that services have returned to normal.

Resolved June 30, 2026 23:59 UTC
Operations have returned to normal and this issue is resolved.

Investigating June 30, 2026 16:08 UTC
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

Investigating June 30, 2026 16:44 UTC
We are continuing to investigate and look into the increased errors on GitLab.com

Identified June 30, 2026 16:52 UTC
We have identified the cause of the increased error rate and are taking corrective action and monitoring the incident.

Identified June 30, 2026 17:39 UTC
We are continuing to investigate and work to resolve the degraded performance on GitLab.com

Monitoring June 30, 2026 18:26 UTC
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.

Resolved June 30, 2026 19:46 UTC
This issue is resolved and performance on GitLab.com has returned to normal.

Investigating June 30, 2026 08:52 UTC
We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root cause.

Identified June 30, 2026 09:37 UTC
We have identified that the sidekiq workers processing the jobs are getting deferred. The team is working on identifying the remediation steps.

Identified June 30, 2026 10:51 UTC
No material updates to report. We are continuing to investigate the current issue and engineers are working to determine remediation steps.

Identified June 30, 2026 11:19 UTC
Our engineers are still investigating the issue but jobs are starting to be processed with a delay. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22412

Monitoring June 30, 2026 11:39 UTC
Queues and runner backlog are trending back towards normal, while systems continue to work through the remaining backlog. Engineers are continuing to monitor this.

Resolved June 30, 2026 12:07 UTC
Incident has now been mitigated and runner backlogs are now back to normal. CI pipelines are now resuming. Engineers will continue to monitor this recovery.

Investigating June 23, 2026 17:33 UTC
We are investigating ongoing errors when attempting to interact with repositories via SSH. HTTPS does not appear to be impacted at this time. We are investigating. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

Identified June 23, 2026 17:52 UTC
We have identified the problematic change causing this behavior and are working to revert it. Details will be posted in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

Identified June 23, 2026 18:09 UTC
We are still working to revert this problematic change as quickly as possible. Once reverted, we will post an update here. Details will be made available in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

Monitoring June 23, 2026 18:25 UTC
We've addressed the underlying issue and are observing SSH interactions succeed. We will place this incident in a monitoring state as we keep an eye on things. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364

Resolved June 23, 2026 19:52 UTC
We have continued to observe successful SSH interactions after implementing our mitigating changes. We will now mark this as resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364