# GitLab: Critical incident: 503s on GitLab.com

**Summary:** _summary pending_
- Kind: Major incident · Label: critical (vendor)
- Changed: 2026-09-24 23:02 UTC · Detected: 2026-10-18 05:07 UTC
- [Source: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6ab5ac13c927d205640922b7](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/6ab5ac13c927d205640922b7)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)
- Versions: before (none: first archived) → after incident\_version:188/6ab5ac13c927d205640922b7@3ba2a623cd99
- Change 1 of 1 for this incident

## 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

Incident page (full timeline): [503s on GitLab.com](https://rewindex.com/company/gitlab/incidents/6ab5ac13c927d205640922b7.md)
## What changed

**1. Added: Title**

```diff
+ 503s on GitLab.com
```

**2. Added: Impact**

```diff
+ critical
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2026-09-24 23:02 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-09-25 04:37 UTC
```

**6. Added: Affected components**

```diff
+ 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
```

**7. Added: Update** (investigating) · 2026-09-24 23:02 UTC

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

**8. Added: Update** (investigating) · 2026-09-24 23:04 UTC

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

**9. Added: Update** (identified) · 2026-09-24 23:27 UTC

```diff
+ 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.
```

**10. Added: Update** (identified) · 2026-09-24 23:39 UTC

```diff
+ 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.
```

**11. Added: Update** (identified) · 2026-09-24 23:44 UTC

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

**12. Added: Update** (identified) · 2026-09-25 00:01 UTC

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

**13. Added: Update** (identified) · 2026-09-25 00:19 UTC

```diff
+ 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.
```

**14. Added: Update** (identified) · 2026-09-25 00:31 UTC

```diff
+ 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.
```

**15. Added: Update** (identified) · 2026-09-25 00:41 UTC

```diff
+ Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
```

**16. Added: Update** (identified) · 2026-09-25 01:02 UTC

```diff
+ Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.
```

**17. Added: Update** (identified) · 2026-09-25 01:43 UTC

```diff
+ GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.
```

**18. Added: Update** (monitoring) · 2026-09-25 02:03 UTC

```diff
+ GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
```

**19. Added: Update** (monitoring) · 2026-09-25 02:34 UTC

```diff
+ GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
```

**20. Added: Update** (monitoring) · 2026-09-25 03:36 UTC

```diff
+ GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.
```

**21. Added: Update** (resolved) · 2026-09-25 04:37 UTC

```diff
+ This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-09-24 23:02 UTC | Critical incident: 503s on GitLab.com (this change) | critical |

All GitLab changes: [timeline](https://rewindex.com/company/gitlab/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/ie4f72464c9dc84 · Markdown: https://rewindex.com/change/ie4f72464c9dc84.md · JSON: https://rewindex.com/api/v1/changes/ie4f72464c9dc84 · Generated 2026-10-18T08:47:50.757Z