TRACE THE QUESTION
One connection.
A few different
possibilities.
Check a public route. Compare an official report.
Leave the unproven causes open.
One pass contacts Cloudflare, GitHub’s status host and your selected service’s public status feed. Small requests, not a speed test. No account access.
3D loading · results work independently
Illustrative paths, not a discovered router map. Native results below describe the evidence.
What the checks can tell you.
Not checked
Browser connection hint is advisory.
Nothing measured yet.
Run the small checks to compare browser hints, public connections and a selected service report.
Provider reports are aggregate evidence, not a test of your account.
NEXT STEPS, BASED ON EVIDENCE
Use the result
to narrow it down.
A public route responded?
Your browser reached at least one tested public host. If one app still fails, compare its official report, sign-in status and browser extensions. Other websites can still have problems.
The service reports an incident?
Read the affected products and timestamp on its official page. That report can explain a service issue, but it does not verify the condition of your individual account.
Both public reads are unknown?
Compare another browser or another connection when convenient. CORS, privacy blockers, endpoint restrictions and network failures can produce the same browser result; no router fault is diagnosed here.
Small checks. Specific limits.
Times are browser fetch durations including server work, not calibrated ping or bandwidth. The online/offline hint can reflect a LAN without working Internet. No IP address, packet-loss test, location scan or uploaded speed-test data is displayed or collected by this app. Providers necessarily see normal request information when you run the checks.
Primary references checked 2026-10-05 · No automatic polling