GitLab uptime
From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.
84.89%free of major or critical incidents, last 30 days
90.85%free of major or critical incidents, last 90 days
87.87%free of any incident, last 90 days
36incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): no vendor-reported incident openAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): no vendor-reported incident openAug 10 (UTC day): no vendor-reported incident openAug 11 (UTC day): no vendor-reported incident openAug 12 (UTC day): no vendor-reported incident openAug 13 (UTC day): 0 min with a major or critical incident open, 3 h 49 min with any incident open, 1 incident startedAug 14 (UTC day): no vendor-reported incident openAug 15 (UTC day): no vendor-reported incident openAug 16 (UTC day): no vendor-reported incident openAug 17 (UTC day): 6 h 32 min with a major or critical incident open, 6 h 32 min with any incident open, 1 incident startedAug 18 (UTC day): 3 h 35 min with a major or critical incident open, 3 h 35 min with any incident open, 1 incident startedAug 19 (UTC day): no vendor-reported incident openAug 20 (UTC day): no vendor-reported incident openAug 21 (UTC day): 29 min with a major or critical incident open, 29 min with any incident open, 1 incident startedAug 22 (UTC day): no vendor-reported incident openAug 23 (UTC day): no vendor-reported incident openAug 24 (UTC day): 1 h 23 min with a major or critical incident open, 1 h 23 min with any incident open, 1 incident startedAug 25 (UTC day): 14 h 1 min with a major or critical incident open, 14 h 1 min with any incident open, 1 incident startedAug 26 (UTC day): 12 min with a major or critical incident open, 12 min with any incident openAug 27 (UTC day): 6 h 11 min with a major or critical incident open, 6 h 11 min with any incident open, 2 incidents startedAug 28 (UTC day): no vendor-reported incident openAug 29 (UTC day): no vendor-reported incident openAug 30 (UTC day): no vendor-reported incident openAug 31 (UTC day): no vendor-reported incident openSep 1 (UTC day): no vendor-reported incident openSep 2 (UTC day): 49 min with a major or critical incident open, 49 min with any incident open, 1 incident startedSep 3 (UTC day): no vendor-reported incident openSep 4 (UTC day): no vendor-reported incident openSep 5 (UTC day): no vendor-reported incident openSep 6 (UTC day): no vendor-reported incident openSep 7 (UTC day): no vendor-reported incident openSep 8 (UTC day): 1 h 3 min with a major or critical incident open, 1 h 3 min with any incident open, 1 incident startedSep 9 (UTC day): 0 min with a major or critical incident open, 1 h 40 min with any incident open, 1 incident startedSep 10 (UTC day): 4 h 46 min with a major or critical incident open, 4 h 46 min with any incident open, 1 incident startedSep 11 (UTC day): no vendor-reported incident openSep 12 (UTC day): no vendor-reported incident openSep 13 (UTC day): no vendor-reported incident openSep 14 (UTC day): no vendor-reported incident openSep 15 (UTC day): no vendor-reported incident openSep 16 (UTC day): no vendor-reported incident openSep 17 (UTC day): 3 h 16 min with a major or critical incident open, 3 h 16 min with any incident open, 1 incident startedSep 18 (UTC day): 13 h 45 min with a major or critical incident open, 13 h 45 min with any incident openSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): 0 min with a major or critical incident open, 8 h 8 min with any incident open, 1 incident startedSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): no vendor-reported incident openSep 24 (UTC day): 8 h with a major or critical incident open, 8 h with any incident open, 2 incidents startedSep 25 (UTC day): 9 h 54 min with a major or critical incident open, 9 h 54 min with any incident open, 1 incident startedSep 26 (UTC day): no vendor-reported incident openSep 27 (UTC day): no vendor-reported incident openSep 28 (UTC day): no vendor-reported incident openSep 29 (UTC day): 0 min with a major or critical incident open, 5 h 45 min with any incident open, 1 incident startedSep 30 (UTC day): 0 min with a major or critical incident open, 12 h 26 min with any incident openOct 1 (UTC day): 14 h 55 min with a major or critical incident open, 14 h 55 min with any incident open, 2 incidents startedOct 2 (UTC day): no vendor-reported incident openOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): no vendor-reported incident openOct 6 (UTC day): no vendor-reported incident openOct 7 (UTC day): 0 min with a major or critical incident open, 1 h 13 min with any incident open, 1 incident startedOct 8 (UTC day): 2 h 34 min with a major or critical incident open, 2 h 34 min with any incident open, 1 incident startedOct 9 (UTC day): no vendor-reported incident openOct 10 (UTC day): 19 h 11 min with a major or critical incident open, 19 h 11 min with any incident open, 1 incident startedOct 11 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 12 (UTC day): 10 h 15 min with a major or critical incident open, 22 h 45 min with any incident open, 1 incident startedOct 13 (UTC day): 16 h 50 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 14 (UTC day): 23 h 40 min with a major or critical incident open, 23 h 40 min with any incident open, 1 incident startedOct 15 (UTC day): 4 h 19 min with a major or critical incident open, 7 h 50 min with any incident open, 2 incidents startedOct 16 (UTC day): 1 h 14 min with a major or critical incident open, 3 h 2 min with any incident open, 2 incidents startedOct 17 (UTC day): no vendor-reported incident openOct 18 (UTC day): no vendor-reported incident openOct 19 (UTC day): no vendor-reported incident openOct 20 (UTC day): 4 h 51 min with a major or critical incident open, 4 h 51 min with any incident open, 2 incidents startedOct 21 (UTC day): 1 h 21 min with a major or critical incident open, 1 h 21 min with any incident openOct 22 (UTC day): no vendor-reported incident openOct 23 (UTC day): 32 min with a major or critical incident open, 32 min with any incident open, 1 incident startedOct 24 (UTC day): no vendor-reported incident openOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): no vendor-reported incident openOct 27 (UTC day): no vendor-reported incident openOct 28 (UTC day): no vendor-reported incident openOct 29 (UTC day): no vendor-reported incident openOct 30 (UTC day): no vendor-reported incident openOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): no vendor-reported incident openNov 3 (UTC day): 0 min with a major or critical incident open, 6 h 16 min with any incident open, 2 incidents startedNov 4 (UTC day): no vendor-reported incident open
Aug 7today
no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive
Last 7 days, by hour
now
Numbers
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days | 84.89% | 80.38% | 4.5 days | 5.9 days | 16 |
| Last 90 days | 90.85% | 87.87% | 8.2 days | 10.9 days | 36 |
This is what GitLab itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .
See the incidents: GitLab status history · last 90 days · GitLab status page (opens in new tab) · Markdown