What Is Packet Loss?

Everything you send or receive online is split into small packets. Packet loss is the share of those packets that never arrive. A little can go unnoticed; a little more can ruin a call or a game.

Updated October 6, 2026 · How we write our guides

What a packet is

Data online travels in small chunks, typically up to about 1,500 bytes each. A single web page might be hundreds of packets; a minute of video call is thousands. Each packet finds its own way across the network and is reassembled at the other end.

What packet loss does

What happens when packets go missing depends on the kind of traffic:

  • Web pages, downloads, streaming (TCP): missing packets are sent again. You don’t see errors, but each resend takes time, and TCP slows down when it detects loss. Pages load slower and download speeds drop.
  • Calls and games (usually UDP): there is no time to resend; by the time a replacement arrived it would be too late. The app fills the gap as best it can. You hear dropped syllables, see blocky or frozen video, or watch other players jump around.

Why packets get lost

  • Congestion: when a router’s queue is full, new packets are dropped.
  • WiFi problems: interference and weak signal corrupt packets in the air. WiFi retries, but sometimes gives up.
  • Faulty hardware or cables: a damaged Ethernet cable, a loose coax connector or an overheating router.
  • Line faults on your provider’s network, such as noise on a DSL line or a failing cable amplifier.
  • Deliberate dropping: some networks drop certain traffic, or limit it, by policy.

How much packet loss is too much?

LossTypical effect
0%Ideal. Most healthy wired connections show none in a short test.
Under 1%Rarely noticed outside calls and games. Microsoft’s Teams guidance targets under 1%.
1–2.5%Noticeable glitches in calls and games; slower downloads over long distances.
Over 2.5%Real-time apps struggle badly; the connection feels unreliable.

Loss often comes in bursts. A connection can show 0% in one test and 3% a few minutes later. Several tests over a day give a fairer picture.

How a speed test measures packet loss

Because normal web requests hide loss by resending, our test uses a different route: WebRTC, the technology browsers use for calls. It opens a UDP connection through a TURN relay server on Cloudflare’s network, sends 1,000 numbered packets, and counts how many come back. If the UDP connection can’t be made, which happens on some networks, VPNs and firewalls, the result says “not available” instead of guessing.

Frequently asked questions

How is packet loss shown?

As a percentage of packets sent that never arrived. If 1,000 packets are sent and 5 go missing, that is 0.5% packet loss.

Does packet loss slow down downloads?

Yes. Downloads use TCP, which resends lost packets and slows down when it detects loss. Even small amounts of loss can noticeably reduce download speed over long distances.

Is packet loss always my provider’s fault?

No. WiFi problems, faulty cables, overloaded routers and busy devices on your own network are common causes. Test over a cable first to find out where the loss starts.

Sources

  1. Understand Teams network requirements Microsoft Learn

    Targets: round-trip latency under 100 ms, jitter under 30 ms, packet loss under 1%.

    Checked October 2026

  2. Cloudflare Realtime TURN service Cloudflare Docs

    The relay used to send and count UDP packets in the packet loss test.

    Checked October 2026

  3. @cloudflare/speedtest (measurement engine source and documentation) Cloudflare

    How download, upload, latency, jitter and packet loss are measured by the engine this site uses.

    Checked October 2026