Changes / GitLab / Errors Opening Repositories
GitLab: Major incident: Errors Opening Repositories
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: full timeline of updates →
What changed
Before: not present
After: Errors Opening Repositories
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-17 20:44 UTC
Before: not present
After: 2026-09-18 13:45 UTC
Before: not present
After: Git Operations, Website
Before: not present
After: We're investigating reports of customers unable to open projects, receiving error 500 instead.
Before: not present
After: No material updates are available at this time. Our team continues to investigate the root cause of the issue.
Before: not present
After: We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation.
Before: not present
After: A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation.
Before: not present
After: Gitaly nodes have stabilized following the completed rollback deployment. The incident has been mitigated and we remain focused on continued monitoring.
Before: not present
After: 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.
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: Errors Opening Repositories (this change) | Major incident |