GitLab experienced a major incident on May 26, 2026 affecting GitLab Duo and GitLab agent server for Kubernetes (Google Compute Engine), lasting 1h 34m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 26, 2026, 12:50 PM UTC
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 team is actively looking into the cause. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- investigating May 26, 2026, 12:50 PM UTC
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 team is actively looking into the cause.
- investigating May 26, 2026, 01:16 PM UTC
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.
- investigating May 26, 2026, 01:16 PM UTC
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.
- investigating May 26, 2026, 01:42 PM UTC
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. Customers may continue to see errors due to cache duration. We'll confirm full resolution in the following updates.
- investigating May 26, 2026, 01:42 PM UTC
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. Customers may continue to see errors due to cache duration. We'll confirm full resolution in the following updates.
- monitoring May 26, 2026, 02:15 PM UTC
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 mitigated.
- monitoring May 26, 2026, 02:15 PM UTC
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 mitigated.
- resolved May 26, 2026, 02:25 PM UTC
All metrics confirm that the issue impacting GitLab Duo Agent Platform (DAP) is fully resolved, and we're marking this incident as closed. We appreciate your patience while we worked through it.