# GitLab: Major incident: 500 Errors due to failures in Gitaly service nodes

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

Incident page (full timeline): [500 Errors due to failures in Gitaly service nodes](https://rewindex.com/company/gitlab/incidents/69961a7fe8084605f194de0c.md)
## What changed

**1. Added: Title**

```diff
+ 500 Errors due to failures in Gitaly service nodes
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2026-02-18 20:01 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-02-23 17:25 UTC
```

**6. Added: Affected components**

```diff
+ Git Operations, Website
```

**7. Added: Update** (investigating) · 2026-02-18 20:01 UTC

```diff
+ GitLab is investigating ongoing issues with several Gitaly nodes that are causing intermittent 500 errors. We are working to identify the cause of instability on these nodes. Our investigation is ongoing; we will post again when we have material updates or in two hours with a status update.
```

**8. Added: Update** (investigating) · 2026-02-18 22:37 UTC

```diff
+ The Gitaly team continues to investigate the performance issues on these Gitaly nodes and are still working to identify a root cause. We will update again in about two hours.
```

**9. Added: Update** (investigating) · 2026-02-19 00:38 UTC

```diff
+ The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes and are still working to identify a root cause. We will post an update within the next four hours.
```

**10. Added: Update** (investigating) · 2026-02-19 04:38 UTC

```diff
+ The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We are still working to identify a root cause and will post an update within the next four hours if not sooner.
```

**11. Added: Update** (investigating) · 2026-02-19 08:30 UTC

```diff
+ The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We are still working to identify a root cause and mitigation steps.
```

**12. Added: Update** (investigating) · 2026-02-19 20:26 UTC

```diff
+ The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We are still working to identify a root cause and mitigation steps.
```

**13. Added: Update** (investigating) · 2026-02-20 00:39 UTC

```diff
+ The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We are still working to identify a root cause and mitigation steps. A status update will be made within the next 8 hours.
```

**14. Added: Update** (investigating) · 2026-02-20 08:25 UTC

```diff
+ The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We have not seen issues within the past 24 hours and continue to monitor closely. We are still working to identify a root cause. A status update will be made within the next 8 hours.
```

**15. Added: Update** (investigating) · 2026-02-20 18:02 UTC

```diff
+ The Gitaly team continues to investigate and mitigate the performance issues on affected Gitaly nodes. We have not seen issues within the past 24 hours and continue to monitor closely. We are still working to identify a root cause. A status update will be made within the next 8 hours.
```

**16. Added: Update** (monitoring) · 2026-02-21 02:11 UTC

```diff
+ The Gitaly team has applied mitigations to address performance issues and will monitor over the weekend. We have confirmed that current performance issues only affect internal GitLab operations. Customer activity should not be impacted at this time. With the current impact and mitigation in place, we will resume status updates for this incident on Monday, February 23rd at 17:00 UTC
```

**17. Added: Update** (resolved) · 2026-02-23 17:25 UTC

```diff
+ After continued monitoring over the weekend, performance has remained stable and within normal levels. As systems are operating as expected, this incident is now marked as resolved.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-02-18 20:01 UTC | Major incident: 500 Errors due to failures in Gitaly service nodes (this change) | major |

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/i8a8f14f01d8db4 · Markdown: https://rewindex.com/change/i8a8f14f01d8db4.md · JSON: https://rewindex.com/api/v1/changes/i8a8f14f01d8db4 · Generated 2026-10-18T10:23:41.570Z