GitLab experienced a minor incident on September 17, 2026 affecting Website and Git Operations and 1 more component, lasting 17h 1m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 17, 2026, 08:44 PM UTC
We're investigating reports of customers unable to open projects, receiving error 500 instead. 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 Sep 17, 2026, 08:44 PM UTC
We're investigating reports of customers unable to open projects, receiving error 500 instead. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22925.
- investigating Sep 17, 2026, 09:32 PM UTC
No material updates are available at this time. Our team continues to investigate the root cause of the issue.
- investigating Sep 17, 2026, 09:32 PM UTC
No material updates are available at this time. Our team continues to investigate the root cause of the issue.
- identified Sep 17, 2026, 09:56 PM UTC
We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.
- identified Sep 17, 2026, 09:56 PM UTC
We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.
- identified Sep 17, 2026, 11:23 PM UTC
We’re continuing mitigation efforts and have observed some recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations when accessing certain projects.
- identified Sep 17, 2026, 11:23 PM UTC
We’re continuing mitigation efforts and have observed some recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations when accessing certain projects.
- identified Sep 18, 2026, 12:29 AM UTC
We are continuing mitigation and monitoring recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations for certain projects. We will provide a further update as mitigation progresses.
- identified Sep 18, 2026, 12:29 AM UTC
We are continuing mitigation and monitoring recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations for certain projects. We will provide a further update as mitigation progresses.
- investigating Sep 18, 2026, 01:25 AM UTC
Mitigation has not yet fully restored the GitLab UI and Git operations in certain projects. We are still investigating HTTP 500 errors and will provide a further update as more information becomes available.
- investigating Sep 18, 2026, 01:25 AM UTC
Mitigation has not yet fully restored the GitLab UI and Git operations in certain projects. We are still investigating HTTP 500 errors and will provide a further update as more information becomes available.
- investigating Sep 18, 2026, 02:01 AM UTC
Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.
- investigating Sep 18, 2026, 02:01 AM UTC
Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.
- investigating Sep 18, 2026, 02:34 AM UTC
The restart of the affected Gitaly node did not improve the issue; HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. We are investigating and will provide further updates as the situation changes.
- investigating Sep 18, 2026, 02:34 AM UTC
The restart of the affected Gitaly node did not improve the issue; HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. We are investigating and will provide further updates as the situation changes.
- investigating Sep 18, 2026, 03:02 AM UTC
Further mitigation is being rolled out while we continue to investigate HTTP 500 errors affecting the GitLab UI and Git operations. We will provide further updates as the mitigation progresses.
- investigating Sep 18, 2026, 03:02 AM UTC
Further mitigation is being rolled out while we continue to investigate HTTP 500 errors affecting the GitLab UI and Git operations. We will provide further updates as the mitigation progresses.
- investigating Sep 18, 2026, 04:00 AM UTC
A further mitigation change has been applied, and we are assessing its impact. HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.
- investigating Sep 18, 2026, 04:00 AM UTC
A further mitigation change has been applied, and we are assessing its impact. HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.
- investigating Sep 18, 2026, 06:28 AM UTC
Further mitigation change are currently being applied, and we are continuing to investigate the issue. HTTP 500 errors may continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.
- investigating Sep 18, 2026, 06:28 AM UTC
Further mitigation change are currently being applied, and we are continuing to investigate the issue. HTTP 500 errors may continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.
- investigating Sep 18, 2026, 07:59 AM UTC
We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation.
- investigating Sep 18, 2026, 07:59 AM UTC
We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation.
- monitoring Sep 18, 2026, 09:01 AM UTC
A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation.
- monitoring Sep 18, 2026, 09:01 AM UTC
A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation.
- monitoring Sep 18, 2026, 11:07 AM UTC
Gitaly nodes have stabilized following the completed rollback deployment. The incident has been mitigated and we remain focused on continued monitoring.
- monitoring Sep 18, 2026, 11:07 AM UTC
Gitaly nodes have stabilized following the completed rollback deployment. The incident has been mitigated and we remain focused on continued monitoring.
- resolved Sep 18, 2026, 01:45 PM UTC
The incident has been resolved following the completion of the rollback deployment across the Gitaly nodes. All nodes have returned to a stable state, repository access has been restored. Incident team is currently investigating the root cause.