Gitlab outage history

September 8, 2026 08:54 UTC Identified - Starting a new chat with an agent from the AI catalog does not work, and the websocket connection is immediately dropped. We are reverting the merge request that introduced the failure. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880. September 8, 2026 09:57 UTC Resolved - The merge request that introduced the failure was reverted, and custom/catalog agents are working again. More information is available in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880.

August 27, 2026 11:46 UTC Investigating - There are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to restore normal service. August 27, 2026 11:53 UTC Monitoring - The issue has been identified and resolved. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807 August 27, 2026 15:34 UTC Resolved - Performance remains stable and prevention steps are being implemented. Find more information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807

August 27, 2026 07:12 UTC Investigating - We are currently investigating reports of connectivity issues affecting some users accessing GitLab.com. August 27, 2026 07:41 UTC Monitoring - We have identified a temporary filtering event by an upstream provider that affected some traffic to GitLab.com. The event has ended, and we are working with our service provider to investigate the cause and prevent recurrence. We are monitoring the situation to ensure that services have returned to normal. August 27, 2026 09:35 UTC Resolved - Our upstream provider mitigated a genuine distributed HTTP DDoS attack against gitlab.com, but incorrectly blocked a small amount of legitimate traffic. This has now been resolved.

August 25, 2026 09:59 UTC Investigating - We are currently investigating reports of slowness and 502 errors. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 August 25, 2026 13:43 UTC Investigating - Slowness & 502s have been bursty with not much impact. A revert MR is under way while we are investigating other possible root causes. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 August 25, 2026 14:48 UTC Monitoring - We have not seen active user impact for several hours and we have identified the possible root cause. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 August 25, 2026 18:34 UTC Monitoring - We continue to monitor and have not observed any active user impact. We are working towards a permanent fix and will provide our next update once it has been implemented. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 August 26, 2026 00:12 UTC Resolved - The fix has been implemented and the issue is now resolved. We have not observed any active user impact. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

August 24, 2026 21:22 UTC Investigating - 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 August 24, 2026 21:37 UTC Identified - We have identified a recent change believed to be contributing to the deployment failures affecting KAS. We are actively reverting this change and will provide an update once complete. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777 August 24, 2026 22:28 UTC Monitoring - The rollback has been completed and we are actively monitoring to confirm resolution of the deployment failures affecting KAS. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777 August 24, 2026 22:45 UTC Resolved - The deployment failures affecting the GitLab Agent for Kubernetes (KAS) have been resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

August 21, 2026 15:56 UTC Monitoring - 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 August 21, 2026 16:25 UTC Resolved - The elevated 403 errors affecting GitLab.com have been resolved and error rates have returned to normal levels. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762

August 18, 2026 13:55 UTC 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 August 18, 2026 14:16 UTC 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 August 18, 2026 14:31 UTC 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 August 18, 2026 14:49 UTC Monitoring - 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 August 18, 2026 16:11 UTC Monitoring - 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 August 18, 2026 17:30 UTC Resolved - The error rate remains within normal thresholds and the issue is now resolved. Further details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

August 13, 2026 13:58 UTC Investigating - 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 August 13, 2026 15:22 UTC 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 August 13, 2026 16:48 UTC 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 August 13, 2026 17:47 UTC Resolved - The queue of pending jobs on the affected runners has returned to normal and has stayed at that level. This incident is now resolved. Please open a ticket with support if you are still seeing job delays. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702

August 6, 2026 14:01 UTC Investigating - 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 August 6, 2026 14:26 UTC Identified - 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 August 6, 2026 16:22 UTC Resolved - We're seeing consistent background job and webhook delivery. The issue is now resolved.

August 5, 2026 22:13 UTC Investigating - We're investigating reports of pipelines failing and becoming stuck. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654. August 5, 2026 22:39 UTC Investigating - 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. August 5, 2026 23:26 UTC Identified - 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. August 5, 2026 23:47 UTC Resolved - We've applied mitigations that have stabilized the job queue. The issue is now resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.

August 4, 2026 16:42 UTC Investigating - 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. August 4, 2026 18:49 UTC Investigating - Our investigation is ongoing. We will provide another update by 21:00 UTC. August 4, 2026 21:07 UTC Identified - We've traced the issue to a recent network change and are preparing a fix. Another update will be provided by 23:00 UTC. August 4, 2026 23:14 UTC Identified - 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. August 5, 2026 03:26 UTC Monitoring - A fix has been deployed and checks have confirmed that unexpected IP addresses are no longer being used. August 5, 2026 15:19 UTC Resolved - Webhook delivery failures have subsided in logs, and customer reports indicate no further errors. This incident is considered resolved.

August 4, 2026 13:56 UTC Investigating - 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 August 4, 2026 16:30 UTC Identified - 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. August 4, 2026 17:54 UTC Resolved - Duo Code Review sessions on GitLab.com have returned to normal operation. This issue is now resolved.

August 3, 2026 14:31 UTC Investigating - 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 August 3, 2026 14:59 UTC Investigating - 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 August 3, 2026 15:57 UTC Investigating - 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 August 3, 2026 17:25 UTC 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. August 4, 2026 00:07 UTC Resolved - After a period of monitoring we have seen continued Gitaly stability and consider the incident resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.

July 27, 2026 20:09 UTC Investigating - We observed a spike in 5xx errors on GitLab.com. These have subsided, but we are investigating the root cause. July 27, 2026 20:28 UTC Monitoring - 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 July 27, 2026 21:11 UTC Resolved - We have continued to observe normal error rates. We will now be marking this incident as resolved. Details surrounding the incident can be seen here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22579

July 22, 2026 21:47 UTC Investigating - We are currently receiving reports and investigating issues with signing into GitLab.com. We will provide more information once it is available. July 22, 2026 23:08 UTC Monitoring - We are still monitoring the situation with possible issues logging into GitLab.com and will provide further updates when they are available. July 23, 2026 00:49 UTC Monitoring - 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 July 24, 2026 03:50 UTC Resolved - Earlier login problems have been resolved and logins are working normally again. This incident is now considered closed. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22551

July 17, 2026 16:10 UTC Investigating - 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. July 17, 2026 16:26 UTC Investigating - Our team is actively investigating the root cause of this issue. We'll continue to share updates as we learn more. July 17, 2026 16:44 UTC Investigating - 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. July 17, 2026 17:09 UTC Investigating - 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. July 17, 2026 17:22 UTC Monitoring - 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. July 17, 2026 17:36 UTC Resolved - 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.

July 15, 2026 14:12 UTC Identified - 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. July 15, 2026 15:33 UTC Identified - 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. July 15, 2026 16:21 UTC Identified - Work to resolve the package registry issue is ongoing. During this time, some users may continue to experience slow or unsuccessful Omnibus package downloads. July 15, 2026 16:54 UTC Identified - 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. July 15, 2026 17:25 UTC Identified - No material updates to report at this time. We are continuing to investigate the current issue and engineers are working to determine remediation steps. July 15, 2026 18:19 UTC Identified - Mitigation efforts are ongoing to address the issue affecting package pulls from our registry. Slow or failed Omnibus package downloads may still occur. July 15, 2026 18:57 UTC Identified - 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. July 15, 2026 19:36 UTC Identified - 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. July 15, 2026 20:12 UTC Identified - 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. July 15, 2026 20:44 UTC Identified - Mitigation efforts remain in progress. We're continuing to monitor the implementation and will provide another update once additional progress has been made. July 15, 2026 21:29 UTC Resolved - Mitigation efforts have been successfully completed, and service has returned to normal. This incident has been resolved.

July 14, 2026 22:47 UTC Investigating - 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 July 14, 2026 23:02 UTC Identified - 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 July 14, 2026 23:37 UTC Identified - 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 July 15, 2026 00:00 UTC Identified - The revert remains in progress. Additional updates will be shared in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22519 July 15, 2026 00:24 UTC Monitoring - 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 July 15, 2026 00:37 UTC Monitoring - 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 July 15, 2026 00:47 UTC Resolved - 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

July 7, 2026 17:47 UTC Identified - 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 July 7, 2026 17:48 UTC Identified - 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 July 7, 2026 18:35 UTC Identified - The fix is still in progress, no updates at this time. More: https://gitlab.com/gitlab-org/gitlab/-/work_items/605117 July 7, 2026 19:29 UTC Identified - 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 July 7, 2026 20:00 UTC Identified - 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 July 7, 2026 20:42 UTC Identified - No further updates at this time. The merge request is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470 July 7, 2026 22:40 UTC Identified - 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 July 7, 2026 23:02 UTC 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 July 8, 2026 15:59 UTC Resolved - The fix has been completed in production. This incident is now resolve. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22470

July 1, 2026 13:14 UTC Investigating - 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 July 1, 2026 13:58 UTC Investigating - We are continuing to investigate and look into CI pipelines being stuck in pending state. July 1, 2026 14:04 UTC Resolved - Incident has now been mitigated. CI pipelines are now resuming. Engineers will continue to monitor this recovery.