🚨GitLab Incident Affects Multiple Services, Ongoing Since Sept 24
GitLab Outage Hits Wide Range of Services
TL;DR
GitLab reported a 503 error affecting numerous services since September 24, impacting Website, API, CI/CD, and more. Recovery efforts ongoing, but many services remain affected.
GitLab reported a widespread 503 error affecting multiple services since September 24, impacting everything from the Website and API to CI/CD and SAML SSO. The incident also affected services hosted on Google Compute Engine, Digital Ocean, and AWS. If you're using GitLab for CI/CD, package management, or SSO, this is a big deal. Recovery efforts are underway, but as of September 25, many services remain affected. The incident also hit GitLab's Support Services and Customer Portal, adding to the disruption.
Key Points
GitLab reported a 503 error impacting multiple services since September 24, 2026, at 23:02 UTC.
The incident affected Website, API, Git Operations, Package Registry, Container Registry, GitLab Pages, CI/CD, and SAML SSO.
Services hosted on Google Compute Engine, Digital Ocean, and AWS were impacted by the incident.
GitLab's Support Services, Customer Portal, and packages.gitlab.com were also affected.
The incident also impacted version.gitlab.com, forum.gitlab.com, and docs.gitlab.com.
Why It Matters
If you're using GitLab for CI/CD, package management, or SSO, this incident is a big deal. Services like GitLab Pages, Container Registry, and Support Services are down, disrupting workflows and development processes. Recovery efforts are ongoing, but the impact is significant for teams relying on GitLab's services.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,508 builders reading daily.