Is GitHub down in Japan?
Vendor reports no incidentWhat GitHub reports
GitHub reports no incident on its status page.
As of the last successful poll, 2026-11-05 15:28 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.
Partially degradedin Japan, measured from Tokyo
Our Tokyo probe last checked GitHub at Nov 5, 2026, 3:33 PM UTC and read partially degraded.
Over the last 24 hours we completed 244 checks from Tokyo and 244 answered cleanly, 100.00% availability.
Of the 9 other regions we check GitHub from, 6 read partially degraded and 3 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 Tokyo probe measured
Last checked Nov 5, 2026, 3:33 PM UTC.
GitHub from Tokyo over the last 30 days
Over the last 30 days, GitHub answered our Tokyo probe in 726 ms on average, and 1 check in 20 took longer than 1,192 ms.
Ranked by average response time across the 10 cities we check GitHub from, Tokyo 7th; London was fastest at 444 ms and Singapore slowest at 911 ms.
From Tokyo we ran 19,206 checks of GitHub in 30 days, and 19,205 answered cleanly: 99.99% availability.
1 of the 30 days had at least one failed check. The weakest was Oct 15 (UTC), at 99.86% across 719 checks.
In Tokyo local time (GMT+9), GitHub was slowest around 10 AM, at 1,240 ms on average over the last 14 days, and quickest around 3 PM, at 798 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 153 | 100.00% | 923 ms |
| Wed, Nov 4 | 239 | 100.00% | 897 ms |
| Tue, Nov 3 | 243 | 100.00% | 867 ms |
| Mon, Nov 2 | 503 | 100.00% | 1,006 ms |
| Sun, Nov 1 | 708 | 100.00% | 897 ms |
| Sat, Oct 31 | 700 | 100.00% | 841 ms |
| Fri, Oct 30 | 641 | 100.00% | 824 ms |
| Thu, Oct 29 | 673 | 100.00% | 860 ms |
| Wed, Oct 28 | 711 | 100.00% | 917 ms |
| Tue, Oct 27 | 680 | 100.00% | 1,128 ms |
| Mon, Oct 26 | 640 | 100.00% | 987 ms |
| Sun, Oct 25 | 643 | 100.00% | 739 ms |
| Sat, Oct 24 | 618 | 100.00% | 957 ms |
| Fri, Oct 23 | 674 | 100.00% | 1,038 ms |
GitHub outages measured from Japan
Our Tokyo probe measured no confirmed GitHub outage in the last 90 days.
How the other regions read right now
Of the 9 other regions we check GitHub from, 6 read partially degraded and 3 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Ashburn | Partially degraded | 100.00% of 606 checks |
| San Jose | Partially degraded | 100.00% of 430 checks |
| Frankfurt | Checks passing | 100.00% of 392 checks |
| Chicago | Checks passing | 99.72% of 358 checks |
| Toronto | Partially degraded | 100.00% of 358 checks |
| London | Partially degraded | 100.00% of 355 checks |
| Singapore | Partially degraded | 100.00% of 355 checks |
| Sydney | Partially degraded | 100.00% of 355 checks |
| São Paulo | Checks passing | 99.72% of 358 checks |
Other countries we check GitHub from
How we measured this
Japan readings on this page come from RealUptime's own Tokyo probe 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 Tokyo
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