Jitter
Also known as: network jitter, packet delay variation, PDV, jitter buffer, RTCP
Jitter is the inconsistency in how long packets take to travel across a network.
In a video call, if packets sometimes take 20ms and sometimes take 80ms, the audio and video become choppy. Low jitter is essential for real-time applications; a jitter buffer compensates by holding packets briefly to smooth out delivery.
Jitter, explained at three levels
At home
Jitter is what makes video calls choppy. In a steady connection, audio packets arrive evenly every 20ms. With jitter, some packets arrive after 10ms, others after 50ms. The uneven timing causes audio gaps and robotic voice effects. More jitter = worse call quality.
At work
Jitter is a key metric for evaluating network quality for businesses using VoIP, video conferencing, or real-time collaboration tools. A connection with high bandwidth but high jitter will sound worse than a slower connection with consistent delivery times.
At home
Jitter is measured in milliseconds (ms) as the variation in packet delay. Acceptable thresholds: <30ms jitter for VoIP (per ITU G.114), <50ms for video conferencing. A jitter buffer at the receiver holds incoming packets briefly and releases them at a steady rate, smoothing out timing variations. Larger buffers absorb more jitter but add latency (and audio delay).
At work
Network causes of jitter: variable queue depths at routers during congestion (packets wait longer when a link is busy), different paths taken by different packets (some paths have more hops), and CPU interrupts in software-based routing. QoS solutions: DSCP priority queuing for voice traffic (ensuring voice packets are always sent before bulk transfers), traffic shaping, and dedicated MPLS or SD-WAN circuits with latency SLAs.
At home
Jitter is calculated from RTCP (Real-Time Control Protocol) reports as the mean deviation of successive packet inter-arrival times. The RTP timestamp in each packet allows the receiver to reconstruct timing independent of network jitter. Adaptive jitter buffers dynamically adjust buffer depth based on measured jitter -- a voice endpoint might buffer 60ms during a congested period and shrink to 20ms when the network smooths out.
At work
In Cisco and enterprise QoS frameworks, voice traffic is marked DSCP EF (Expedited Forwarding, DSCP 46) and placed in a priority queue (LLQ -- Low Latency Queuing) that is served before all other queues. This eliminates jitter caused by queue depth variation. DSCP CS3 or AF41 marks interactive video. Application-level FEC (Forward Error Correction, as used in Zoom's audio codec) corrects minor packet loss without retransmission, reducing perceived jitter effects.
Real-world examples
At home
Fatima noticed her video calls were choppy even though her internet speed test showed 200 Mbps. She ran a Speedtest that measured jitter separately -- it was 85ms, well above the 30ms threshold for voice. Her ISP's node was congested, causing uneven packet delivery.
At work
Marcus's IT team investigated poor video conferencing quality. Network monitoring showed average latency of 25ms (acceptable) but jitter of 45ms (too high). They implemented DSCP marking and LLQ for Zoom traffic at the office router -- jitter dropped to 8ms and call quality improved immediately.
Common confusions
- High bandwidth means low jitter — Bandwidth (speed) and jitter (consistency) are independent metrics. A 1 Gbps connection can have high jitter if routers are congested or packet paths vary. A 50 Mbps connection on a well-managed network can have very low jitter. Real-time apps care more about consistent timing than raw speed.
- Jitter only affects voice calls — Jitter affects any real-time application: video streaming (causes buffering), online gaming (causes lag spikes), industrial control systems, and financial trading platforms. High jitter in gaming is the 'rubber banding' effect where your character jumps positions on screen.
For analysts
Jitter metrics are essential in network SLA evaluation for unified communications procurement. BAs should ensure that jitter thresholds (typically <30ms) appear alongside latency and packet loss in network service agreements, not just bandwidth numbers.
History & origin
Jitter became a recognized issue as VoIP (Voice over IP) networks emerged in the 1990s and 2000s. Traditional telephone networks used circuit switching with constant timing -- jitter didn't exist. Packet switching introduces inherent timing variation due to variable queue depths in routers. RTP (Real-Time Protocol, RFC 3550) was developed to carry audio/video over IP with timestamps that allow receivers to detect and compensate for jitter. QoS mechanisms were developed to minimize jitter for real-time traffic.