Is It Your WiFi, Your Router, or Your ISP?

By Paul Snyman · Published August 9, 2026 · 6 min read

Something's wrong with your internet, and the maddening part isn't fixing it, it's figuring out what's actually broken. Your phone? Your WiFi? Your router? Your ISP? Restarting the wrong thing wastes ten minutes and tells you nothing. There's a faster way: test in the right order, and each step tells you exactly where to stop looking.

The Four Places a Problem Can Hide

A "no internet" symptom has four possible causes, and they're not equally likely or equally fixable by you:

• Your device - WiFi toggled off, airplane mode, a stale connection to the wrong network
• Your WiFi or router - the access point itself is down, frozen, or your device can't reach it
• Your home network beyond the router - the router's up but the modem or the line to your ISP isn't
• Your ISP - the router and modem are fine, but the outage is upstream, out of your hands entirely

Testing in order, from device outward, means you stop at the first failure instead of guessing. This is exactly what PingKit's Smart Diagnostics automates - six checks, run in sequence, each one isolating a layer before moving to the next.

The 6 Steps, in Order

1. Network Interface

Before anything else: does your device actually have an active WiFi or cellular connection? Sounds obvious, but a surprising number of "internet is down" moments are airplane mode left on, or a phone still trying to hold onto a network it's out of range of.

2. Ping the Gateway

Your router has a local address (often something like 192.168.1.1). Pinging it doesn't touch your ISP at all - it only tests whether your device can reach your own router. If this fails, stop here: the problem is your WiFi or your router, and nothing further downstream matters yet. Try moving closer to the router, or checking whether it needs a restart.

3. Check Internet Reachability

If the gateway responds, the next check pings a public IP address out on the open internet. Gateway reachable but this failing means the problem is upstream of your router - your modem, the physical line, or your ISP. This is the point where a router restart stops being useful and a modem restart or an ISP outage check becomes the right next move.

4. Check DNS Resolution

The internet can be reachable by IP address while DNS - the system that turns a name like example.com into an address - is broken or misconfigured. If step 3 succeeded but a hostname won't resolve, that's a DNS problem specifically, not a real outage. Switching your DNS server (see our guide to changing DNS on iPhone) often resolves it in seconds.

5. Check HTTPS Connectivity

Ping and DNS can both succeed while a real web request still fails - a captive portal that hasn't been accepted yet, content filtering, or a certificate issue can all block this step specifically. It's the closest simulation of "does a website actually load" in the sequence.

6. Download Speed

Once connectivity is confirmed at every layer above, the last check measures throughput. This is where "totally down" and "technically working but painfully slow" split apart - if everything above passed but this number is low, you don't have an outage, you have a performance problem, and Speed Test and our slow WiFi guide are the better next stop.

What This Approach Can't Catch

Smart Diagnostics' reachability check sends two pings and stops at the first success - built for speed, not for catching problems that come and go. A connection that drops for ten seconds every few minutes can pass every step above and still be genuinely broken. For that, two tools are built specifically to catch it:

• Connection Monitor - a live, foreground graph of latency and loss over time, good for watching a connection during a call or stream to see exactly when it degrades. See how to prove your internet keeps dropping for using it as evidence.
• MTR - traces every hop to a destination and shows per-hop loss and latency over many samples, useful for finding exactly which point on the route is dropping packets.

Which Guide to Read Next

This is the triage step - once you know roughly where the problem lives, one of these covers the specific fix:

• Gateway step failed, or WiFi seems to be the issue: How to Fix Slow WiFi on iPhone
• Connected but nothing loads: "Connected to WiFi But No Internet"
• Works, then drops, repeatedly: Why Does My Internet Keep Disconnecting?
• Connected and stable, just slow at certain times: How to Tell If Your ISP Is Throttling