What packet loss is — and how it feels
Everything you do online travels as small packets of data. Packet loss is the share of those packets that never arrive: 1% means one packet in every hundred went missing.
What happens next depends on the app. Downloads, web pages and streaming run over TCP, which resends the missing packet, so loss shows up as slowdowns and stalls rather than missing data. Games and calls can’t wait for a resend — a late packet is as useless as a lost one — so that moment is simply gone.
- Gaming: rubber-banding, players teleporting, shots that don’t register, brief freezes followed by a jump forward.
- Calls: robotic or choppy audio, words dropping out, video that freezes or breaks into blocks.
- Streaming and browsing: buffering, drops in picture quality, pages that stall and then load all at once.
How this test measures packet loss
Press Start and, for about 15 seconds, the page downloads data from the nearest Cloudflare data center at a steady, deliberately modest pace over a few connections. The modest pace matters: a test that floods your line would cause the very congestion it is trying to detect.
When the download ends, the test reads the server’s own TCP counters for those connections — how many packets it sent and how many it had to retransmit — which Cloudflare reports in a Server-Timing response header. The server resends a packet when the packet or the acknowledgment confirming it goes missing, so retransmitted ÷ sent is a close proxy for packet loss on the path from the server to you. The page also reports idle latency and jitter.
| Packet loss | Grade | What it typically means |
|---|---|---|
| Under 0.1% | Excellent | Noise level — nothing to fix. |
| 0.1% to under 0.5% | Good | Fine for almost everything. |
| 0.5% to under 1% | Fair | Noticeable in fast-paced games and calls. |
| 1% to under 2.5% | Poor | Regular glitches in games and calls; downloads slow down. |
| 2.5% or more | Bad | Something is wrong and worth tracking down. |
Read the number with its limits in mind:
- Download direction only. The counters cover data flowing from the server to you, not your upload — your voice in a call, your inputs in a game.
- Wi-Fi hides some loss. Wi-Fi resends failed transmissions at the radio level before TCP sees a gap, so a struggling wireless link often shows up as jitter and latency spikes instead.
- Tiny values are noise. TCP occasionally retransmits a packet that wasn’t actually lost, so read results under 0.1% as zero.
- Intermittent problems need good timing. If the trouble comes and goes, re-run the test while it’s happening; a clean result at a quiet moment doesn’t rule it out.
What causes packet loss
Packets get dropped wherever a link is noisy, faulty or full. The usual suspects, starting closest to you:
- Wi-Fi: distance, walls, interference from neighboring networks, microwaves and Bluetooth, or a crowded channel.
- Home equipment: an overloaded or overheating router, outdated firmware or a failing network adapter.
- Cables and connectors: a kinked Ethernet cable, a loose or corroded coax connector, an old splitter, or a worn phone extension cord on DSL.
- Your ISP’s line: noise on a coax or DSL line — from damaged wiring, water in a connector or a fault in the street — that corrupts packets on the way.
- Congestion upstream: overloaded links inside your ISP’s network or between networks, typically worst in the evening.
- Full queues: when a router or modem buffer fills completely, new packets are dropped, so heavy downloads or uploads on your own network can cause loss as well as lag.
How to fix packet loss
Work through these steps in order and re-run the test after each one. Every step either fixes the problem or narrows down where it lives.
- Test on a cable. Connect a laptop or PC to the router with Ethernet and test again. If the loss disappears, the problem is your Wi-Fi: move closer, switch to 5 GHz or change channel. See why Wi-Fi keeps disconnecting for more fixes.
- Restart the modem and router. It clears an overloaded router and makes the modem reconnect to your ISP. Order matters — see how to restart your router and modem.
- Check every cable and connector. Swap in an Ethernet cable you know works, finger-tighten coax connectors, remove splitters you don’t need, and on DSL plug the modem straight into the main phone socket.
- Stop the bandwidth hogs. Pause big downloads, backups and streams, then test again. If loss appears only when the line is busy, your queues are overflowing: run the bufferbloat test and enable Smart Queue Management (SQM) if your router has it.
- Update firmware and drivers. Install router firmware updates and your computer’s latest network adapter driver; updates often fix stability bugs.
- Check your modem’s signal levels. Most cable and DSL modems have a status page with signal levels and error counts. Climbing uncorrectable errors (cable) or CRC errors (DSL) point to a line fault only your ISP can fix.
- Contact your ISP with evidence. Run the test several times — wired, at different times of day and while the problem is happening — noting the time and result of each. Repeated loss on a wired connection after the steps above is hard for support to dismiss.
Packet loss in games
Online games send small updates many times a second, usually over UDP, and never wait for a lost one to be resent. When updates go missing, the game predicts where everyone should be, then corrects itself when real data arrives — that correction is rubber-banding. In fast-paced games even loss below 1% can be noticeable; slower genres tolerate more.
Loss can also happen far from you. This test checks the path from a nearby Cloudflare data center to your device — your home network and your ISP. If it’s clean but a game still reports loss, look at the route to that particular server, the server itself, or your upload direction.
Many competitive games have a network statistics overlay, or “net graph”, that shows incoming and outgoing loss separately. Use it alongside this test and our ping test: loss plus high jitter often points to Wi-Fi, while loss on only one game’s servers points away from your home.
How this test differs from other packet loss tests
Most online packet loss tests send their own stream of small UDP packets — often over WebRTC, the technology behind browser video calls — and count how many arrive. That closely imitates game and call traffic, and some of these tests check both directions.
This test reads the real TCP counters of a real download instead, as reported by the server that sent it. Both approaches are valid. If they disagree, remember that each measures its own path to its own server, and that this one sees only the download direction.
Common questions
What is an acceptable amount of packet loss?
Ideally none. Under 0.1% is noise level and under 0.5% is fine for almost everything. From 0.5% to 1%, fast-paced games and calls start to show it, and sustained loss of 2.5% or more means something needs fixing.
Can Wi-Fi cause packet loss?
Yes, and it is one of the most common causes at home. Because Wi-Fi resends failed transmissions itself, much of that trouble appears as jitter and latency spikes rather than lost packets — so compare a wired test with a wireless one.
Is packet loss my problem or my ISP’s?
Restart your modem and router, then test on a cable. Loss that vanishes when wired is your Wi-Fi; loss that stays with good cables and connectors points to the line or your ISP; loss that shows up only on one game’s servers points to the route to those servers.
Why does my game lag when the test shows no packet loss?
Lag usually comes from high latency, jitter or bufferbloat rather than loss — or from loss in the upload direction or on the route to the game server, which this test can’t see. Run the bufferbloat test and check the game’s own network stats.
How do I check packet loss from the command line?
Ping a reliable host 100 times — ping -n 100 1.1.1.1 on Windows, or ping -c 100 1.1.1.1 on Mac and Linux — and read the loss percentage in the summary. Pinging your router’s address instead checks only your home network. Treat the odd lost ping with caution, because some routers give ping replies low priority.
Will a faster internet plan fix packet loss?
Rarely. Loss comes from interference, faulty cables, failing equipment and congestion, and a faster tier fixes none of those directly. If your line is constantly full, Smart Queue Management on your router often does more for games and calls than extra speed.