GitLab Outage History
4 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded GitLab Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 21, 2026 | 403 errors across GitLab.comWe're monitoring an incident where 403s were seen across GitLab.com. The fix for this is already in place. More about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762 | 26 min | Resolved |
| Aug 18, 2026 | 500 errors when fetching commits on GitLab.comWe are investigating an issue causing a subset of requests to GitLab.com receiving 500 errors. We will provide updates as we learn more from our investigation. More information here… | 3h 11m | Resolved |
| Aug 17, 2026 | Project and Group Deletions DelayedWe are currently investigating an issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been… | 6h 25m | Resolved |
| Aug 13, 2026 | Elevated queue times on saas-linux-medium-arm64 runnerWe are seeing a growing queue of pending jobs on the saas-linux-medium-arm64 hosted runner on GitLab.com. We are rolling out a mitigation. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702 | 3h 18m | Resolved |
How to Read This GitLab Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before GitLab acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single GitLab outage in this window ran 6h 25m, against a mean recovery of 3h 20m. If you depend on GitLab in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.