GitLab incident

503s on GitLab.com

Major Resolved View vendor source →

GitLab experienced a major incident on October 16, 2026 affecting Website and API and 1 more component, lasting 1h 13m. The incident has been resolved; the full update timeline is below.

Started
Oct 16, 2026, 04:10 PM UTC
Resolved
Oct 16, 2026, 05:24 PM UTC
Duration
1h 13m
Detected by Pingoru
Oct 16, 2026, 04:10 PM UTC

Affected components

WebsiteAPIGit OperationsPackage RegistryContainer RegistryGitLab PagesCI/CDCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on WindowsCI/CD - Hosted runners on macOS

Update timeline

  1. investigating Oct 16, 2026, 04:10 PM UTC

    We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details. 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 Oct 16, 2026, 04:10 PM UTC

    We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

  3. investigating Oct 16, 2026, 04:25 PM UTC

    We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

  4. investigating Oct 16, 2026, 04:25 PM UTC

    We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

  5. identified Oct 16, 2026, 04:40 PM UTC

    We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

  6. identified Oct 16, 2026, 04:40 PM UTC

    We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

  7. identified Oct 16, 2026, 04:52 PM UTC

    Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

  8. identified Oct 16, 2026, 04:52 PM UTC

    Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

  9. monitoring Oct 16, 2026, 05:05 PM UTC

    We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

  10. monitoring Oct 16, 2026, 05:05 PM UTC

    We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

  11. resolved Oct 16, 2026, 05:24 PM UTC

    The issue is fully resolved and operations on GitLab.com and GitLab Duo are operating normally. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261