Gitlab Status

June 18, 2026 14:02 UTC Identified - We've identified a recent code change as the likely cause of elevated Sidekiq job execution errors on the low-urgency-cpu-bound shard, which may delay processing of some background jobs. Mitigations are in progress. We'll continue to update as soon as the mitigation is merged and deployed. June 18, 2026 16:48 UTC Resolved - A recent code change was rolled back and the error rates have subsided since it was merged. Our team has been monitoring and performance has returned to expected levels. This incident is now resolved. https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22335

June 13, 2026 03:53 UTC Monitoring - Claude Fable is not available through GitLab.com. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9 June 13, 2026 04:13 UTC Monitoring - Although Claude Fable is not available on GitLab.com, it still appears in the model selection menu. Customers who are currently using it should manually select a different model. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9 June 13, 2026 07:22 UTC Monitoring - The revert MR to remove the Claude Fable was merged and deployed to production. While the GitLab.com service is back to normal, Fable remains unavailable due to an upstream suspension. Customers need continue to select a different model. We are monitoring the situation closely. June 13, 2026 07:56 UTC Resolved - GitLab.com is currently operating normally. The issue has been resolved. For more info, please see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22308

June 11, 2026 07:08 UTC Investigating - We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information. June 11, 2026 07:11 UTC Investigating - We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information. June 11, 2026 07:23 UTC Investigating - We changed the status title to reflect the intermittent nature of this incident. We'll share another update as soon as we have more information. June 11, 2026 08:06 UTC Monitoring - The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently. June 11, 2026 12:16 UTC Monitoring - GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database, and we are continuing to monitor closely. June 11, 2026 20:19 UTC Resolved - GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database and the issue should be resolved now.

June 8, 2026 09:17 UTC Investigating - The GitLab.com credit dashboard fails to load, displaying the error message: "An error occurred while fetching data". This issue is under investigation. June 8, 2026 12:15 UTC Monitoring - Mitigation has been applied and GitLab Credits dashboards appear to be loading again. We’ll leave affected components marked as Partial Service Disruption as we monitor error rates closely to ensure the service remains stable. June 8, 2026 13:22 UTC Resolved - GitLab Credits dashboards are operating normally again. The issue has been resolved.

June 5, 2026 11:58 UTC Investigating - We are investigating an issue where CI jobs are not processing. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 June 5, 2026 12:08 UTC Identified - We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 June 5, 2026 12:51 UTC Identified - We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 June 5, 2026 12:53 UTC Identified - We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 June 5, 2026 13:04 UTC Identified - The change has been reverted and we are seeing that error rates are recovering. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 June 5, 2026 13:15 UTC Monitoring - Error rates have recovered back to normal levels and we started processing jobs again. We expect that the job queue should be processed over the next 30 minutes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 June 5, 2026 13:46 UTC Resolved - The job queue is now cleared and we do not expect any further customer impact. This is considered resolved. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

June 4, 2026 16:05 UTC Investigating - We are investigating an issue where Duo Agent Platform Flows, including Duo Code Review, are not working on some projects. See issue for more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 June 4, 2026 16:23 UTC Identified - We have identified the root cause of the recent Duo Agent Platform Flow failures and are deploying a fix. Customers should begin seeing improvements as the deployment completes. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 June 4, 2026 16:52 UTC Identified - We have merged a fix for the Duo Agent Platform Flow failures and it is awaiting deployment. Deployment is expected to take several hours. We will share our next update once the deployment is complete. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 June 5, 2026 05:37 UTC Monitoring - Error rates have decreased significantly following the fix. We are continuing to monitor the situation. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 June 5, 2026 07:51 UTC Resolved - This issue has been resolved and error rates have returned to normal. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

June 3, 2026 14:39 UTC Investigating - We are investigating an issue where Duo Agent Platform Flows fail to start when used with the default Docker image. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241 June 3, 2026 15:59 UTC Identified - We have identified the issue and we're rolling out a fix to production. Customers should start to see improvement as deployment completes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241 June 3, 2026 17:53 UTC Resolved - The fix has been deployed, and Duo Agent Platform Flows are working as expected. We will now mark this incident as resolved. For details, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22241

May 29, 2026 12:50 UTC Investigating - We're investigating an issue where customers using `@GitLabDuo` mentions in merge requests are receiving access errors. Impact has been reported across GitLab.com, Dedicated, and Self-Managed. Our team is actively investigating. We'll share another update as soon as we have more information. May 29, 2026 13:33 UTC Identified - We've identified a likely root cause for the `@GitLabDuo` access errors in merge requests and are preparing a revert MR. We'll share another update once it's deployed. May 29, 2026 15:17 UTC Monitoring - A fix has been deployed via a revert MR. We're moving the incident to Monitoring and will share another update once we can confirm it's fully resolved. May 29, 2026 17:21 UTC Monitoring - We are still monitoring the deployed fix. We will share another update once we can confirm it's fully resolved. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22228 May 29, 2026 18:58 UTC Identified - After monitoring, our team is still seeing some failures which is prompting additional investigation. While there has been a drop in errors, some users continue to experience issues. May 29, 2026 20:40 UTC Identified - No material updates at this time. Our team is still seeing some failures which prompted additional investigation. While there has been a drop in errors, some users continue to experience issues. May 29, 2026 22:43 UTC Monitoring - A fix has now been deployed that should remediate the errors. We will continue to monitor, and as long as error rates remain low, we will resolve the incident. May 29, 2026 23:41 UTC Resolved - We're no longer seeing errors related to this in the logs, so we are resolving this incident. If you're still experiencing errors when using `@GitLabDuo` mentions in merge requests, please contact support. https://support.gitlab.com

May 27, 2026 07:31 UTC Investigating - We receive report regarding git operation error. Our Gitaly team is investigating the problem. See more detail: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217 May 27, 2026 08:17 UTC Investigating - Our Gitaly team is continuing to investigate the reported Git operation errors. We don't have new information to share at this time, but work is ongoing. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217 May 27, 2026 08:47 UTC Investigating - Investigation into the Git operation errors is ongoing. The team is reviewing logs and has identified a few potential culprits, though we haven't yet confirmed whether any of them are causing the incident. We'll share another update as soon as we have more. May 27, 2026 09:27 UTC Monitoring - We've implemented mitigation rules and are seeing a reduced rate of errors. All signals indicate the incident is resolved. We'll continue monitoring for a bit before marking it as fully resolved. May 27, 2026 09:55 UTC Resolved - The Git operation errors have been resolved and metrics have returned to normal. Thank you for your patience throughout the incident. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22217

May 26, 2026 16:16 UTC Identified - Some users may see jobs pending while waiting for runners. The team is currently working on the fix. We will update in 30 minutes. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212 May 26, 2026 16:43 UTC Monitoring - The fix has been deployed. Shared runners should be picking up jobs normally. We will continue to monitor the situation. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212 May 26, 2026 17:21 UTC Resolved - The fix has been deployed, and hared runners are picking up jobs normally. We will now mark this incident as resolved. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22212