Is GitHub down in the US?
Vendor reports no incidentWhat GitHub reports
GitHub reports no incident on its status page.
As of the last successful poll, 2026-11-05 18:18 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn, San Jose, and Chicago
All 3 of our probes in the US, in Ashburn, San Jose, and Chicago, read checks passing when they last checked GitHub at Nov 5, 2026, 6:27 PM UTC.
Over the last 24 hours we completed 1389 checks from Ashburn, San Jose, and Chicago and 1388 answered cleanly, 99.92% availability. 1 of those was a measured failure.
Of the 7 other regions we check GitHub from, all 7 read checks passing right now.
Email me when GitHub reports an incident on its status page, and again when it reports it resolved.
What our Ashburn, San Jose, and Chicago probes measured
Last checked Nov 5, 2026, 6:27 PM UTC.
GitHub from Ashburn, San Jose, and Chicago over the last 30 days
Over the last 30 days, GitHub answered our Ashburn probe in 521 ms on average, and 1 check in 20 took longer than 873 ms.
Over the last 30 days, GitHub answered our San Jose probe in 548 ms on average, and 1 check in 20 took longer than 883 ms.
Over the last 30 days, GitHub answered our Chicago probe in 608 ms on average, and 1 check in 20 took longer than 1,084 ms.
Ranked by average response time across the 10 cities we check GitHub from, Ashburn 3rd, San Jose 4th, Chicago 5th; London was fastest at 444 ms and Singapore slowest at 912 ms.
From Ashburn, San Jose, and Chicago we ran 52,084 checks of GitHub in 30 days, and 52,082 answered cleanly: 99.99% availability.
2 of the 30 days had at least one failed check. The weakest was Nov 5 (UTC), at 99.90% across 1,062 checks.
In Ashburn local time (EST), GitHub was slowest around 12 PM, at 709 ms on average over the last 14 days, and quickest around 9 PM, at 583 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 1,062 | 99.90% | 664 ms |
| Wed, Nov 4 | 1,384 | 100.00% | 679 ms |
| Tue, Nov 3 | 1,362 | 100.00% | 704 ms |
| Mon, Nov 2 | 1,626 | 100.00% | 691 ms |
| Sun, Nov 1 | 1,796 | 100.00% | 540 ms |
| Sat, Oct 31 | 1,795 | 100.00% | 614 ms |
| Fri, Oct 30 | 1,799 | 100.00% | 630 ms |
| Thu, Oct 29 | 1,793 | 100.00% | 610 ms |
| Wed, Oct 28 | 1,796 | 100.00% | 696 ms |
| Tue, Oct 27 | 1,793 | 100.00% | 696 ms |
| Mon, Oct 26 | 1,796 | 100.00% | 738 ms |
| Sun, Oct 25 | 1,794 | 100.00% | 668 ms |
| Sat, Oct 24 | 1,799 | 100.00% | 544 ms |
| Fri, Oct 23 | 1,803 | 100.00% | 745 ms |
GitHub outages measured from the US
Our Ashburn, San Jose, and Chicago probes measured no confirmed GitHub outage in the last 90 days.
How the other regions read right now
Of the 7 other regions we check GitHub from, all 7 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 391 checks |
| Tokyo | Checks passing | 100.00% of 244 checks |
| Toronto | Checks passing | 100.00% of 358 checks |
| London | Checks passing | 100.00% of 356 checks |
| Singapore | Checks passing | 100.00% of 355 checks |
| Sydney | Checks passing | 100.00% of 355 checks |
| São Paulo | Checks passing | 100.00% of 358 checks |
Other countries we check GitHub from
How we measured this
The US readings on this page come from RealUptime's own Ashburn, San Jose, and Chicago probes against GitHub's public endpoints. They are not user reports, and they are not GitHub's own status page.
See GitHub's full check readings, the 90-day history by region, or the outage tracker methodology.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter