Changes / GitLab / 500 Errors due to failures in Gitaly service nodes
GitLab: Major incident: 500 Errors due to failures in Gitaly service nodes
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: full timeline of updates →
What changed
Before: not present
After: 500 Errors due to failures in Gitaly service nodes
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-02-18 20:01 UTC
Before: not present
After: 2026-02-23 17:25 UTC
Before: not present
After: Git Operations, Website
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: 500 Errors due to failures in Gitaly service nodes (this change) | Major incident |