Checked 14 days ago from real home networks
What this means: All 6 home networks reached github.com. If it doesn't load for you, the problem is most likely local — your DNS cache, browser cache, VPN or ISP. See the checklist below.
The fastest answer came from 🇫🇷 FR (44 ms), the slowest from 🇩🇪 DE (168 ms) — 89 ms on average across 6 locations.
These probes come from the Sensmos network — 104 small devices running on ordinary home internet across 19 countries, including 8 nodes in DE, where this site's server appears to be hosted.
github.com is served from 4 different servers — nodes in different countries reached different IP addresses. That means github.com is not one place: it's a multi-location deployment (a CDN or geo-routed setup), and the copy you reach depends on where you are. The same URL can differ by country — response time, availability, even which content or page version is served. It's how the modern web scales, but it's also the mechanism behind geo-blocking and regional censorship: a site that is up and unrestricted from one country can be slow, altered, or entirely blocked from another. That's exactly why checking from real home networks in multiple countries — not from a single data center — matters.
Each node makes a single HTTP request, the same way a browser does, and reports the response time from its own household connection. A data-center monitor can tell you a server is up — checks from real home networks show whether people can actually reach it, through real ISPs, real routing and the real last mile.
Down only for you? Quick checklist:
1. Hard-refresh (Ctrl+F5). 2. Try another browser or incognito. 3. Switch networks — try your phone's mobile data. 4. Flush DNS or switch resolver (1.1.1.1 / 8.8.8.8). 5. Turn off VPN/proxy. 6. Check the service's official status channels.
FAQ
Is github.com down right now?
No — as of the last check (14 days ago), github.com was reachable from all 6 real home networks that probed it.
Why does github.com work for some people but not for others?
Websites can fail regionally: geo-blocks, national ISP filtering, DNS differences, CDN or routing problems. A site behind a CDN is many servers — the copy you reach depends on where you are, so one country can be down while another is fine.
How is this check different from other "is it down" tools?
Most tools check from cloud datacenters or aggregate user complaints. UpFromWhere sends real HTTP requests from small devices on ordinary home internet connections in multiple countries — the same path a real visitor takes, including the ISP and the last mile.
Recently checked: sensmos.com · allegro.pl · youtube.com · google.com · aukro.cz · netflix.com · amazon.com · cryptojar.net