Tutorial

Latency, Jitter & Packet Loss Explained

Network quality comes down to three numbers: latency (how long a packet takes), jitter (how much that delay varies), and packet loss (how many packets never arrive). Bandwidth tells you the pipe's width; these three tell you whether it actually works well.

Latency — the delay

Latency is the round-trip time for a packet, measured in milliseconds by ping. It is set mostly by distance and the number of hops — physics, not bandwidth. Healthy guide values: same-city <20ms, same-country <50ms, intercontinental 100–300ms. High latency ruins video calls and gaming even on a fast connection (this is why latency ≠ bandwidth).

Jitter — the variation

Jitter is the variation in latency between packets. Steady 60ms is fine; bouncing 20ms–200ms is jitter, and it's what makes VoIP robotic and video freeze. It comes from congestion, overloaded Wi-Fi and inconsistent queuing. Healthy VoIP jitter is under ~30ms. Jitter is why a connection can 'speed-test fine' yet sound terrible on calls.

Packet loss — the missing packets

Packet loss is the percentage of packets that never arrive. TCP recovers by retransmitting (so you see slowness); UDP doesn't (so you see glitches in calls and streams). Even 1–2% loss is very noticeable. Causes: congestion, bad cables/Wi-Fi, a duplex mismatch, or a failing device — trace it with the interface error counters in the slow-network guide.

How to measure all three

ping -n 100 8.8.8.8      # Windows: min/avg/max = latency; loss % at end
ping -c 100 8.8.8.8      # Linux/Mac equivalent
mtr google.com          # live per-hop latency + loss (Linux/Mac)

Read them together: high latency but zero loss = distance (normal); low latency with rising loss = a fault to hunt; steady latency with high jitter = congestion or Wi-Fi. This triage is the heart of network troubleshooting.

Frequently asked questions

What is the difference between latency and jitter?

Latency is the delay of a packet (round-trip time in ms). Jitter is how much that delay varies between packets. Low average latency with high jitter still ruins real-time apps like VoIP.

What is an acceptable amount of packet loss?

Ideally zero. Under 1% is often tolerable for web browsing, but even 1–2% badly degrades voice and video calls, which cannot retransmit lost packets in time.

Does more bandwidth reduce latency?

No. Bandwidth is the pipe's capacity; latency is travel time set by distance and hops. A faster connection does not make packets arrive sooner — it lets more arrive at once.

How do I measure latency, jitter and packet loss?

Ping with a large count shows min/avg/max latency (the spread indicates jitter) and the loss percentage. Tools like mtr or PathPing show per-hop latency and loss to locate where the problem starts.

VS
Vipul Sir — Lead Instructor, Attila Technologies20+ years in Cisco networking. Teaching CCNA, CCNP, CCIE & CyberOps in Ahmedabad since 2004.

Want hands-on training?

Learn this on real Cisco lab devices with placement support at Attila Technologies, Ahmedabad.

Start your networking career with Attila Technologies

Hands-on Cisco training, real lab devices and placement support in Ahmedabad.