GitLab Outage

GitLab reported the incident beginning at 23:02 UTC on September 24, 2026, when it received reports of 503 errors on GitLab.com and moved into an active investigation. A duplicate update at 23:04 UTC repeated that the issue was under investigation.

By 23:27 UTC the company had moved to an IDENTIFIED state, stating it had identified the cause of the 503 errors and was working on mitigating the issue; a follow-up at 23:39 UTC added that the API was also affected. Updates at 23:44 UTC and 00:01 UTC reported that mitigation efforts were ongoing and that some recovery was becoming visible.

Two updates at 00:19 UTC and 00:31 UTC said error rates were decreasing after active mitigation, while noting GitLab was still actively working on the root cause, and two further updates at 00:41 UTC and 01:02 UTC cautioned that some customers might still see errors as the remaining impact was addressed. At 01:43 UTC GitLab said services remained stable with decreased error rates while recovery efforts continued.

GitLab moved to MONITORING at 02:03 UTC and again at 02:34 UTC, stating that services were operational and that it was continuing to monitor the situation and assess any outstanding impacts during the disruption window. The status page listed a broad set of affected or monitored components, including the website, API, Git operations, Package Registry, Container Registry, GitLab Pages, CI/CD and its hosted runners on Linux, Windows, and macOS, self-managed runners, community-contribution runners, SAML SSO for GitLab SaaS, background processing, the GitLab Customers Portal, support services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, docs.gitlab.com, Canary, GitLab Duo, and the GitLab agent server for Kubernetes. Locations and dependencies listed were Google Compute Engine, Digital Ocean, Zendesk, AWS, and Self-Managed Runner Connectivity.