Changes / GitLab / 503s on GitLab.com
GitLab: Critical incident: 503s on GitLab.com
Summary
Summary pending. The diff below shows exactly what changed.
Discussed on Hacker News
- 70 points · 36 comments · posted · posted 9 min after the vendor’s first update
Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.
Incident page: full timeline of updates →
What changed
Before: not present
After: 503s on GitLab.com
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-09-24 23:02 UTC
Before: not present
After: 2026-09-25 04:37 UTC
Before: not present
After: 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
Before: not present
After: We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
Before: not present
After: We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
Before: not present
After: We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
Before: not present
After: Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
Before: not present
After: GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.
Before: not present
After: GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
Before: not present
After: GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
Before: not present
After: GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
Before: not present
After: This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: 503s on GitLab.com (this change) | Major incident |