Packet loss test

Press Start and the test sends a burst of small UDP messages through Cloudflare's relay and counts how many never come back. 0% is normal on a healthy line. Up to 1% is fine for competitive games, up to 2% for video calls. More than that, shots go missing and voices cut out. One bad run can be bad luck, so test again, and test while the problem is happening.

The test needs JavaScript.

Packet loss
–
Ping
–
Jitter
–

What packet loss is

Everything you send online is cut into small packets. Packet loss is the share of those packets that never arrive. It's written as a percentage: 1% means one packet in a hundred went missing.

For a download or a web page, loss mostly goes unnoticed. The connection asks for the missing packets again and waits for them, so the page just loads a little slower. Games and calls can't wait. They send moves and sound live, over UDP, and a packet that arrives late is as useless as one that never arrives. So in a game, loss looks like shots that don't register, players who teleport and moves that rubber-band back. On a call, it sounds like words cutting out.

How this test measures loss

A web page can't send the raw packets that tools like ping or mtr use, because browsers don't allow it. What a browser can do is open a WebRTC connection, the same technology video-call sites use. So the test:

  1. gets short-lived login details for Cloudflare's TURN relay from our server (they expire after a few minutes);
  2. opens a WebRTC data channel that goes from your browser, out to the nearest Cloudflare relay, and back to your browser;
  3. sets the channel to UDP-style delivery: nothing is sent twice and nothing waits for order, so a lost message stays lost;
  4. sends a burst of small numbered messages and counts how many come back within a few seconds.

The share that never returns is your packet loss. For example, if 500 messages go out and 495 return, loss is 1%.

The relay is Cloudflare Realtime TURN, which runs on Cloudflare's network and connects you to its nearest location. Your messages only travel between your browser and that relay. They don't go to a game server or anywhere else. The test also measures ping and jitter first, over ordinary HTTP round trips, so you see all three together.

What "UDP blocked" means

Sometimes the test can't open the relay connection at all. Then it shows "UDP looks blocked" instead of a percentage. That isn't packet loss. It means something between you and the relay refused the connection:

  • a firewall on a work, school, hotel or public network;
  • a VPN that doesn't carry UDP or WebRTC traffic;
  • a browser setting or extension that turns off WebRTC to hide your IP address.

If you see it, try another browser or turn off the VPN for one run. If it still says blocked on your home network, check your router's firewall settings, since games and calls use UDP too. The ping and jitter results still stand either way.

How much loss is acceptable

Our verdict uses these limits. They're our thresholds, set out on how it works:

Use Acceptable loss What you notice above it
Competitive gaming 1% or less Shots and moves go missing; players jump around.
Video calls 2% or less Voices cut out; the picture freezes or blurs.
4K streaming 5% or less The picture drops in quality while the stream recovers.

A healthy wired connection should show 0% almost every time. Anything steadily above 1% is worth fixing, even if you don't play games: it usually means a fault somewhere, and faults tend to get worse. What packet loss is acceptable explains the bands in more detail.

One test can be bad luck

Loss often comes in bursts: a few seconds of trouble, then nothing for an hour. A single test can land in a burst and show 3% on a line that is usually fine, or miss a real problem completely. So:

  • Run it again. If the second and third runs show 0%, the first was probably a blip.
  • Run it during the problem. If your game lags every evening, test in the evening, while it's lagging. A test at noon proves little about 9 p.m.
  • Compare Wi-Fi with a cable. If loss disappears on a cable, the cause is your Wi-Fi (Wi-Fi vs Ethernet).
  • Test with nothing else running. A big download can fill the router's queue, and a full queue drops packets. The bufferbloat test shows whether that's happening.

Common causes

  • Weak or crowded Wi-Fi. The most common cause at home. Distance, walls and neighboring networks all drop packets.
  • A full router queue. When the line is busy, the router drops what doesn't fit. Smart queue settings fix this (fix bufferbloat).
  • Bad cables or connectors. A damaged Ethernet cable or a loose coax connector can drop packets on a wired connection.
  • Your provider's line or equipment. Loss that shows up on a cable, with nothing else running, at many times of day, is usually outside your home. Note the results and times and send them to your provider.

Our packet loss guide goes through the checks in order, from the cheapest fix to the call to your provider.

Sources