How to Fix Packet Loss (Gaming, Calls and Streaming)

What packet loss is

Packet loss is data that leaves one end of the connection and never arrives at the other. Internet traffic travels in small packets; a few vanishing is routine and invisible, but loss that repeats during a game or call breaks the experience, because live data can't be paused and resent later without a gap.

Loss is not the same as its two companions on a bad connection: latency (the delay before data arrives) and jitter (how much that delay moves around). High latency makes everything late; loss makes pieces of it missing. They often travel together — a flaky Wi-Fi link adds all three at once.

Check for loss with ping

The built-in ping command sends small packets to a server and reports every one that never comes back:

• Windows: open Command Prompt and run ping -t 1.1.1.1. Let it run while the problem happens, then stop it with Ctrl+C. The summary shows "Sent / Received / Lost".
• macOS: Terminal, ping 1.1.1.1 (it runs until you stop it with Ctrl+C).
• During the fault: "Request timed out" lines appearing while you stutter or rubber-band are the loss you're hunting. Lines that simply show high times are latency, not loss.

Most competitive games and many voice apps also show a loss figure in their connection or network-stats overlay — if it climbs exactly when the symptoms start, you've confirmed it without any command line.

Fix 1: the Wi-Fi link

Wireless is where most household loss begins: weak signal, walls, and interference from neighbouring networks and microwave ovens all drop packets before they reach the router.

1. Plug in a cable for the session — the definitive test and often the definitive fix. If loss stops on Ethernet, it was the Wi-Fi.
2. Move closer or move the router to a central, raised, open spot.
3. Use the 5 GHz band in nearby rooms (less interference), keep 2.4 GHz for distance.
4. Update the device's Wi-Fi driver — a single affected laptop dropping packets is the classic driver symptom.

Fix 2: a connection that's full

When every packet has to queue behind a big download or upload, some get dropped. This is bufferbloat's nasty sibling — the same cause (a filled link), showing up as both lag and loss.

1. Notice the timing. Loss that appears only while a game update, cloud backup or someone's upload runs is congestion, not a fault.
2. Schedule big transfers for overnight or pause them for the match or call.
3. Turn on SQM or QoS on your router, so real-time traffic is prioritised instead of queued behind bulk data. The bufferbloat test shows how your connection behaves under exactly this load.

Fix 3: equipment and cables

Packets die in tired hardware too: an overheating router, a damaged Ethernet cable, or a loose connector between the wall and the modem. Restart the router (30 seconds unplugged), update its firmware, and swap any cable that's bent sharply, pinched by furniture or aged. If the drops also take the whole connection down — not just your game — read why your internet keeps disconnecting; that's a different fault with overlapping suspects.

Fix 4: routing and VPNs

Between you and the game server sit many hops, and any of them can lose packets. A VPN usually adds distance and delay, but occasionally fixes loss by routing around a bad path — test with it off first, then on, and keep whichever loses less. In games, picking the server region nearest to you shortens the path and removes whole chunks of the internet from the equation. More on that: how to lower ping in games.

Fix 5: the line and your provider

If a cable-connected computer, on a quiet connection, with the router restarted, still shows loss to multiple destinations — the fault is on the line or the provider's network. Collect your ping summaries (times, dates, per-cent lost) and report them; recurring line faults usually need an engineer. On copper lines, loss that worsens in wet weather is a strong clue to give them.

What loss does to each activity

Questions