Your network bottleneck is hiding in a Windows command most people never run

After a 7-year corporate stint, Tanveer found his love for writing and tech too much to resist. An MBA in Marketing and the owner of a PC building business, he writes on PC hardware, technology, and Windows. When not scouring the web for ideas, he can be found building PCs, watching anime, or playing Smash Karts on his RTX 3080 (sigh).

When your internet feels slower than it should be, the first instinct is probably to run a speed test. If it doesn't reveal anything unusual, you probably blame your ISP, router settings, or even Windows itself. Most people start going through commonly suggested fixes to improve internet performance, but Windows has a built-in network diagnostic that tells you exactly where your connection is failing.

The "pathping" command sends hundreds of packets to each step of your connection, showing you the latency for each of them. From your router to the ISP to the website you're trying to reach, it reveals the bottleneck in the chain, so you're better informed. It arms you with the information you need to choose the right fixes, or at least stop wasting time on the ones addressing the wrong thing.

Blaming your router or ISP without data gets you nowhere

It's better to talk numbers

Your internet might work perfectly most days of the month, but even those few days of sluggish connectivity can be frustrating. When normal speed tests don't spot anything fishy, you realize you need to get serious. Restarting your router, rechecking Windows network settings, changing your DNS servers, or considering a plan change are the things probably running through your mind.

One or more random fixes might even solve your internet woes, or an external bottleneck might resolve itself in a few hours or days. However, unless you know where exactly the issue was, you'll be clueless if or when it comes back. While there are numerous Windows commands and diagnostics to extract data about your network activity, "pathping" is the one most users should start with.

The pathping command gives you the insight you always needed

Let there be light

While commands like "ping" and "tracert" shed light on parts of the problem, pathping combines the two. It traces the complete route to the destination server and pings every hop along the way to calculate the packet loss and latency. It works by sending ICMP Echo Request messages to every intermediate router for a given time period, essentially sending 100 packets to every hop.

It can take some time to complete the test, but the results, displayed right there in the Command Prompt window, can be quite useful. The first part of the test lists every stop from your PC to the supplied server, be it a router, gateway, or node. The next phase pings each of those hops and measures the round-trip time to and from the hop and the packet loss.

The "Source to Here" column refers to the path from your PC to that hop, while the "This Node/Link" refers to the individual hop or the connection between nodes. To illustrate the test, I enabled a VPN before running the test and ran the following command: pathping escapetheordinaryweb.wordpress.com You can see a massive 169ms delay between the PC and the first hop, i.e., the router. You can also see 99% packet loss between hops 1 and 2 (i.e., my router and the ISP), so none of the subsequent hops received any traffic. My VPN is the one causing all the chaos here, but if you see a similar result on your PC without anything obvious slowing you down, you can conclude that the ISP is suffering from network congestion.

It tells you where to look, so you're not shooting in the dark

You can save a lot of wasted troubleshooting

Credit:  

In most cases, you will see a minimal round-trip time (RTT) or delay between your PC and the router (1ms to 5ms). This is typical for your home router, and you can safely rule out any misconfigured router settings, bad Ethernet cable, or a poor Wi-Fi signal. A sudden jump in latency on hop 2 or 3 means that your ISP's servers are at fault. You should raise a ticket at this point and wait for things to be resolved at their end.

If the latency and packet loss increase at the later hops or the destination, things are beyond the control of your ISP. There's little you can do in this scenario, but you at least know what's causing the slowdown. The external glitch will probably resolve itself soon, but until then, you can stop blaming your PC, router, or the ISP.

Built-in Windows diagnostics are underrated

Most Windows users don't know that the OS hides several useful commands and tools. While DISM and SFC scans have become more well-known in recent years, tools like Resource Monitor, Performance Monitor, and Event Viewer are still underutilized. Networking diagnostic commands like pathping offer a quick and simple way to unearth more data about network slowdown on your Windows PC.