How can I tell if my internet is slow because of my ISP?

Ping your router (often 192.168.1.1) and then an internet address like 1.1.1.1. If the router answers fast (1–5 ms) but the internet address is slow or drops packets, the fault is past your router — the ISP side. If even the router is slow from one machine, the problem is inside your home or on that machine.

Does a speed test tell me whether it's the network or my computer?

Only half. A speed test measures the path from that one device to one server at one moment. A bad result doesn't say whether the path or the device is at fault — that's why the two-device comparison matters. A good result while the machine still feels slow points the finger firmly at the machine.

How do I prove to my ISP that the problem is on their side?

Collect evidence over time, not one screenshot: repeated speed tests from two different devices, ping results to your gateway (fast, clean) versus the internet (slow, packet loss), ideally at different times of day. Continuous monitoring for a few days — with timestamps — is what support desks find hard to wave away.

What free tool tells me if it's the network or the machine automatically?

Acutis Go is a free 7 MB agent for Windows, macOS, and Linux that runs the checks in this guide — path, Wi-Fi signal, DNS, gateway, plus local CPU, RAM, drivers, and certificates — every 60 seconds, and states a plain verdict: network issue or machine issue, with confidence. It's observe-only: it reads signals and reports; it never changes settings or opens ports.

What's the difference between a network fault and a machine fault?

A network fault lives outside your device: Wi-Fi interference, a struggling router, DNS failures, ISP congestion, or an outage. A machine fault lives inside it: overloaded CPU or RAM, bad drivers, misconfigured VPN or DNS settings, malware, or failing hardware. The split matters because the fixes are completely different — restarting a router won't fix a driver, and reinstalling Windows won't fix your ISP.

Is it the network or the machine? How to tell in 60 seconds

Q: How do I know if it's my Wi-Fi or my laptop?

Run the same speed test on your laptop and on your phone, standing in the same spot on the same Wi-Fi. If both are slow, it's the network (Wi-Fi, router, or ISP). If only the laptop is slow, the laptop is the problem — look at its Wi-Fi adapter, drivers, CPU load, or VPN.

Q: Why is the internet slow on only one device?

When one device is slow and everything else is fine, the network is innocent. Usual causes on that device: a busy CPU or full RAM, an old or misbehaving network driver, a VPN or proxy in the path, a security product scanning traffic, power-saving throttling the Wi-Fi adapter, or a weak signal to that device's position.

Acutis · plain-English network help · updated July 2026

The short answer: compare two devices, then split the path. Run the same speed test on your computer and on your phone, on the same Wi-Fi, in the same spot. Both slow → it's the network. Only one slow → it's that machine. Then ping your router and an internet address: if the router answers fast but the internet doesn't, the fault is past your house — the ISP side. Those two checks take about a minute and settle most cases.

"The internet is slow" is the most common complaint in computing, and the least specific. The slowness you feel is one number — but it's produced by two very different suspects: the network (Wi-Fi, router, cabling, DNS, your ISP) and the machine (CPU, memory, drivers, VPNs, security software). Fixing the wrong one wastes an evening. This page is the fast, honest way to split them.

The 60-second method

The two-device test. Same speed test (any of them — ours is here), two devices, same Wi-Fi, same spot. Two slow devices can't both be broken the same way — that's the network. One slow device while its neighbor flies — that's the machine.
Split the path. Open a terminal and ping your router, then the internet:
ping 192.168.1.1 (your gateway — find yours with this guide)
ping 1.1.1.1 (the internet)
Router fast (1–5 ms, no loss) + internet slow or dropping → the problem is past your router, on the ISP side. Router itself slow or lossy from one machine → the problem is inside the house, or inside that machine.
Glance at the machine. Task Manager (Windows) or Activity Monitor (Mac): CPU pinned near 100%? Memory maxed? Disk thrashing? A machine drowning in its own work makes a perfect network look broken.

Where the fault can hide

Every click you make crosses the same chain: your machine → Wi-Fi → router → modem → ISP → the internet. A fault anywhere in the chain feels identical from the couch — a spinner. The whole game is finding which link broke, and the checks above walk the chain from your keyboard outward.

Symptom table: what it usually means

What you see	Usual culprit	Why
Every device in the house is slow	Network	Shared fault upstream — router, modem, or ISP
Only one computer is slow	Machine	The network serves everyone else fine
Speed test is fine, but everything feels slow	Machine	Local: CPU, RAM, disk, browser, or malware
Video calls stutter, downloads are fine	Network	Latency/jitter problem, not bandwidth — often Wi-Fi
Works on Ethernet, not on Wi-Fi	Network	Wireless-side: signal, interference, channel, or the adapter
Websites fail but pings succeed	Either	Usually DNS — test if it's DNS; can be set per-machine or per-network
Slow only at certain times of day	Network	Congestion — your ISP's neighborhood segment at peak hours
Slow right after startup, then normal	Machine	Startup programs and updates competing for disk/CPU

Say it precisely: the two kinds of fault

Network fault: A failure outside your device: weak Wi-Fi signal or interference, an overloaded router, failing modem, DNS not resolving, or congestion and outages on the ISP side. Fingerprint: more than one device suffers.
Machine fault: A failure inside your device: exhausted CPU or memory, an old or crashing network driver, a VPN or proxy inserted into the path, security software scanning every packet, or failing hardware. Fingerprint: the machine underperforms even on a healthy network.

The split matters because the fixes never overlap. Restarting the router will not fix a driver. Reinstalling Windows will not fix your ISP. Diagnosing first isn't perfectionism — it's the shortcut.

When you need evidence, not a feeling

One good speed test proves almost nothing — networks fail intermittently. The 3 p.m. slowdown that's gone by 3:20 is invisible to any spot check, and it's exactly the case where households blame the laptop, offices blame the "slow computer," and ISPs blame you. What settles arguments is the same checks, repeated over time, with timestamps: speed and latency from more than one device, gateway-vs-internet pings, Wi-Fi signal, and the machine's own vitals, logged across days.

You can do that by hand with a spreadsheet and discipline. Nobody does. That's the gap the tool below closes.

Or let something watch for you

Acutis Go is a free, 7 MB agent for Windows, macOS, and Linux that runs this page's method continuously — path, gateway, DNS, Wi-Fi signal, plus the machine's CPU, memory, drivers, and certificates — every 60 seconds. It states its conclusion in plain words: "Network issue — likely not your PC" or "This PC needs attention," with a confidence score. It's observe-only by construction: it reads signals and reports; it never changes settings, and it opens no inbound ports.

Get Acutis Go — free How it compares to doing it by hand →

Frequently asked questions

How do I know if it's my Wi-Fi or my laptop?

Run the same speed test on your laptop and your phone, same Wi-Fi, same spot. Both slow → the network (Wi-Fi, router, or ISP). Only the laptop slow → the laptop: check its Wi-Fi adapter and driver, CPU load, and whether a VPN is in the path.

How can I tell if it's my ISP?

Ping your router (often 192.168.1.1) and then 1.1.1.1. Router fast + internet slow or lossy → the fault is past your router, on the ISP side. Repeat it a few times across the day; ISP congestion is usually time-of-day shaped.

Why is the internet slow on only one device?

Then the network is innocent. On that device, look at: CPU/RAM exhaustion, an outdated network driver, a VPN or proxy, security software inspecting traffic, power-saving throttling the wireless adapter, or simply a worse radio position than your other devices.

Does a speed test settle it?

Half of it. A speed test measures one path from one device at one moment — a bad number doesn't say which side broke. Comparing two devices is what turns the number into a verdict. And a good number while the machine still crawls points at the machine.

How do I prove it to my ISP?

Evidence over time: repeated two-device speed tests, gateway-vs-internet pings showing loss past the router, timestamps across several days. A log is hard to wave away; a single angry screenshot is easy.

Is there a free tool that just tells me?

Acutis Go — a free 7 MB observe-only agent that runs these checks every 60 seconds on Windows, macOS, or Linux and states the verdict plainly, with history you can show an ISP or a helpdesk.

Stop guessing — get the verdict on every machine

One agent per computer, a plain answer per problem: network, or machine. Free, observe-only, no credit card.

Get Acutis Go — free