# GitLab: 503s on GitLab.com

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2026-09-24 23:02 UTC · Resolved: 2026-09-25 04:37 UTC · Duration: 5.6 h
- Updates: 15 · Affected components: 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
- [Vendor status page: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6ab5ac13c927d205640922b7](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6ab5ac13c927d205640922b7)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)

## Discussed on Hacker News

- [GitLab Outage](https://news.ycombinator.com/item?id=49838034): 70 points, 36 comments, posted 2026-09-24 23:10 UTC, posted 9 min after the vendor’s first update

## Timeline of updates

- **investigating** 2026-09-24 23:02 UTC: We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
- **investigating** 2026-09-24 23:04 UTC: We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
- **identified** 2026-09-24 23:27 UTC: 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.
- **identified** 2026-09-24 23:39 UTC: 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.
- **identified** 2026-09-24 23:44 UTC: We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
- **identified** 2026-09-25 00:01 UTC: We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
- **identified** 2026-09-25 00:19 UTC: 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.
- **identified** 2026-09-25 00:31 UTC: 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.
- **identified** 2026-09-25 00:41 UTC: Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
- **identified** 2026-09-25 01:02 UTC: Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
- **identified** 2026-09-25 01:43 UTC: GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.
- **monitoring** 2026-09-25 02:03 UTC: GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
- **monitoring** 2026-09-25 02:34 UTC: GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
- **monitoring** 2026-09-25 03:36 UTC: GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
- **resolved** 2026-09-25 04:37 UTC: This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.

## Rewindex changes for this incident

- 2026-09-24 23:02 UTC: [Critical incident: 503s on GitLab.com](https://rewindex.com/change/ie4f72464c9dc84.md)


---
Canonical: https://rewindex.com/company/gitlab/incidents/6ab5ac13c927d205640922b7 · Markdown: https://rewindex.com/company/gitlab/incidents/6ab5ac13c927d205640922b7.md · JSON: https://rewindex.com/api/v1/companies/gitlab/incidents/6ab5ac13c927d205640922b7 · Generated 2026-10-18T10:29:49.058Z