Router Diagnostics
Best-effort reachability checks for your home gateway, plus a practical router health checklist to fix drops, dead spots and laggy connections.
Can your browser reach the router?
We try to load a resource from common gateway addresses and time the response. This is a rough, best-effort signal — see the honest limits below.
Router health checklist
The fixes that resolve most home network complaints — free, in order of impact.
- Reboot on a schedule A monthly power-cycle clears memory leaks and stale connections that quietly slow an ageing router.
- Update the firmware Outdated firmware is the #1 cause of drops and security holes. Check the admin page for an update.
- Place it high and central Routers radiate downward and outward. Out in the open, off the floor, away from metal and microwaves.
- Split or band-steer your bands Keep 5 GHz for nearby fast devices and 2.4 GHz for range and smart-home gear.
- Turn on SQM / QoS Smart Queue Management tames bufferbloat — the latency-under-load that wrecks calls and gaming.
- Change the admin password If it's still admin/admin, change it. A compromised router is a compromised network.
How router diagnostics works in a browser
A real router diagnostic uses tools like ping
and traceroute, which need
operating-system access browsers don't have. What a browser can do is
ask to load a resource from an address and measure how long that takes — or
whether it fails fast. We run that best-effort check against the gateway
addresses most home routers use, plus any custom IP you enter.
Treat the result as a hint, not a verdict. Because this page uses HTTPS and
most routers answer over plain HTTP, the browser often blocks the request
before it reaches your router — a security feature, not a fault. The most
reliable browser test is simply opening your router's admin address (for
example http://192.168.1.1) in a
new tab: if the login page appears, the router is reachable.
How to read the results
- Responded: the address answered quickly — that device is alive on your network.
- Blocked / opaque: the browser stopped the request (mixed content or CORS). Inconclusive — confirm by opening the admin page.
- No response: the request timed out. The address may be wrong, or that device isn't your gateway.
If reachability looks fine but your connection still misbehaves, the problem is rarely the router being "down" — it's usually placement, an overloaded Wi-Fi channel, or bufferbloat. Work through the health checklist above first.
Frequently asked questions
Why can't the browser just ping my router?
Browsers have no access to ICMP ping or raw sockets — that's an operating-system privilege. We can only ask the browser to request a resource from an address and time the response, which is a rough, best-effort signal, not a true ping.
Why do all my gateways show as unreachable?
Two common reasons. First, this page is served over HTTPS and most routers answer over plain HTTP, so the browser blocks the request as mixed content. Second, routers usually don't expose a file the browser is allowed to read. A blocked result here does not mean your router is down.
What is my gateway IP and how do I find it?
It's the address of your router on your local network — often 192.168.1.1 or 192.168.0.1. On Windows run ipconfig and read "Default Gateway"; on macOS or Linux run ip route or netstat -nr. Type it into the field above to test it directly.
Is it safe to run this test?
Yes. Everything happens in your browser, we never store your addresses, and the test only tries to reach devices already on your own network. No credentials are sent and nothing leaves the page.
Not sure if it's the router or the line?
The Doctor runs the full panel and tells you whether the culprit is your router, your Wi-Fi or your ISP — in plain English, with the fix ranked by impact.