GitLab experienced a major incident on May 29, 2026 affecting GitLab Duo and GitLab agent server for Kubernetes (Google Compute Engine), lasting 10h 50m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 29, 2026, 12:50 PM UTC
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. 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 29, 2026, 12:50 PM UTC
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.
- identified May 29, 2026, 01:33 PM UTC
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.
- identified May 29, 2026, 01:33 PM UTC
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.
- monitoring May 29, 2026, 03:17 PM UTC
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.
- monitoring May 29, 2026, 03:17 PM UTC
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.
- monitoring May 29, 2026, 05:21 PM UTC
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
- monitoring May 29, 2026, 05:21 PM UTC
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
- identified May 29, 2026, 06:58 PM UTC
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.
- identified May 29, 2026, 06:58 PM UTC
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.
- identified May 29, 2026, 08:40 PM UTC
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.
- identified May 29, 2026, 08:40 PM UTC
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.
- monitoring May 29, 2026, 10:43 PM UTC
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.
- monitoring May 29, 2026, 10:43 PM UTC
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.
- resolved May 29, 2026, 11:41 PM UTC
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