# GitLab: Critical incident: Issues with GitLab Duo in merge requests

**Summary:** _summary pending_
- Kind: Major incident · Label: critical (vendor)
- Changed: 2026-05-29 12:50 UTC · Detected: 2026-10-18 05:08 UTC
- [Source: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6a198b7a50c7630597c4d950](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6a198b7a50c7630597c4d950)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)
- Versions: before (none: first archived) → after incident\_version:188/6a198b7a50c7630597c4d950@8b9a390e8231
- Change 1 of 1 for this incident

Incident page (full timeline): [Issues with GitLab Duo in merge requests](https://rewindex.com/company/gitlab/incidents/6a198b7a50c7630597c4d950.md)
## What changed

**1. Added: Title**

```diff
+ Issues with GitLab Duo in merge requests
```

**2. Added: Impact**

```diff
+ critical
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2026-05-29 12:50 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-05-29 23:41 UTC
```

**6. Added: Affected components**

```diff
+ GitLab Duo
```

**7. Added: Update** (investigating) · 2026-05-29 12:50 UTC

```diff
+ 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.
```

**8. Added: Update** (identified) · 2026-05-29 13:33 UTC

```diff
+ 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.
```

**9. Added: Update** (monitoring) · 2026-05-29 15:17 UTC

```diff
+ 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.
```

**10. Added: Update** (monitoring) · 2026-05-29 17:21 UTC

```diff
+ 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
```

**11. Added: Update** (identified) · 2026-05-29 18:58 UTC

```diff
+ 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.
```

**12. Added: Update** (identified) · 2026-05-29 20:40 UTC

```diff
+ 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.
```

**13. Added: Update** (monitoring) · 2026-05-29 22:43 UTC

```diff
+ 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.
```

**14. Added: Update** (resolved) · 2026-05-29 23:41 UTC

```diff
+ 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
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-05-29 12:50 UTC | Critical incident: Issues with GitLab Duo in merge requests (this change) | critical |

All GitLab changes: [timeline](https://rewindex.com/company/gitlab/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/iec00b5f187d728 · Markdown: https://rewindex.com/change/iec00b5f187d728.md · JSON: https://rewindex.com/api/v1/changes/iec00b5f187d728 · Generated 2026-10-18T10:23:45.767Z