GitLab experienced a minor incident on August 3, 2026 affecting Website and Git Operations and 1 more component, lasting 9h 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 03, 2026, 02:31 PM UTC
The team is investigating an issue related to a Gitaly node. Customers may experience errors or slowness when performing git operations. For more info see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625 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
- investigating Aug 03, 2026, 02:31 PM UTC
The team is investigating an issue related to a Gitaly node. Customers may experience errors or slowness when performing git operations. For more info see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- investigating Aug 03, 2026, 02:59 PM UTC
Impact is limited to projects on a single Gitaly node. The team is currently focused on relieving pressure from the overloaded Gitaly node to mitigate impact in the affected projects. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- investigating Aug 03, 2026, 02:59 PM UTC
Impact is limited to projects on a single Gitaly node. The team is currently focused on relieving pressure from the overloaded Gitaly node to mitigate impact in the affected projects. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- investigating Aug 03, 2026, 03:57 PM UTC
The team is still working on actions to mitigate impact from the affected Gitaly node. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- investigating Aug 03, 2026, 03:57 PM UTC
The team is still working on actions to mitigate impact from the affected Gitaly node. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- monitoring Aug 03, 2026, 05:25 PM UTC
Restarting the affected Gitaly node relieved pressure on it, and error rates have dropped significantly. We're monitoring for continued stability. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.
- monitoring Aug 03, 2026, 05:25 PM UTC
Restarting the affected Gitaly node relieved pressure on it, and error rates have dropped significantly. We're monitoring for continued stability. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.
- resolved Aug 04, 2026, 12:07 AM UTC
After a period of monitoring we have seen continued Gitaly stability and consider the incident resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.