GitLab incident

Elevated 5xx Errors on GitLab.com

Minor Resolved View vendor source →

GitLab experienced a minor incident on May 12, 2026 affecting Website and Git Operations and 1 more component, lasting 28m. The incident has been resolved; the full update timeline is below.

Started
May 12, 2026, 09:04 PM UTC
Resolved
May 12, 2026, 09:33 PM UTC
Duration
28m
Detected by Pingoru
May 12, 2026, 09:04 PM UTC

Affected components

WebsiteGit OperationsCI/CDGitLab agent server for Kubernetes (Google Compute Engine)

Update timeline

  1. investigating May 12, 2026, 09:04 PM UTC

    We are seeing an increase in 5xx errors on GitLab.com and are investigating the issue. User may experience issues on GitLab.com. We will provide updates as we have them. 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

  2. investigating May 12, 2026, 09:04 PM UTC

    We are seeing an increase in 5xx errors on GitLab.com and are investigating the issue. User may experience issues on GitLab.com. We will provide updates as we have them.

  3. identified May 12, 2026, 09:22 PM UTC

    We have identified the issue as a frozen Gitaly node and are working to correct the issue.

  4. identified May 12, 2026, 09:22 PM UTC

    We have identified the issue as a frozen Gitaly node and are working to correct the issue.

  5. resolved May 12, 2026, 09:33 PM UTC

    This issue has resolved and error rates have returned to normal. More information can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22107