GitLab incident

500 errors accessing repositories

Resolved after 2 hours 34 minutes, affecting Website and Git Operations and 1 more, on May 11, 2026.

resolved May 11, 2026, 11:16 AM UTC

The issue has been resolved. The 500 errors when accessing repositories should not seen anymore and affected Git operations should work as expected. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041

Started
May 11, 2026, 08:41 AM UTC
Resolved
May 11, 2026, 11:16 AM UTC
Duration
2h 34m
Detected by Pingoru
May 11, 2026, 08:41 AM UTC

Affected components

WebsiteGit OperationsGitLab agent server for Kubernetes (GitLab agent server for Kubernetes — Google Compute Engine)

Update timeline

  1. investigating May 11, 2026, 08:41 AM UTC

    We are currently investigating 500 errors when accessing repositories and Gitaly errors when pushing to a repository. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041

  2. monitoring May 11, 2026, 09:12 AM UTC

    To restore the service, we restarted the Gitaly process. We will monitor for any recurrence. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041

  3. resolved May 11, 2026, 11:16 AM UTC

    The issue has been resolved. The 500 errors when accessing repositories should not seen anymore and affected Git operations should work as expected. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041

Your product runs on more than GitLab

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →