Global IT infrastructure status

GITLAB

🟡 Degraded

503s on GitLab.com

Investigating

Started
2026-10-16 16:10 UTC
21 days ago
Last update
2026-10-16 17:24 UTC
21 days ago
Running for
21d 4h

Timeline

  1. 16 Oct · 17:24 UTC 🟡 Investigating rss

    October 16, 2026 16:10 UTC
    Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

    October 16, 2026 16:25 UTC
    Investigating - 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

    October 16, 2026 16:40 UTC
    Identified - 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

    October 16, 2026 16:52 UTC
    Identified - 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

    October 16, 2026 17:05 UTC
    Monitoring - 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

    October 16, 2026 17:24 UTC
    Resolved - 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

  2. 16 Oct · 17:24 UTC 🟡 Investigating rss

    October 16, 2026 16:10 UTC
    Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

    October 16, 2026 16:25 UTC
    Investigating - 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/23402

    October 16, 2026 16:40 UTC
    Identified - 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/23402

    October 16, 2026 16:52 UTC
    Identified - 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/23402

    October 16, 2026 17:05 UTC
    Monitoring - 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/23402

    October 16, 2026 17:24 UTC
    Resolved - 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/23402

  3. 16 Oct · 17:05 UTC 🟡 Investigating rss

    October 16, 2026 16:10 UTC
    Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

    October 16, 2026 16:25 UTC
    Investigating - 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

    October 16, 2026 16:40 UTC
    Identified - 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

    October 16, 2026 16:52 UTC
    Identified - 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

    October 16, 2026 17:05 UTC
    Monitoring - 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

  4. 16 Oct · 16:52 UTC 🟡 Investigating rss

    October 16, 2026 16:10 UTC
    Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

    October 16, 2026 16:25 UTC
    Investigating - 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

    October 16, 2026 16:40 UTC
    Identified - 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

    October 16, 2026 16:52 UTC
    Identified - 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

  5. 16 Oct · 16:40 UTC 🟡 Investigating rss

    October 16, 2026 16:10 UTC
    Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

    October 16, 2026 16:25 UTC
    Investigating - 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

    October 16, 2026 16:40 UTC
    Identified - 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. 16 Oct · 16:25 UTC 🟡 Investigating rss

    October 16, 2026 16:10 UTC
    Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

    October 16, 2026 16:25 UTC
    Investigating - 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

  7. 16 Oct · 16:10 UTC 🟡 Investigating rss

    October 16, 2026 16:10 UTC
    Investigating - We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

Source

Official GitLab status — view original incident ↗

IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.