GitLab uptime
GitLab, checked by StatOSS every 5 minutes from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia. Measured from outside, with every outage dated in UTC.
GitLab is up.
Up for 6 d 3 h. Last checked 2026-10-06 11:37 UTC from Sydney, Australia: 401 in 278 ms.
Last 24 hours
Up for 6 d 3 h100% passed
288 checks, median 208 ms from Copenhagen, all passed
95% under 248 ms
Response time by region
Medians over this range, on one scale up to 500 ms. Europe's places are scaled to Copenhagen, its fastest shared place.
Last 90 days
Up for 6 d 3 h100% passed
1,764 checks, median 208 ms from Copenhagen, all passed
95% under 247 ms
Response time by region
Medians over this range, on one scale up to 500 ms. Europe's places are scaled to Copenhagen, its fastest shared place.
In the last 24 hours GitLab passed 288 of 288 checks, 100%.
No outage since checks began on 30 Sep 2026.
Availability
The share of checks that passed, and the outages that began, in each window up to now.
| Last | Passed | Checks | Outages |
|---|---|---|---|
| 24 hours | 100% | 288 of 288 | 0 |
| 7 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 30 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 90 days | Not enough history yet: checks began on 30 Sep 2026 | ||
A year of checks is kept; the year's figure appears here once there is a year of them.
Response time by location
Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.
| From | Median | 95th percentile | Mean | Checks |
|---|---|---|---|---|
| Falkenstein, Germany | 217 ms | 252 ms | 221 ms | 200 |
| Ashburn, USA | 139 ms | 226 ms | 158 ms | 555 |
| Copenhagen, Denmark | 208 ms | 259 ms | 218 ms | 170 |
| Singapore | 400 ms | 568 ms | 417 ms | 563 |
| Sydney, Australia | 296 ms | 508 ms | 346 ms | 84 |
| Aarhus, Denmark | 212 ms | 261 ms | 219 ms | 192 |
Outages
None detected since checks began on 30 Sep 2026.
What is checked
GitLab.com, the hosted GitLab: Git repositories, merge requests, CI/CD pipelines and a package and container registry.
StatOSS sends GET https://gitlab.com/api/v4/version and counts the check as passed on status 401 within 10 seconds. The REST API's version endpoint. It needs a token, so GitLab.com answers 401 Unauthorized: the API is reachable and answering. The sign-in page would do less well, since a bot check answers scripts there with 403.
Runners, Git over SSH and the web pages are not checked. Self-managed GitLab instances are not GitLab.com.
GitLab reports its own incidents at status.gitlab.com. The figures here are measured from outside and can differ from it in both directions.
How it is measured
- One check every 5 minutes, from one location at a time in turn: Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia.
- A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 401.
- A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
- Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
- Availability is the share of checks that passed. There are no maintenance windows: every check counts.
It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.