GitLab incident

Degraded performance affecting Duo features

Minor Resolved View vendor source →

GitLab experienced a minor incident on May 15, 2026 affecting GitLab Duo and GitLab agent server for Kubernetes (Google Compute Engine), lasting 2h 33m. The incident has been resolved; the full update timeline is below.

Started
May 15, 2026, 03:37 PM UTC
Resolved
May 15, 2026, 06:11 PM UTC
Duration
2h 33m
Detected by Pingoru
May 15, 2026, 03:37 PM UTC

Affected components

GitLab DuoGitLab agent server for Kubernetes (Google Compute Engine)

Update timeline

  1. investigating May 15, 2026, 03:37 PM UTC

    We’re investigating an issue affecting GitLab Duo Agent Platform workflows across GitLab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135 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

  2. investigating May 15, 2026, 03:37 PM UTC

    We’re investigating an issue affecting GitLab Duo Agent Platform workflows across GitLab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

  3. investigating May 15, 2026, 04:07 PM UTC

    We’re continuing to investigate an issue affecting GitLab Duo Agent Platform workflows on GitLab.com and GitLab Dedicated. We have identified a likely cause and are testing a revert. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

  4. investigating May 15, 2026, 04:07 PM UTC

    We’re continuing to investigate an issue affecting GitLab Duo Agent Platform workflows on GitLab.com and GitLab Dedicated. We have identified a likely cause and are testing a revert. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

  5. identified May 15, 2026, 04:32 PM UTC

    We’ve identified the issue affecting GitLab Duo Agent Platform workflows across GitLab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” We are working on a revert to correct the issue. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

  6. identified May 15, 2026, 04:32 PM UTC

    We’ve identified the issue affecting GitLab Duo Agent Platform workflows across GitLab.com, and GitLab Dedicated. Some code review and custom flows may fail or show “Session failed.” We are working on a revert to correct the issue. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

  7. identified May 15, 2026, 05:05 PM UTC

    We have identified the cause and have created an MR to revert. We are waiting for that MR to deploy. We will provide further updates once that has merged and deployed. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

  8. identified May 15, 2026, 05:05 PM UTC

    We have identified the cause and have created an MR to revert. We are waiting for that MR to deploy. We will provide further updates once that has merged and deployed. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

  9. monitoring May 15, 2026, 05:44 PM UTC

    The revert has been deployed and we are now monitoring the situation. Error rates look to be returning to normal. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

  10. monitoring May 15, 2026, 05:44 PM UTC

    The revert has been deployed and we are now monitoring the situation. Error rates look to be returning to normal. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135

  11. resolved May 15, 2026, 06:11 PM UTC

    The revert has been merged and deployed and we are seeing error rates return to normal and flows running. This issue has been resolved. More details at gitlab.com/gitlab-com/gl-infra/production/-/work_items/22135