StatOSS

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.com/api/v4/versionEvery 5 minutes

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
EuropeEurope188 ms
N. AmericaNorth America120 ms
AsiaAsia441 ms
OceaniaOceania369 ms

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
EuropeEurope196 ms
N. AmericaNorth America135 ms
AsiaAsia406 ms
OceaniaOceania317 ms

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.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:04 UTC.

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.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,004 of 2,0040
30 days100%8,853 of 8,8530
90 daysNot 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.

FromMedian95th percentileMeanChecks
Falkenstein, Germany214 ms293 ms225 ms42
Helsinki, Finland196 ms221 ms202 ms42
Ashburn, USA128 ms215 ms143 ms504
Copenhagen, Denmark190 ms227 ms203 ms422
Singapore473 ms619 ms465 ms504
Sydney, Australia318 ms490 ms383 ms502

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)LengthWhat failedSeen from
10 minNot keptNot 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.