FRIDAY, SEPTEMBER 25, 2026|No. 16355
Technology · Service Disruption

GitLab.com Experiences Widespread Service Disruption

GitLab.com experienced a significant service disruption, impacting a broad range of its features and services, including Git operations, CI/CD, and the customer portal.

A screenshot of the GitLab status page indicating a service disruption.
A screenshot of the GitLab status page indicating a service disruption. · Photo by David Pupăză on Unsplash
1 sources
Pipeline ingest
3 reads
Positive / Neutral / Negative
0 countries
Related coverage
503s on GitLab.com Service Disruption

Incident Status

Service Disruption

Components

Website, API, Git Operations, Package Registry, Container Registry, GitLab Pages, CI/CD, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners for GitLab community contributions, CI/CD - Self-managed runners, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, docs.gitlab.com, Canary, GitLab Duo, GitLab agent server for Kubernetes

Locations

Google Compute Engine, Digital Ocean, Zendesk, AWS, Self-Managed Runner Connectivity


September 25, 2026 00:01 UTC

IDENTIFIED

We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

September 24, 2026 23:44 UTC

IDENTIFIED

We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

September 24, 2026 23:39 UTC

IDENTIFIED

We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly.

September 24, 2026 23:27 UTC

IDENTIFIED

We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly.

September 24, 2026 23:04 UTC

INVESTIGATING

We are receiving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.

September 24, 2026 23:02 UTC

INVESTIGATING

We are receiving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.

Website

Google Compute Engine

Service Disruption

API

Google Compute Engine

Service Disruption

Git Operations

Google Compute Engine

Service Disruption

Package Registry

Google Compute Engine

Service Disruption

Container Registry

Google Compute Engine

Service Disruption

GitLab Pages

Google Compute Engine

Service Disruption

CI/CD

Google Compute Engine

Service Disruption

CI/CD - Hosted runners on Linux

Google Compute Engine

Service Disruption

CI/CD - Hosted runners on Windows

Google Compute Engine

Service Disruption

CI/CD - Hosted runners on macOS

Google Compute EngineAWS

Service Disruption

CI/CD - Hosted runners for GitLab community contributions

Google Compute Engine

Service Disruption

CI/CD - Self-managed runners

Self-Managed Runner Connectivity

Service Disruption

SAML SSO - GitLab SaaS

Google Compute Engine

Service Disruption

Background Processing

Google Compute Engine

Service Disruption

GitLab Customers Portal

Google Compute Engine

Service Disruption

Support Services

Zendesk

Service Disruption

packages.gitlab.com

AWS

Service Disruption

version.gitlab.com

AWS

Service Disruption

forum.gitlab.com

Digital Ocean

Service Disruption

docs.gitlab.com

Google Compute Engine

Service Disruption

Canary

Google Compute Engine

Service Disruption

GitLab Duo

Google Compute Engine

Service Disruption

GitLab agent server for Kubernetes

Google Compute Engine

Service Disruption

PAN's pipeline reviewed approximately 1 open sources for this article. No human editor reviewed this article before publication.

Related Reads

Show on timeline →