What Is Jitter and Why Does It Wreck Your Calls?

The basics

Your internet connection has a speed number attached to it. Maybe 100 Mbps down, 20 up. That number tells you how much data can flow through the pipe, but it says almost nothing about how consistently that data arrives. Jitter is the measure of that consistency.

When you send VoIP packets across a network, each one takes its own path and arrives at its own pace. In a perfect world, if you send a packet every 20 milliseconds, they arrive every 20 milliseconds. In reality, one packet might take 30ms, the next 15ms, the next 45ms. The variation between those arrival times is jitter.

Why voice traffic hates jitter

Most internet traffic handles jitter just fine. When you load a web page, it does not matter if some packets arrive a few milliseconds late. The browser assembles everything and renders the page once it has all the pieces.

Voice is different. It plays back in real time. Your phone or softphone has a jitter buffer that collects incoming packets and reorders them before playing the audio. The buffer adds a small amount of delay (usually 20 to 60 milliseconds) to smooth things out.

When jitter stays within the buffer's window, you hear clean audio. When a packet arrives too late for the buffer to use it, it gets discarded. The effect is identical to packet loss: gaps, clicks, or robotic audio. High jitter effectively creates packet loss even when every packet technically arrives.

How to read jitter numbers

Jitter is reported in milliseconds. Here is a rough guide:

• Under 15ms: Excellent. No perceptible impact on call quality.
• 15 to 30ms: Acceptable. A well-tuned jitter buffer handles this without issue.
• 30 to 50ms: Degraded. You will start hearing artifacts, especially with smaller buffer sizes.
• Over 50ms: Poor. Expect frequent audio problems regardless of buffer configuration.

These thresholds assume a properly configured jitter buffer. A misconfigured buffer can make 20ms jitter sound terrible, while a generous buffer can paper over 40ms jitter at the cost of added latency.

Common causes

Network congestion is the usual suspect. When a router gets overloaded, it queues packets. Some wait longer than others, and that inconsistency is jitter. This is why call quality often degrades during business hours when everyone is on video calls and pulling files from the cloud.

Wi-Fi adds jitter by nature. The wireless medium is shared, and devices take turns transmitting. Interference from other access points, Bluetooth devices, or even microwaves introduces unpredictable delays. If you are running VoIP over Wi-Fi, expect higher baseline jitter than on a wired connection.

Long or complex routes contribute as well. If your packets are bouncing through a dozen hops across multiple ISP networks, each hop introduces a small amount of variability. International calls routed through multiple carriers tend to have higher jitter than local traffic.

Bufferbloat is an often-overlooked cause. Some routers and modems have oversized buffers that create large, variable queuing delays. The connection still shows low packet loss, but jitter spikes dramatically under load. The fix is usually enabling SQM (Smart Queue Management) or similar QoS on your router.

Jitter vs. latency

People sometimes confuse the two. Latency is how long it takes a packet to get from point A to point B. Jitter is how much that time varies from packet to packet.

You can have high latency with low jitter. A satellite link might have 600ms of latency, but if every packet takes almost exactly 600ms, the jitter is low. The call will have a noticeable delay, but the audio itself will be clear.

You can also have low latency with high jitter. A local network might average 5ms latency, but if packets bounce between 2ms and 40ms, the jitter is terrible and calls will sound broken.

For voice quality, consistent delivery matters more than fast delivery. A steady 80ms connection produces better calls than an erratic 20ms connection.

What you can do

Use wired connections for VoIP endpoints whenever possible. This is the single most impactful change for most setups.

Enable QoS on your router to prioritize voice traffic. DSCP marking (EF/46 for voice) tells network equipment to handle voice packets with priority. This helps most during congestion.

Check for bufferbloat using a DSLReports or Waveform speed test. If your bufferbloat grade is poor, enable SQM on your router. OpenWrt-based routers support this natively. Many consumer routers now include it as "QoS" or "traffic management."

Right-size your jitter buffer if your VoIP system exposes this setting. Too small and you lose packets unnecessarily. Too large and you add latency that makes conversation awkward. Most systems auto-tune this, but manual settings can help in consistently high-jitter environments.

Separate your traffic with VLANs if you manage your own network. Keeping voice traffic on a dedicated VLAN prevents bulk data transfers from creating jitter on your voice path.

The testing gap

Standard speed tests tell you bandwidth and average latency. They do not measure jitter in a way that reflects VoIP performance, because they use TCP (which retransmits lost data) rather than UDP (which mirrors real voice traffic). To actually know your jitter characteristics under realistic conditions, you need a test that simulates voice packet patterns, which is exactly what our VoIP quality test does.

For a deeper look at how jitter fits into the full voice path alongside latency and packet loss, see Latency, Jitter, and Packet Loss: The Details in our VoIP From the Ground Up series.