GitHub uptime
GitHub, 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.
GitHub is up.
Up for 6 d 3 h. Last checked 2026-10-06 11:36 UTC from Sydney, Australia: 200 in 20 ms.
Last 24 hours
Up for 6 d 3 h99.65% passed
288 checks, median 30 ms from Falkenstein, 1 timeout
95% under 40 ms
Response time by region
Medians over this range, on one scale up to 300 ms. Europe's places are scaled to Falkenstein, its fastest shared place.
- Timed out, from Ashburn, USA5 min, 1 check
Last 90 days
Up for 6 d 3 h99.94% passed
1,764 checks, median 30 ms from Falkenstein, 1 timeout
95% under 50 ms
Response time by region
Medians over this range, on one scale up to 200 ms. Europe's places are scaled to Falkenstein, its fastest shared place.
In the last 24 hours GitHub passed 287 of 288 checks, 99.65%.
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 | 99.65% | 287 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 | 31 ms | 40 ms | 33 ms | 193 |
| Ashburn, USA | 26 ms | 109 ms | 57 ms | 560 |
| Copenhagen, Denmark | 80 ms | 105 ms | 83 ms | 168 |
| Singapore | 170 ms | 743 ms | 196 ms | 557 |
| Sydney, Australia | 33 ms | 294 ms | 86 ms | 83 |
| Aarhus, Denmark | 89 ms | 336 ms | 113 ms | 202 |
Outages
None detected since checks began on 30 Sep 2026.
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: 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 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.