What Is Network Jitter and How to Fix It

Published April 23, 2026 · 8 min read

Your speed test says 500 Mbps. Your latency to the game server is 18ms. On paper, your connection is great. So why does your video call freeze every 30 seconds? Why does your character in the shooter rubber-band across the map? The answer is almost always jitter.

Jitter is the most under-discussed network metric for everyday users, even though it determines whether your real-time applications feel smooth or broken. This guide explains what jitter is, why it matters, how to measure it, and how to fix it on a typical home network.

What Jitter Actually Is

Jitter is the variation in latency between consecutive packets. Latency tells you how long one round trip takes. Jitter tells you how much the next one will differ.

Imagine sending ten ping packets to a server. Here are two scenarios:

• Low jitter: 22ms, 21ms, 23ms, 20ms, 22ms, 21ms, 24ms, 22ms, 20ms, 23ms. Average 21.8ms, very consistent.
• High jitter: 22ms, 80ms, 15ms, 150ms, 20ms, 60ms, 18ms, 200ms, 25ms, 90ms. Average 68ms but wildly inconsistent.

Both might "feel fast" on a speed test. The first scenario gives you a smooth video call. The second one freezes, audio cuts out, and your game character teleports.

Why Real-Time Apps Care About Jitter

Streaming video (Netflix, YouTube) handles jitter well because the player buffers several seconds of content ahead. A 200ms blip is invisible because the buffer absorbs it.

Real-time apps cannot buffer. A video call needs to play your voice the instant it arrives — if it waits, the conversation feels laggy and people start talking over each other. Online games update the world state 30–60 times per second. If packets arrive in bursts instead of evenly, the game cannot reconstruct what is happening and resorts to client-side prediction (rubber-banding).

The result: a connection with 20ms average latency and 80ms jitter feels worse than a connection with 50ms average latency and 5ms jitter. Consistency beats raw speed.

What Is Acceptable Jitter?

Rough thresholds:

• Under 5ms: Excellent. Competitive gaming-grade.
• 5–30ms: Good. Voice and video calls feel smooth.
• 30–50ms: Noticeable. Occasional audio glitches in calls, occasional rubber-banding in games.
• Over 50ms: Problematic. Calls drop, games are unplayable competitively.
• Over 100ms: Severe. Real-time apps essentially do not work.

How to Measure Jitter

Run a continuous ping to a stable target for 30–60 seconds. The standard deviation of the round-trip times is your jitter. PingKit shows this directly:

1. Open PingKit.
2. Go to Ping Test or MTR.
3. Target 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) for an internet jitter test, or your router's IP for a LAN jitter test.
4. Run for 60 seconds.
5. Read the jitter value from the summary.

Run the test under realistic conditions: while someone is streaming Netflix, while a backup is uploading, while the kids are gaming. Jitter often only shows up under load.

The Common Causes of Jitter

WiFi Interference and Signal Strength

The single most common cause. WiFi shares spectrum with neighbours, microwaves, baby monitors, and Bluetooth devices. When your client has to retransmit frames, latency spikes. Move closer to the router or switch to 5GHz / 6GHz to reduce this.

Bufferbloat

When your upload link saturates (someone is uploading photos to iCloud), packets queue up in your modem's buffer and latency spikes for everything else. This is called bufferbloat. Modern routers with Smart Queue Management (SQM, fq_codel, CAKE) eliminate it. Older ISP-provided modems often suffer badly.

WiFi Congestion

Too many devices on the same channel competing for airtime. Use a WiFi analyzer to find the least-used channel for your area, or switch to the 5/6 GHz band where channels are wider and less crowded.

ISP Path Issues

Your ISP's path to a particular destination might have a congested hop. Run an MTR to your gaming server or video conferencing endpoint and look for hops with consistently high jitter or packet loss. If the bad hop is inside your ISP's network, only they can fix it.

Old or Cheap Network Hardware

The free modem from your ISP may struggle under load. Older Ethernet cables (Cat 5) can cause errors that look like jitter. A WiFi router from 2015 cannot handle modern device counts.

Step-by-Step: Fix High Jitter

1. Measure baseline LAN jitter. Ping your router for 60 seconds.
2. Measure baseline WAN jitter. Ping 1.1.1.1 for 60 seconds.
3. If LAN jitter is high, switch to Ethernet. If LAN drops to under 1ms with low jitter, the problem is WiFi.
4. For WiFi: switch bands. 2.4GHz is crowded and slow. Use 5GHz or 6GHz where your device supports it.
5. For WiFi: change channel. Use a WiFi analyzer to find the least-used channel.
6. Test under load. Start a large upload while pinging. If jitter spikes, you have bufferbloat. Enable QoS / SQM in your router.
7. Run an MTR to the destination that is broken. Find the hop where jitter starts. If it is on your ISP's side, contact support with the MTR output.
8. Replace ageing hardware. If the ISP modem is more than 5 years old, request a new one. If your router is older than that, upgrade.

VoIP-Specific Tips

For voice calls, jitter buffers help — the call client adds a small artificial delay (usually 30–100ms) and reorders packets within that window. This trades a tiny bit of latency for smoother audio. Most clients adapt automatically. If your call provider has a "low latency mode" toggle, try both and see which feels better given your network conditions.

Gaming-Specific Tips

Gaming routers have a "Game Mode" or QoS preset that prioritises gaming traffic. These work by classifying small UDP packets to known game ports as high priority. They do not magically lower internet latency, but they do prevent your game from being starved when someone else on the network starts a download.

Disable WiFi Sleep / Power Save on your gaming device — the radio sleeping for 100ms shows up as a huge jitter spike. Plug in via Ethernet if you can. The wired path eliminates an entire class of problem.

Conclusion

Jitter is the metric that tells you whether real-time applications will feel smooth. Speed tests do not show it, so most people do not know they have it. Measure it under realistic load, separate LAN from WAN, and work down the list of causes from cheapest fix (channel change) to most expensive (new hardware).

PingKit makes it easy: run a Ping Test or MTR, read the jitter value, and start eliminating possibilities. Most home networks can hit single-digit jitter once the obvious problems are fixed.