A video call that freezes for half a second, a game that rubber-bands, or a file upload that repeatedly stalls can all point to packet loss. Learning how to test packet loss helps separate a Wi-Fi problem in your home from an ISP issue or a problem with the site or server you are trying to reach.
Packet loss is not always obvious in a speed test. Your download speed may look normal while small pieces of network traffic fail to arrive or arrive too late to be useful. The most useful test is a series of controlled checks: first inside your network, then to the internet, and finally along the route to a destination.
What Packet Loss Means
Internet traffic is broken into small units called packets. Think of them as individually addressed envelopes carrying portions of a webpage, voice call, game update, or email. Your router and ISP forward those packets toward their destination, where they are reassembled.
Packet loss occurs when some packets never make the trip. A small amount of loss may not affect a web page, because many applications can request missing data again. Real-time services have less time to recover. Voice and video calls may sound robotic, cloud gaming may stutter, and online games may show high ping or disconnects.
Loss can happen for several reasons: weak Wi-Fi signal, radio interference, damaged Ethernet cables, overloaded routers, a busy local network, faulty network hardware, congestion at the ISP, or a problem farther along the internet route. The location matters more than the first percentage you see.
How to Test Packet Loss Step by Step
Before testing, pause large downloads, cloud backups, streaming, and game updates if possible. Those activities can create congestion that changes the result. Run each test for long enough to spot an intermittent problem rather than relying on four quick packets.
Start With Your Own Router
Your default gateway is usually your home router. Testing it tells you whether packets are being lost before traffic even leaves your local network.
On Windows, open Command Prompt and enter:
“`text ipconfig “`
Find the value labeled Default Gateway, often something like `192.168.1.1` or `192.168.0.1`. Then run:
“`text ping -n 100 192.168.1.1 “`
On macOS or Linux, open Terminal and use:
“`text ping -c 100 192.168.1.1 “`
Replace the address with your actual gateway. A healthy wired connection to the router should normally show 0% loss and very low response times, often under a few milliseconds. Wi-Fi can add a little variation, but it should not regularly lose packets.
If loss appears here, do not start by blaming your ISP. Move closer to the router, test with an Ethernet cable, restart the router, and inspect cables and ports. If an Ethernet test is clean while Wi-Fi loses packets, the issue is likely wireless coverage, interference, or router placement.
Test a Reliable Public IP Address
Next, test an external address that is unlikely to be affected by DNS lookup issues. A common example is a public DNS resolver such as `1.1.1.1`:
“`text ping -n 100 1.1.1.1 “`
On macOS or Linux:
“`text ping -c 100 1.1.1.1 “`
At the end of the test, look for the packet-loss percentage and minimum, maximum, and average response times. Ideally, loss is 0%. Consistent loss above 1% can affect calls and gaming; 3% to 5% is usually noticeable; higher loss can make a connection unreliable even when speed-test numbers remain high.
Run this test more than once, including when the problem is happening. A clean result at noon does not rule out evening congestion or an issue caused by another device joining your network.
Test the Actual Service That Has a Problem
A public IP test shows general internet reachability, but it does not prove that a specific game server, work VPN, or website is healthy. If only one service has trouble, test its hostname if it responds to ping:
“`text ping -n 100 example.com “`
This check can reveal whether the loss is limited to a destination or route. However, do not treat a failed ping as automatic proof that the server is down. Many websites and services intentionally block or limit ICMP ping replies as a security or capacity measure. The service may still work normally.
For a broader first check, a browser-based ping test from WhatIsMyPublicIP.com can provide a quick result without opening a command window. Repeat the test from your device as well when you need to compare conditions on your own connection.
Use Traceroute to Locate the Trouble
Ping shows whether replies are missing. Traceroute helps show the path packets take through routers, called hops.
On Windows, run:
“`text tracert 1.1.1.1 “`
On macOS or Linux, run:
“`text traceroute 1.1.1.1 “`
The first hop is normally your router. The next few hops typically belong to your ISP, and later hops may belong to backbone providers or the destination network. High response times or timeouts near the first hop can support the case for a local issue. Trouble that begins after traffic reaches your ISP may require the ISP to investigate.
Be careful with a single asterisk or timeout in traceroute. A router can forward traffic normally while choosing not to answer traceroute probes or while rate-limiting those replies. What matters is the pattern. If one middle hop looks bad but every later hop returns normally, that middle router is probably not dropping your real traffic. If high latency or loss begins at one point and continues through every following hop, it is more meaningful.
Compare Wi-Fi and Ethernet Results
This comparison is one of the fastest ways to narrow the cause. Connect a computer directly to the router with a known-good Ethernet cable and repeat the router and public-IP ping tests.
If Ethernet shows 0% loss but Wi-Fi does not, focus on wireless conditions. Place the router in an open, central location rather than inside a cabinet or behind a television. Distance, walls, cordless devices, Bluetooth activity, neighboring networks, and crowded apartment buildings can all interfere with Wi-Fi.
Use the 5 GHz or 6 GHz band when your devices support it and you are reasonably close to the router. These bands often have less interference and higher capacity, though their range through walls is shorter than 2.4 GHz. For a desktop, game console, work computer, or server, Ethernet remains the more predictable choice.
If both wired and wireless tests show loss to the router, try another cable, another router port, and a second device. That helps distinguish a bad cable or network adapter from a router problem.
Interpret Results Without Chasing False Alarms
Packet loss measurements depend on what is being tested. Ping uses ICMP packets, and network equipment may give ICMP lower priority during busy periods. That means 2% loss shown only at an intermediate traceroute hop is not necessarily a user-facing issue.
A stronger diagnosis comes from matching several observations: packet loss to the router, loss to a public address, a traceroute pattern that persists through later hops, and a real application problem at the same time. Keep a short record of dates, times, wired versus Wi-Fi results, and the commands used. If you contact your ISP, this is far more useful than saying the internet feels slow.
Also check whether the problem occurs only while someone is uploading. Consumer connections often have much less upload capacity than download capacity. A saturated upload queue can delay game and call packets, a condition sometimes called bufferbloat, without producing obvious permanent packet loss. Pausing uploads or enabling router quality-of-service settings may improve responsiveness.
When to Contact Your ISP or Replace Equipment
Contact your ISP when a wired device has repeated loss to multiple public destinations, the issue occurs at several times of day, and local tests to your router are clean. Provide the timing, packet-loss percentages, modem status lights, and traceroute results if requested. An ISP can check signal levels, line errors, neighborhood congestion, or a failing modem.
Replace or further investigate local equipment when loss starts at the router, when the router regularly reboots or overheats, or when changing cables and devices changes the outcome. Firmware updates can help, but an older router may struggle with a busy household, many connected devices, or modern Wi-Fi demands.
The key is to test from the inside out. A clean router test, repeated public ping, and a careful traceroute comparison turn packet loss from a vague complaint into evidence you can act on.
