We have all been there. You are trying to download a massive file, join a Zoom call, or play a game, and the internet is stuttering. You call your internet service provider (ISP), and they ask you to run a speed test. You do, it says you have 300 Mbps, and they proudly tell you, "Everything looks fine on our end."

They hang up, and your internet is still garbage.

Here is the harsh truth: Speed tests only measure bandwidth (how wide the pipe is), not latency or packet loss (how bumpy the ride is).

If your internet feels slow, it’s usually because of packet loss—data literally being dropped before it reaches you. And Windows has a hidden, built-in command that doesn't just tell you if you have packet loss, but proves exactly where it is happening. It's called pathping.

Here is exactly how to use this command, read the data like a network engineer, and force your ISP to actually fix your connection.

Why Ping and Tracert Are Useless

Most tech tutorials tell you to use ping or tracert.

  • ping tells you if a server is responding. It doesn't tell you why your video call is freezing.
  • tracert (trace route) shows you the path your data takes to reach a website, hop by hop, but it only gives you a snapshot.

pathping is the combination of both, and it is brutal.

It sends hundreds of packets to every single router (hop) along the path to a destination over the course of several minutes. It calculates the exact percentage of packet loss at every step. This means you can visually see the exact router that is failing and dropping your data.

Step 1: Open Command Prompt

You don't need Administrator privileges for this, but it's good practice.

  1. Open your Start menu, type cmd, and open the Command Prompt.
  2. To test your connection, you need a stable, reliable target. We will use Google's primary DNS server, which never goes down.

Type this command and press Enter:

bash

pathping 8.8.8.8

Step 2: Wait (This Takes a Minute)

When you hit Enter, you will see the first section print out instantly. It looks like this:

text

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
  0  MyPC.lan [192.168.1.15]
  1  192.168.1.1
  2  10.20.0.1
  3  isp-router-1.dhcp.net [24.12.1.5]

This shows the physical path your data is taking. The 192.168.1.1 is your home router. The 10.20.0.1 is your neighborhood node. The rest are the ISP's major routers.

Do not close the window. You will now see a message saying Computing statistics for 75 seconds... (or up to 325 seconds). Let it run. Go make a cup of tea.

Step 3: Reading the Stats (Finding the Culprit)

Once the test finishes, pathping prints a massive table. It looks terrifying, but you only need to look at the last two columns: Lost/Sent and %Loss.

text

              Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           MyPC.lan [192.168.1.15]
                                0/ 100 =  0%   |
  1    1ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2    5ms     0/ 100 =  0%     0/ 100 =  0%  10.20.0.1
                                10/ 100 = 10%   |
  3   11ms    10/ 100 = 10%     0/ 100 =  0%  isp-router-1.dhcp.net [24.12.1.5]

How to read this:

  1. Hop 0 is your PC. If you see packet loss here, your Wi-Fi card or Ethernet cable is bad.
  2. Hop 1 is your router. If you see loss here (e.g., 5%), your router is dying, or you are too far from the Wi-Fi.
  3. Look at the This Node/Link column. This is where the magic happens. It shows the loss that occurred specifically at that hop.
  4. In the example above, Hop 2 shows 10/100 = 10%. This means the link between your ISP's local node and their main router is dropping 10% of your data.

If you see 0% loss all the way down to the destination, but your internet still feels slow, the problem is likely the server you are connecting to, not your internet.

Step 4: Confronting Your ISP

If you see packet loss (anything above 1% or 2%), you now have the ultimate weapon.

When you call your ISP, do not say, "My internet is slow." They will run a script, see your bandwidth is fine, and tell you to restart your router.

Instead, tell them this:

"I ran a pathping to 8.8.8.8. I am experiencing a consistent 15% packet loss at the hop [insert IP address here]. The issue is on your network, not my home equipment. I need a technician to check the node, or I am switching providers."

I have used this exact strategy multiple times. The moment you speak their language and provide their own IP addresses showing where the failure is, they stop treating you like a casual user and escalate you to Tier 2 support. They know they can't bluff their way out of raw diagnostic data.

What to do after you fix your internet?

Once you have a stable connection, it's time to make sure your PC isn't adding to the problem. If your network is blazing fast but your computer is freezing up while you try to browse, you need to check your system resources.

Read our guide on The Secret Windows Command to Instantly Find What is Eating Your RAM to find out if a rogue background app is secretly hogging your system.

And if you want to make sure your files are safe while you troubleshoot, run The Secret Windows Command to Instantly See Every Crash and Error on Your PC.

Stop letting your ISP gaslight you. Run the command, get the proof, and get the internet you are paying for.