Search

Changes / GitLab / 503s on GitLab.com

GitLab: Critical incident: 503s on GitLab.com

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: critical (vendor)Changed Detected Source: status.gitlab.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: 503s on GitLab.com
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-10-16 16:10 UTC
AddedResolved time#5
Before: not present
After: 2026-10-16 17:24 UTC
AddedAffected components#6
Before: not present
After: API, Background Processing, Canary, CI/CD, CI/CD - Hosted runners for GitLab community contributions, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners on Windows, CI/CD - Self-managed runners, Container Registry, docs.gitlab.com, forum.gitlab.com, GitLab agent server for Kubernetes, GitLab Customers Portal, GitLab Duo, GitLab Pages, Git Operations, Package Registry, packages.gitlab.com, SAML SSO - GitLab SaaS, Support Services, version.gitlab.com, Website
AddedUpdateinvestigating#7
Before: not present
After: We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.
AddedUpdateinvestigating#8
Before: not present
After: 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
AddedUpdateidentified#9
Before: not present
After: 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
AddedUpdateidentified#10
Before: not present
After: 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
AddedUpdatemonitoring#11
Before: not present
After: 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
AddedUpdateresolved#12
Before: not present
After: 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

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Critical incident: 503s on GitLab.com (this change)Major incident

All GitLab changes → · GitLab profile · Markdown · JSON