Jitter Buffer Late Packets

Understand jitter buffer late packets — packets that arrived after their playback deadline and were discarded by the buffer.

Jitter buffer late packets is a cumulative count of packets that arrived at the receiver after their scheduled playback time had already passed. These packets are useless for real-time playback — the buffer has already moved on — so they are discarded.

Think of it as arriving at a bus stop after the bus has already left. The bus (playback) does not wait for you, and you (the late packet) are simply dropped from the schedule.

How It Works

The jitter buffer assigns each incoming packet a playback deadline based on its sequence number and the current buffer delay. If a packet arrives before its deadline, it is queued for orderly playback. If it arrives after its deadline has passed, there is nothing the buffer can do with it — the moment it was needed has already gone by.

Late packets are discarded silently. In audio, each discarded packet creates a brief gap that may be filled by a concealment algorithm (generating synthetic audio to mask the gap). In video, a late packet may cause a partial frame loss or a visible artifact.

The late packet counter is cumulative over the lifetime of the media stream. It increases monotonically — it never decreases.

Direct quality impact

Every late packet represents an actual gap in the media stream. Unlike buffered packets that arrive with variable timing but still play correctly, late packets are permanently lost to playback. High late packet counts directly correlate with audible and visible quality degradation.

Why It Matters

Late packets reveal a fundamental mismatch between network behavior and buffer configuration. They mean the jitter buffer is not large enough to absorb the actual timing variations on the network. Each late packet is a moment where the user experienced degraded quality — a click in audio, a glitch in video.

In SIP load testing, late packet counts help you understand whether your buffer sizing is appropriate for the network conditions under test. A test that shows zero late packets with 2 endpoints but hundreds of late packets with 100 endpoints tells you that your infrastructure introduces significant jitter under load.

Thresholds

Level	Value (cumulative per stream)	Interpretation
Good	0 - 10	Minimal, buffer sizing is adequate
Warning	10 - 50	Buffer frequently too small for observed jitter
Critical	Above 50	Persistent timing issues, quality degraded

Common Causes

Cause	Explanation
Buffer too small	Fixed buffer size insufficient for actual jitter
Jitter spikes	Sudden timing variations exceeding buffer capacity
Network congestion	Queuing delays pushing packets past their deadline
Slow buffer adaptation	Adaptive algorithm not growing fast enough during jitter increases
Route changes	Network path changes causing sudden delay shifts

How to Fix It

Increase buffer capacity — If using a fixed jitter buffer, increase its size. If using an adaptive buffer, verify that the maximum allowed buffer size is sufficient for your network conditions.
Reduce network jitter — Address the root cause of packet timing variation. Apply QoS, use dedicated media networks, and minimize hop count.
Compare with current delay — If the buffer delay is already high and you still have late packets, the problem is severe jitter spikes that exceed even the buffer's maximum capacity.
Check for route instability — Sudden increases in late packets may correlate with network route changes. Use traceroute monitoring to identify path instability.
Correlate with jitter measurements — Compare late packet counts with the average jitter metric. Late packets typically appear when jitter exceeds the buffer delay.

Current Delay — The buffer size that determines the playback deadline
Packet Losses — Packets the buffer declared lost (never arrived), distinct from late packets (arrived too late)
Average Jitter — The timing variation that causes packets to be late
Packets Pushed — Successfully delivered packets, the inverse of late and lost