GitLab uptime
GitLab, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.
GitLab is up.
Up for 38 d 10 h. Last checked 2026-11-20 18:03 UTC from Copenhagen, Denmark: 401 in 182 ms.
Last 24 hours
Up for 38 d 10 h100% passed
288 checks, median 188 ms from Copenhagen, all passed
95% under 225 ms
Response time by region
Medians over this range, on one scale up to 800 ms.
Last 90 days
Up for 38 d 10 h99.97% passed
14,795 checks, median 196 ms from Copenhagen, 3 failed checks, 2 timeouts
95% under 251 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.
Failures older than 15 days show on the bars only.
In the last 30 days GitLab passed 8,853 of 8,853 checks, 100%.
One outage since 30 Sep 2026, lasting 10 min, on 13 Oct 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 | 100% | 2,004 of 2,004 | 0 |
| 30 days | 100% | 8,853 of 8,853 | 0 |
| 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 | 214 ms | 293 ms | 225 ms | 42 |
| Helsinki, Finland | 196 ms | 221 ms | 202 ms | 42 |
| Ashburn, USA | 128 ms | 215 ms | 143 ms | 504 |
| Copenhagen, Denmark | 190 ms | 227 ms | 203 ms | 422 |
| Singapore | 473 ms | 619 ms | 465 ms | 504 |
| Sydney, Australia | 318 ms | 490 ms | 383 ms | 502 |
Outages
Every outage in the last year, newest first. Times are UTC; what failed and where are kept for 14 days.
| Began (UTC) | Ended (UTC) | Length | What failed | Seen from |
|---|---|---|---|---|
| 10 min | Not kept | Not kept |
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: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, 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.