GitLab incident

General slowness and intermittent 502s on Gitlab.com

Minor Resolved View vendor source →

GitLab experienced a minor incident on August 25, 2026 affecting Website and API and 1 more component, lasting 14h 12m. The incident has been resolved; the full update timeline is below.

Started
Aug 25, 2026, 09:59 AM UTC
Resolved
Aug 26, 2026, 12:12 AM UTC
Duration
14h 12m
Detected by Pingoru
Aug 25, 2026, 09:59 AM UTC

Affected components

WebsiteAPIGitLab agent server for Kubernetes (Google Compute Engine)

Update timeline

  1. investigating Aug 25, 2026, 09:59 AM UTC

    We are currently investigating reports of slowness and 502 errors. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783 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 25, 2026, 09:59 AM UTC

    We are currently investigating reports of slowness and 502 errors. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

  3. investigating Aug 25, 2026, 01:43 PM UTC

    Slowness & 502s have been bursty with not much impact. A revert MR is under way while we are investigating other possible root causes. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

  4. investigating Aug 25, 2026, 01:43 PM UTC

    Slowness & 502s have been bursty with not much impact. A revert MR is under way while we are investigating other possible root causes. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

  5. monitoring Aug 25, 2026, 02:48 PM UTC

    We have not seen active user impact for several hours and we have identified the possible root cause. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

  6. monitoring Aug 25, 2026, 02:48 PM UTC

    We have not seen active user impact for several hours and we have identified the possible root cause. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

  7. monitoring Aug 25, 2026, 06:34 PM UTC

    We continue to monitor and have not observed any active user impact. We are working towards a permanent fix and will provide our next update once it has been implemented. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

  8. monitoring Aug 25, 2026, 06:34 PM UTC

    We continue to monitor and have not observed any active user impact. We are working towards a permanent fix and will provide our next update once it has been implemented. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

  9. resolved Aug 26, 2026, 12:12 AM UTC

    The fix has been implemented and the issue is now resolved. We have not observed any active user impact. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783