How much packet loss is acceptable?

On a wired connection, 0% packet loss is normal, and anything that stays above 1% is worth fixing. Our limits are 1% or less for competitive games, 2% or less for video calls and 5% or less for 4K streaming. A little loss on Wi-Fi or 5G home internet is common; steady loss on a cable usually points to a fault.

Packet loss ranges

Data crosses the internet in small packets. Packet loss is the share that never arrives. Our test sends a burst of small UDP messages, the kind games and calls use, through Cloudflare's relay and counts how many come back.

Packet loss What it means Competitive gaming Video calls 4K streaming
0% Normal, especially on a cable. Yes Yes Yes
Under 1% Common on Wi-Fi; usually unnoticed. Yes Yes Yes
1–2% Noticeable in fast games. No (our limit is 1%) Yes Yes
2–5% Calls cut out; games feel broken. No No (our limit is 2%) Yes
Over 5% Something is wrong. Everything suffers. No No No (our limit is 5%)

These limits are our thresholds, the same ones the test's verdict uses (how it works explains them). A result exactly on a limit passes.

Why a little loss hurts so much

Most web traffic runs over TCP, which notices a missing packet and sends it again. You don't see the gap; the page or download just slows down for a moment.

Games and calls usually use UDP, which doesn't resend. By the time a resent packet arrived, it would be too late to matter. So a lost packet is simply gone:

  • In a game, a lost update means a shot that doesn't register, or a player who jumps when the next update arrives. The verdict puts it as "shots and moves will go missing."
  • In a call, lost audio packets become gaps and clipped words. The app can paper over a few; at a few percent, voices cut out.
  • In streaming, the player has a buffer and can fetch data again, so it copes with more loss. Past our 5% limit, the verdict warns that the picture will drop in quality.

Normal, worth watching, worth fixing

  • 0% on a cable: normal. This is what a healthy wired connection looks like.
  • Under 1% on Wi-Fi or 5G home internet: common and usually fine. Wireless links lose a packet now and then and recover.
  • Above 1%, run after run: worth fixing. A steady loss on a cable points to a fault: a damaged or loose cable, a failing modem or router, a line problem outside your home, or a busy provider network.
  • Loss only at certain times: note when. Evening-only loss suggests congestion on your provider's side; loss whenever someone downloads suggests bufferbloat filling your router's queue until it drops packets.

One test is a snapshot. A single 1% reading can be a blip. Run the packet loss test three or four times, on a cable if you can, before you act.

A worked example

Say three runs on Wi-Fi show 2%, 0% and 3% loss, and three runs on a cable show 0%, 0% and 0%.

  • On Wi-Fi, two of three runs fail our 2% call limit. Calls on that device will cut out at times.
  • On the cable, the line itself is clean.
  • So the loss is happening between the device and the router. The packet loss guide and high ping on Wi-Fi cover what to change.

If the cable runs had shown loss too, the next steps would be the modem and router, then your provider. Keep a note of the results and times: they make the support call much shorter.

When the test can't measure loss

The loss test needs UDP and WebRTC, which some networks and browser privacy settings block, such as some workplace and school networks. When that happens, the result says so instead of showing a number. The rest of the test (ping, jitter and speed) still stands.