Affiliate Disclosure: This article may contain affiliate links. If you purchase through these links, we may earn a commission at no extra cost to you.
Quick answer: Open a terminal and run ping 8.8.8.8 -n 100 (Windows) or ping -c 100 8.8.8.8 (Mac): the summary shows your loss percentage. Then ping your router’s own address the same way. Loss to the router means a local WiFi or cable problem, fix that first. Clean local results with loss to the internet means router firmware, congestion or the ISP line.
Step 1 – Measure it properly
One hundred pings give a real percentage instead of a feeling. Test three targets: your router (gateway IP), a public DNS like 8.8.8.8, and the game or meeting server region if you know it. Write the three numbers down, they tell you where the problem lives.
Step 2 – If loss appears to your own router: fix the local link
- Go wired for the test: if Ethernet shows zero loss, WiFi is the entire problem.
- Move or re-aim: every wall costs signal, and 5GHz drops faster with distance than 2.4GHz.
- Change the channel: in dense buildings, a congested channel corrupts frames constantly. Auto channel after a router reboot usually picks better.
- Replace suspect cables: a kinked or half-clipped Ethernet cable produces classic intermittent loss.
Step 3 – If local is clean: work outward
Reboot modem and router (yes, really: it clears degraded state and forces a fresh channel scan). Update router firmware, old firmware has known bufferbloat and NAT table bugs that show up as loss under load. If loss only appears while someone streams or downloads, enable QoS / Smart Queue so bulk traffic cannot starve your game packets.
Step 4 – Build the ISP case
Run tracert 8.8.8.8, note the first hop after your router, and ping it 200 times wired at two different times of day. Sustained loss there is on the ISP line: congested node, degraded coax, or a failing modem. Send them the numbers; vague complaints get script responses, percentages get engineers.
When the hardware is the bottleneck
Routers from the WiFi 4/5 era drop packets under modern loads of dozens of devices. If your unit is more than five or six years old, an upgrade removes a whole class of problems: see our tested budget WiFi 6 routers, mesh systems for gaming and modem-router combos for cable internet.
Frequently asked questions
What is an acceptable packet loss percentage?
Zero is the target on a healthy wired connection. Up to 1% is tolerable for browsing and streaming but already noticeable in fast games and calls. Anything above 2 to 3% sustained means something is wrong: rubber-banding in games, robotic audio and frozen video frames.
Can WiFi cause packet loss?
WiFi is the number one source in homes. Distance, walls, and interference from neighboring networks or microwaves all corrupt frames that then need resending. If loss disappears when you test over an Ethernet cable, the wireless link is your culprit: move closer, change channels, or upgrade the router or mesh.
How do I prove packet loss to my ISP?
Run ping tests to your own gateway (no loss expected), then to the first hop outside your network from a tracert, then to a public server like 8.8.8.8, each for a few hundred packets, wired. Zero loss inside plus consistent loss at the ISP hop, captured at different hours, is exactly the evidence a support engineer needs.
Test wired first, blame the right layer, and the fix is usually simple: a cable, a channel change, a router that is not ten years old, or a firm call to the ISP with numbers in hand.
