StatOSS

GitHub uptime

GitHub, 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.

api.github.com/rate_limitEvery 5 minutes

GitHub is up.

Up for 12 d 5 h. Last checked 2026-11-20 18:02 UTC from Falkenstein, Germany: 200 in 40 ms.

Last 24 hours

Up for 12 d 5 h100% passed

288 checks, median 30 ms from Falkenstein, all passed

95% under 49 ms

Response time by region
EuropeEurope30 ms
N. AmericaNorth America20 ms
AsiaAsia23 ms
OceaniaOceania23 ms

Medians over this range, on one scale up to 100 ms.

Last 90 days

Up for 12 d 5 h99.87% passed

14,795 checks, median 34 ms from Falkenstein, 18 failed checks, 7 timeouts

95% under 88 ms

Response time by region
EuropeEurope34 ms
N. AmericaNorth America22 ms
AsiaAsia43 ms
OceaniaOceania22 ms

Medians over this range, on one scale up to 200 ms. Europe's places are scaled to Falkenstein, 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 GitHub passed 8,836 of 8,852 checks, 99.81%.

2 outages since 30 Sep 2026; the longest lasted 35 min, on 8 Nov 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 days99.81%8,836 of 8,8522
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, Germany32 ms51 ms34 ms421
Helsinki, Finland80 ms133 ms87 ms41
Ashburn, USA19 ms103 ms33 ms504
Copenhagen, Denmark54 ms57 ms55 ms42
Singapore24 ms195 ms63 ms503
Sydney, Australia22 ms191 ms49 ms504

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
25 minHTTP 503, Timed outAshburn, USA, Falkenstein, Germany, Helsinki, Finland
35 minHTTP 503, Timed outAshburn, USA, Falkenstein, Germany, Helsinki, Finland

What is checked

Git hosting, pull requests, issues, Actions and packages. Most open source code and a large share of private code lives there.

StatOSS sends GET https://api.github.com/rate_limit and counts the check as passed on status 200 within 10 seconds. The REST API's rate limit endpoint. It answers 200 without a token, and GitHub documents that asking it does not count against the limit, so the check spends nobody's allowance.

It checks api.github.com. Git over HTTPS and SSH, Actions runners and github.com pages run on other systems and can fail on their own.

GitHub reports its own incidents at www.githubstatus.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 200.
  • 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.