GitLab incident

HTTP 500 errors affecting GitLab.com

Major Resolved View vendor source →

GitLab experienced a major incident on August 27, 2026 affecting Website and CI/CD and 1 more component, lasting 3h 47m. The incident has been resolved; the full update timeline is below.

Started
Aug 27, 2026, 11:46 AM UTC
Resolved
Aug 27, 2026, 03:34 PM UTC
Duration
3h 47m
Detected by Pingoru
Aug 27, 2026, 11:46 AM UTC

Affected components

WebsiteCI/CDGitLab agent server for Kubernetes (Google Compute Engine)

Update timeline

  1. investigating Aug 27, 2026, 11:46 AM UTC

    There are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to restore normal service. 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 Aug 27, 2026, 11:46 AM UTC

    There are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to restore normal service.

  3. monitoring Aug 27, 2026, 11:53 AM UTC

    The issue has been identified and resolved. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807

  4. monitoring Aug 27, 2026, 11:53 AM UTC

    The issue has been identified and resolved. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807

  5. resolved Aug 27, 2026, 03:34 PM UTC

    Performance remains stable and prevention steps are being implemented. Find more information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807