What Happened

GitLab experienced an outage on May 29, 2026. The incident lasted approximately 10 hours 55 minutes.

Complete DevOps platform delivered as a single application covering the entire software development lifecycle from planning to monitoring.

Timeline

Time (UTC)StatusDetails
22:43InvestigatingA 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.
20:40InvestigatingNo 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.
18:58InvestigatingAfter 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.
17:21InvestigatingWe 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
15:17InvestigatingA 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.
13:33InvestigatingWe'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.
12:50InvestigatingWe'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 ...
23:46ResolvedAll systems operational

Impact

The outage lasted approximately 10 hours 55 minutes. GitLab runs on Google Cloud (GCP), AWS — check those status pages if you experienced cascading issues.

Resolution

GitLab has recovered and is now operational.

What To Do Next

---

This post was automatically generated by ServiceAlert.ai's monitoring system. View live status →