GitLab Outage

# GitLab System Status Source: [https://status.gitlab.com/](https://status.gitlab.com/) Incident Status Partial 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 01:02 UTC** **IDENTIFIED** Error rates are decreasing, but some customers may still see errors\. We are continuing to address the remaining impact and will update again soon\. **September 25, 2026 00:41 UTC** **IDENTIFIED** Error rates are decreasing, but some customers may still see errors\. We are continuing to address the remaining impact and will update again soon\. **September 25, 2026 00:31 UTC** **IDENTIFIED** Error rate is decreasing after active mitigation efforts\. We're still actively working on addressing the root cause\. We will update with more details shortly\. **September 25, 2026 00:19 UTC** **IDENTIFIED** Error rate is decreasing after active mitigation efforts\. We're still actively working on addressing the root cause\. We will update with more details shortly\. **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 recieving 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 recieving reports of 503 errors on GitLab\.com\. This is under active investigation\. We will update with more details shortly\.