What Happened

GitLab experienced an outage on May 27, 2026. The incident lasted approximately 2 hours 25 minutes.

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

Timeline

Time (UTC)StatusDetails
14:15InvestigatingThe cache is refreshed for some users, and we've received confirmation from a few customers that DAP is working again for them. We're keeping a close eye on metrics before marking this as fully mit...
13:42InvestigatingWe've identified a feature flag on the Customers Portal as the likely cause of the issue affecting GitLab DAP. The flag has been disabled, and we're monitoring logs and metrics for recovery. Custom...
13:16InvestigatingOur team is continuing to investigate the issue affecting GitLab Duo Agent Platform (DAP). We don't have new information to share at this time, but work is ongoing.
12:50InvestigatingWe're currently investigating an issue affecting GitLab Duo. Some customers using the Duo Agent Platform (DAP) may be unable to access the service and are seeing a "Usage quota exceeded" error. Our...
16:16ResolvedSome 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_ite...
07:31ResolvedWe 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
10:02ResolvedAll systems operational

Impact

The outage lasted approximately 2 hours 25 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 →