What Happened
GitLab experienced an outage on May 26, 2026. The incident lasted approximately 1 hour 35 minutes.
Complete DevOps platform delivered as a single application covering the entire software development lifecycle from planning to monitoring.
Timeline
| Time (UTC) | Status | Details |
|---|---|---|
| 14:15 | Investigating | The 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:42 | Investigating | We'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:16 | Investigating | Our 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:50 | Investigating | We'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... |
| 14:32 | Resolved | All systems operational |
Impact
The outage lasted approximately 1 hour 35 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
- View GitLab live status and outage history
- Set up alerts to get notified instantly next time GitLab has an issue
- Compare GitLab reliability with other services
---
This post was automatically generated by ServiceAlert.ai's monitoring system. View live status →