Diagnosis

Is It Your WiFi or Your Internet? How to Actually Tell the Difference

"The internet is down" is rarely precise enough to actually fix anything. Before you reset the router, call your ISP, or buy a new mesh system, it's worth spending two minutes working out which of two genuinely different problems you actually have.

WiFi and "the internet" are two separate links in a chain, and a failure in either one looks identical to the person sitting at their desk:

WiFi — the radio connection between your device and your router, entirely inside your building, under your control.
Your internet connection — the link from your router out to your ISP and the wider internet, which is largely out of your control and depends on your provider's network.

Misdiagnosing which one is broken wastes time and money in both directions — people buy expensive new routers to fix what was actually an ISP outage, and people call their ISP to complain about an outage that was actually a weak signal in one corner of the office.

The quick test

Stand right next to the router

Connect a laptop or phone as close to the router as physically possible — ideally in the same room, a few feet away. This removes distance and walls from the equation entirely.

Run a speed test from there

If speed and ping are normal right next to the router, but bad elsewhere in the building, that's a strong sign the problem is WiFi coverage, not your internet connection.

Plug in directly with an ethernet cable, if you can

This is the single most decisive test available. If a wired connection to the router is also slow or unstable, WiFi is innocent — the problem is your router, your internet connection, or your ISP.

Check if it happens consistently, or only sometimes

A problem that's there 100% of the time, everywhere in the building, points toward your internet connection or ISP. A problem that comes and goes, or only happens in specific spots, points toward WiFi — interference, congestion, or coverage.

📶 Signs it's WiFi

Fine when wired directly into the router
Fine in one room, bad in another
Fine on 5GHz, bad on 2.4GHz (or vice versa)
Improves when you move closer to the router
Gets worse with more people/devices connected

🌐 Signs it's your internet / ISP

Bad even wired directly into the router
Bad everywhere in the building equally
Bad on both WiFi bands equally
Speed test shows far less than your plan promises
Happens at consistent times of day (peak-hour congestion)

Why a single test still isn't enough

The quick test above is genuinely useful for a one-off check, but it has a real limitation: it only tells you about this exact moment. Both WiFi problems and ISP problems are very often intermittent — fine when you happen to check, bad at 8am or during a specific weekly call. If you only test when you remember to, you'll systematically miss the actual pattern.

This is the gap that trips up most troubleshooting. Someone complains the WiFi was terrible during their 9am call. By the time you check at 11am, everything looks fine — not because the problem didn't happen, but because intermittent problems are, by definition, not always happening.

The only real fix for intermittent problems is continuous testing. Something needs to be checking ping, speed, and signal strength on a schedule — every few minutes, around the clock — and keeping a record, so that when someone reports a problem, you can go back and look at exactly what was happening at that time instead of relying on memory or re-testing after the fact.

What good continuous testing actually checks

To properly separate WiFi problems from internet problems automatically, a monitoring setup needs to test several things separately, not just bundle everything into one "is the internet OK" number:

Ping to the router (gateway) — tests purely the local network and WiFi link, nothing further
Ping to somewhere external — tests the full path out to the internet, isolating ISP-level issues
Speed test — actual throughput, not just whether a connection exists
Signal strength and link quality — the WiFi-specific numbers that explain why, not just that, something's wrong
DNS resolution time — a surprisingly common, often-overlooked cause of "the internet feels slow" that isn't really a bandwidth problem at all

Testing each of these separately, on both WiFi bands, is what actually lets you say with confidence "the gateway ping was fine but external ping spiked at 9:03am — that's an ISP issue, not your office WiFi" rather than just "something was wrong."

This is exactly what Neto does, automatically

Neto tests gateway ping, external ping, speed, DNS, and signal strength on both your 2.4GHz and 5GHz bands every 5 minutes — so the next time something seems off, you have an actual record instead of a guess.

▶ See a live demo

The short version

WiFi problems and internet problems feel the same to the person using the connection, but they're fixed completely differently — and you can't reliably tell them apart from memory or a single check. A quick wired-vs-wireless test will get you most of the way for a one-off issue; genuinely intermittent problems need continuous, automated monitoring to actually pin down.

If you haven't already, it's worth reading how WiFi actually works for the underlying concepts referenced here, or the common causes and fixes once you've confirmed it genuinely is a WiFi problem rather than your internet connection.