Companies / GitLab / incidents

GitLab: Issues with GitLab Duo in merge requests

Impact: criticalStatus: resolvedStarted Resolved (11 h)8 updatesSource: status.gitlab.com (opens in new tab)

Affected components: GitLab Duo

Timeline of updates

  1. investigating

    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.

  2. identified

    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.

  3. monitoring

    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.

  4. monitoring

    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

  5. identified

    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.

  6. identified

    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.

  7. monitoring

    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.

  8. resolved

    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

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab). GitLab profile · Recent GitLab incidents · Markdown · JSON