GitLabOutage history and postmortems
Downtime, added up
GitLab: 0m weighted downtime in range, category median 1h 50m.
0 incidents, 0m of incident time (0m major or critical, 0m partial) between Jun 27, 2026 and Sep 24, 2026.
GitLab is a software forge primarily developed by GitLab Inc. It is available as either a free software "Community" edition or a proprietary software "Enterprise" edition.
Stated causes
0 incidents with no cause stated.
Postmortems
- Primary database data accidentally deleted, 18-hour restore
GitLabJan 31, 2017 · 19h
A backup is only real once a restore has been tested; destructive commands on production hosts need an unmistakable prompt.
GitLab incidents
1 on filePrimary database data accidentally deleted, 18-hour restoreJan 31, 2017, 23:0019hCriticalOperator
Questions
Is GitLab down right now?
Check GitLab's own status page at https://status.gitlab.com for the live state. This page shows GitLab's incident history from that page; the most recent incident started 2017-01-31: "Primary database data accidentally deleted, 18-hour restore".
How often does GitLab have outages?
GitLab posted 0 incidents in the last 90 days and 0 in the last year, 0 of them major or critical in the last 90 days. The median incident lasted Ongoing.
When was GitLab's last major outage?
2017-01-31: "Primary database data accidentally deleted, 18-hour restore", lasting 19h.
What usually causes GitLab incidents?
Where GitLab explained the cause, the most common was operator action (1 incidents). Most status updates do not name a cause.
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.