2026-05-11: 500 errors when trying to access itlab-org/frontend/renovate-gitlab-bot project
# 500 errors when trying to access itlab-org/frontend/renovate-gitlab-bot project (Severity 3)
Problem: 500 errors occurred when accessing several GitLab projects, affecting both web access and Git operations.
Impact: Users were unable to access multiple GitLab projects, including gitlab-org/frontend/renovate-gitlab-bot and gitlab-com/gl-infra/autolabels, both via the web and through Git operations (commit and push). At least four customer support tickets were reported. The outage started around 8:15am UTC, with partial recovery by 8:33am UTC. All affected user-facing projects are now accessible and support tickets have been closed.
Causes: A Gitaly process was stuck in the reload process, old process was not accepting new requests, the new process was never launched. There were no code changes in the recent Gitaly deployment, so the issue was not caused by new code.
Response strategy: We restarted the Gitaly process (not the node); when a standard restart failed, the process was killed and started again, restoring service. Status updates have been posted externally. A new deployment involving a Gitaly reload will proceed to confirm stability, and the team remains in monitoring until stability is verified.
_This ticket was created to track_ [_INC-9984_](https://app.incident.io/gitlab/incidents/9984)_, by_ [_incident.io_](https://app.incident.io) 🔥
issue