Jitter

Jitter is the variation in packet arrival time, measured in milliseconds. If your ping alternates between 5 ms and 80 ms, your jitter is 75 ms. High jitter causes choppy video calls, voice distortion on VoIP, and inconsistent frame rates in gaming even when average ping looks acceptable.

Jitter vs latency

Latency is the average time for a packet to travel from source to destination. Jitter measures how much that time varies from packet to packet. A connection with 40 ms average latency and 2 ms jitter is very consistent — every packet arrives within a 2 ms window of the expected time. A connection with 20 ms average latency and 35 ms jitter is erratic — packets arrive anywhere from near-instant to 55 ms late. For real-time applications, consistency matters more than the average. A game engine or VoIP codec that expects a packet every 20 ms cannot cope when packets arrive unpredictably.

What causes jitter

Several mechanisms produce variable queuing delay that manifests as jitter:

• Network congestion — when a link or buffer becomes congested, packets queue and wait. As congestion fluctuates, so does wait time, producing variable arrival intervals.
• Bufferbloat — oversized router buffers fill with bulk data (downloads, uploads), and real-time packets get stuck behind them. Arrival times become highly variable depending on how full the buffer is at any moment.
• Wi-Fi retransmissions — Wi-Fi uses acknowledgement and retransmission for every frame. When a frame is lost due to interference and retransmitted, the effective delay for that packet doubles or triples, creating a spike in the jitter trace.
• Packet reordering — on paths where packets take different routes (common in some ECMP and mobile networks), packets arrive out of order. The receiver waits for the missing packet before handing data to the application, introducing variable delay.
• ISP infrastructure — shared cable plant, DSLAM contention, and fixed-wireless links where signal quality varies second to second all contribute to variable transit times.

How jitter affects real-time applications

VoIP and WebRTC applications encode audio in 20 ms frames. Each frame must arrive before the playout deadline or the audio gaps — producing the choppy, robotic quality of a bad call. Video calls add video frames on top: high jitter causes frames to arrive late, forcing the codec to repeat or skip frames, which appears as pixelation, freezing, or stuttering. In gaming, the server processes player inputs at fixed tick rates (typically 64 or 128 Hz). If your packets arrive irregularly, the server sees delayed or bunched-up inputs, producing rubber-banding (the character snapping back to an earlier position) and missed hit registrations.

Jitter buffers

VoIP and WebRTC applications use an adaptive jitter buffer to smooth out arrival irregularities. Incoming audio packets are held briefly in a small buffer before being played out, so that even if packets arrive slightly late they are already in the buffer when needed. The buffer depth adapts dynamically: when jitter increases, the buffer grows to absorb spikes; when the connection stabilises, the buffer shrinks to reduce the added latency. The trade-off is fixed: a deeper jitter buffer tolerates higher jitter but adds more end-to-end delay. Most implementations target a buffer depth that adds no more than 50–150 ms while absorbing typical jitter spikes.

Acceptable jitter thresholds

How to measure jitter

A speed test that reports jitter sends multiple packets and calculates the standard deviation or mean deviation of round-trip times. ping -n 100 (Windows) or ping -c 100 (Linux/macOS) to a stable target shows the spread between minimum and maximum RTT — a rough proxy for jitter. iperf3 -u -b 1M (UDP mode) reports jitter directly as part of its output. For VoIP quality specifically, MOS (Mean Opinion Score) calculators convert latency, jitter, and packet loss into a single 1–5 quality score using the ITU E-model. The most revealing test is a loaded jitter test — measuring jitter while the connection is simultaneously saturated with download or upload traffic, which exposes bufferbloat-induced jitter that idle tests miss entirely.

Frequently Asked Questions

Why does my ping look fine but my calls are choppy?

Average ping hides jitter. A connection averaging 20 ms ping but spiking to 150 ms every few seconds will sound choppy on a call even though the average looks healthy. Run a jitter test specifically, not just a ping test.

Is jitter or latency worse for gaming?

Both matter, but jitter is often the bigger problem. A consistent 40 ms ping is playable; a connection that bounces between 10 ms and 100 ms every second is not — because the game engine cannot compensate for unpredictable timing.

Does fiber have lower jitter than cable?

Yes. Fiber delivers dedicated, symmetric paths — jitter is typically under 1 ms. Cable networks share capacity across neighbours, and congestion causes packet queuing that inflates jitter, especially in the evening.