Jitter and Packet Loss Explained

Guide · Updated July 2026

You pay for a fast plan, the speed test looks great — and yet your voice robotises on calls, teammates teleport around the map, and live streams hiccup. When speed is fine but the connection feels broken, the culprits are almost always jitter and packet loss: the two quality metrics most people have never checked.

Test your connection quality →Free · No signup · ~10 seconds

The postal service analogy

Think of your connection as a postal service delivering thousands of small letters (packets) per second:

Ping is how long one letter takes to arrive. (Lower = better.)
Jitter is how consistent delivery times are. A service that always takes 3 days is more useful than one that takes 1 day or 6 days at random — even though its average is worse.
Packet loss is letters that never arrive at all and must be re-sent — or, for live audio and games, are simply gone forever.

Video calls and online games are live conversations: they can't wait for re-delivery. That's why they suffer from jitter and loss far more than downloads do — a download just retries invisibly; a call glitches audibly.

What counts as good, tolerable and bad

Metric	Good / Tolerable / Bad
Ping	<20 / <50 / >100 ms
Jitter	<5 / <15 / >30 ms
Packet loss	0% / <1% / >2%

Even 2% packet loss — 1 letter in 50 — is enough to make a shooter feel rigged and a call drop syllables. These thresholds matter far more for real-time use than another 100 Mbps of download ever will.

How each one shows up

Symptom	Likely culprit
Robotic / underwater voice on calls	Jitter
Words cut out mid-sentence	Packet loss
Rubber-banding, teleporting players	Jitter + loss
Hits not registering in shooters	Packet loss
Everything delayed but smooth	High ping
Live streams buffer, downloads fine	Jitter

What causes them

Wi-Fi. The number one cause at home. Radio interference and retransmissions create exactly the random delays that define jitter. Wired connections have almost none — see Wi-Fi vs Ethernet.
A saturated connection (bufferbloat). When someone maxes out the line — a big upload, cloud backup, 4K streams — the router queues packets, and everyone's latency spikes wildly. This is why games lag "whenever someone uses the internet."
An overloaded router. Cheap or ancient routers buckle under many devices, adding delay variance even when bandwidth is free.
Provider or route problems. Congestion at peak hours, a fault in the line (especially after storms, for cable/DSL), or a bad route to one specific game server.

How to fix them, in order

Go wired for the device that matters. This alone eliminates Wi-Fi jitter, the most common cause. If a cable is impossible, move closer to the router and use 5 GHz (placement tips).
Find the bandwidth hog. If lag coincides with someone's backup or stream, enable QoS/"Smart Queue Management" on the router — it prevents any one device from flooding the queue. SQM (fq_codel/CAKE) specifically targets bufferbloat and is transformative on busy home lines.
Reboot and update the router. Months of uptime and old firmware both correlate with degraded quality.
Test at different times. Loss only at 20:00–23:00 points to provider congestion; loss at 3 AM too points to a line fault.
Collect evidence, then call the provider. A week of timestamped tests showing consistent loss on a wired connection is very hard for support to wave away. Line faults (corroded connectors, water in cabinets) are real and fixable — but usually only after you prove it isn't your Wi-Fi.

Measure before and after

Run a speed test and note the ping. Then change one thing — plug in the cable, enable QoS, move the router — and run it again. Fixing connection quality is invisible in the download number, but you'll feel it immediately in every call and every match.