What users notice
Games hitch or rubber-band, voice becomes robotic, video calls freeze briefly and live streams stutter even though download speed may remain strong.
Unstable packet timing explained
What Is Jitter?
Jitter is the variation in packet response times. A connection can have an acceptable average ping but still feel inconsistent when individual packets arrive at uneven intervals.
Quick answer
Jitter Measures How Much Ping Changes Between Packets
Ping describes response time. Jitter describes the variation between successive response times. A flat 45 ms connection can feel more predictable than one that repeatedly jumps between 15 ms and 120 ms.
What the result means
A repeated high result shows packet timing is unstable. The next question is whether the variation begins on Wi-Fi, one device, the router, traffic load or the provider route.
Simple estimate = average change between consecutive ping samples
Visual explainer
Stable timing versus jitter
Average ping can look fine while timing still feels bad. The diagrams below show the difference between steady packet timing and uneven delivery.
Interactive evaluator
Latency Jitter Evaluator
Enter three consecutive ping readings. This lightweight estimate averages the change between samples and gives a practical stability rating; it is not a substitute for a longer packet-level test.
Result-led diagnosis
Match the Jitter Pattern to the First Useful Check
This matrix combines the symptom, most likely layer and next comparison so the page does not repeat separate Issue, Validation and Fix sections.
| What the Test Shows | Most Likely Layer | First Useful Check |
|---|---|---|
| Jitter is high on Wi-Fi but normal over Ethernet | Local wireless path. Interference, retries, weak signal, crowded airtime or mesh backhaul is making packet arrival times uneven. | Keep Ethernet as the control and follow the Wi-Fi coverage and shared-airtime diagnostic guide in the affected room. |
| Jitter remains high over Ethernet across several devices | Router, modem, access path or provider route. Wi-Fi and one-device causes have been removed. | Repeat the same wired test with household traffic paused, record the hub model and compare quiet and peak times. |
| Only one device has unstable timing in the same room | Client hardware or software. Adapter drivers, VPNs, security scanning, CPU load or power saving may be delaying that device. | Test a second device using the same connection and service before changing the router or broadband package. |
| Jitter rises mainly while uploads or downloads are active | Load-sensitive queueing or gateway strain. Traffic pressure is changing packet timing rather than causing a constant baseline fault. | Pause household transfers, compare loaded latency and read what bufferbloat is when queueing or gateway strain appears. |
| Only one game, call platform or server region is unstable | Destination or route. The wider connection may be healthy while one external path varies. | Compare another service and a nearer server region, then use the lag-spike diagnostic guide for route-specific patterns. |
| The same wired jitter returns at similar evening times | Shared provider capacity or external routing. The pattern changes by time of day rather than room or device. | Repeat identical wired tests on at least two days and retain the time, average ping, jitter, packet loss and router status. |
Measurement matrix
Jitter Ranges and Likely Real-World Impact
Use repeated results as practical indicators rather than treating three samples as proof. Real-time games and calls expose unstable timing before ordinary browsing does.
| Measured Jitter | Practical Rating | Likely Real-World Impact | First Useful Check |
|---|---|---|---|
| 0 to 2 ms | Excellent consistency | Packet timing is tightly grouped. Gaming, calls and browsing should feel predictable if packet loss and loaded latency are also healthy. | Keep this as the wired or near-router baseline and repeat when the problem occurs. |
| Over 2 to 7 ms | Generally stable | Most everyday use should remain smooth, though highly competitive games may reveal small timing variations under load. | Compare Wi-Fi with Ethernet and note whether upload or household load increases the result. |
| Over 7 to 20 ms | Degraded timing | Voice can become choppy, games may hitch and video calls can freeze briefly as packets arrive unevenly. | Determine whether the instability is Wi-Fi-only, device-specific, load-sensitive or present on wired tests. |
| Over 20 ms | Severe instability | Real-time use can become unpredictable, with robotic audio, rubber-banding, freezes and delayed interactions. | Collect repeated Ethernet evidence, check packet loss and loaded latency, then escalate persistent network-wide timing variation. |
Controlled comparison
Run the Six-Step Jitter Check
Keep the test method consistent and change one variable at a time so every comparison removes a possible cause.
- Record a quiet jitter baseline.
Run repeated ping measurements while the connection is quiet. Record average ping, jitter, packet loss, device and connection type.
- Compare Ethernet with Wi-Fi.
Repeat the same test over a direct cable. If jitter falls sharply, focus on coverage, interference, retries or mesh backhaul rather than the provider line.
- Cross-check another device.
If only one client is unstable in the same location, investigate its adapter, drivers, VPN, security software and processing load.
- Compare quiet and loaded conditions.
Start an upload or download separately. If jitter rises mainly under load, compare the loaded-latency result and background traffic.
- Repeat at quiet and peak times.
Use the same wired method during a quiet period and when the issue normally appears. Keep the server and test conditions consistent.
- Route the proven pattern to the correct next guide.
Use the result paths below rather than applying Wi-Fi, router and provider changes together.
Use the result
Choose the Next Step That Matches the Proven Timing Pattern
This guide stays focused on measuring and locating unstable packet timing. Detailed configuration and provider-specific actions remain in their specialist pages.
If only Wi-Fi has high jitter
Keep Ethernet as the clean control and follow the Wi-Fi coverage and shared-airtime diagnostic guide for placement, interference, channel and mesh checks.
If wired jitter rises under load
Pause background traffic and compare loaded latency. Use the loaded latency measurement guide to quantify the added delay.
If packet loss appears as well
Missing packets can create gaps and retransmissions that look like unstable timing. Use the packet loss explainer and classifier.
If only one service is affected
Compare another destination and server region. Use the lag-spike diagnostic guide for route and application-specific patterns.
If only one device is affected
Check adapter drivers, VPN routing, security scanning, power-saving and CPU load. A network-wide hardware change is unlikely to correct a single-client fault.
If peak-time wired jitter repeats
Keep matching results from at least two days, including time, jitter, average ping, packet loss, device and hub status before contacting the provider.
Detailed answers
Jitter FAQs
Use these answers to interpret the result, separate jitter from ping and packet loss, and decide when the evidence supports provider escalation.
What is a good jitter result?
Lower and repeatable is better. Around 0 to 2 ms is excellent, 3 to 7 ms is generally stable, 8 to 20 ms can affect real-time use, and repeated results above 20 ms indicate severe timing instability.
What is the difference between jitter and ping?
Ping is the response time of a packet or an average response time. Jitter measures how much that response time changes between packets.
Can Wi-Fi cause jitter?
Yes. Weak signal, retries, crowded airtime, interference and unstable mesh backhaul can make packet arrival times vary before traffic reaches the broadband line.
When should I contact my broadband provider about jitter?
Contact the provider when repeated jitter remains high over Ethernet, affects several devices and services, persists after household traffic is paused, or follows a repeatable time-of-day pattern.