What ping, jitter and packet loss actually mean

There is no single good ping, because it depends entirely on what you are doing. Under 30 ms is excellent for anything. Between 30 and 80 ms is comfortable for calls and most games. From 80 to 150 ms it is noticeable in fast games and invisible while browsing, and past 150 ms a conversation starts to feel like a satellite link. Jitter and packet loss matter as much, and for live audio and video they matter more.

Ping is a distance, not a speed

Ping measures the round trip: a small packet goes out, comes back, and the stopwatch reads in milliseconds. It says nothing about how much data you can move.

This is the confusion worth clearing first. Speed is how wide the pipe is. Ping is how long it is. A satellite connection can move a large file at a perfectly good rate and still be hopeless for a call, because every syllable takes half a second to arrive. A slow connection with a short path feels snappier than a fast one with a long path, for everything interactive.

None of this needs a specialist tool to observe: any ping app that prints one line per packet, rather than a single averaged figure, shows all three numbers at once.

Physics sets a floor. Light travels through fibre at roughly two thirds of its speed in a vacuum, about 200 km per millisecond, and a round trip covers the distance twice — so a server 3,000 km away costs about 30 ms before any equipment is involved, and every switch and router along the way adds to it. A number close to that floor is not something to optimise; it is the answer.

Round trip	Browsing	Video call	Fast-paced game
Under 30 ms	Instant	Perfect	Competitive
30–80 ms	Instant	Fine	Fine
80–150 ms	Fine	Slight talk-over	Noticeable
150–300 ms	Slightly sluggish	Awkward turns	Frustrating
Over 300 ms	Sluggish	Hard to converse	Unplayable

Jitter is the one that ruins calls

Jitter is the variation between consecutive pings. A connection reporting 20, 21, 20, 22, 20 ms and one reporting 5, 90, 8, 140, 12 ms can average out similarly and behave completely differently.

The reason is that live audio and video have to play at a steady rate. The receiving end holds a small buffer to absorb variation; when a packet arrives later than the buffer can wait, it is simply dropped. That is the robotic quarter-second of silence in a call on a connection whose average ping looks fine.

Under 5 ms of jitter is good. Under 20 ms is usable. Consistently over 30 ms will be audible, and it is why “my internet is fast but calls are terrible” is a coherent complaint rather than a contradiction.

Packet loss compounds

Packet loss is the percentage that never came back, and it is worse than it sounds. A lost packet is usually resent, so 2% loss costs you a good deal more than 2% of your experience.

• On your own network: none is acceptable. A ping to your own router that drops anything is a Wi-Fi fault, not a fluctuation. That test is the first step in is it my Wi-Fi or the internet.
• Across the internet: under 1% is normal and invisible.
• 1–3% is audible on calls and noticeable in games.
• Over 5% breaks live traffic outright and slows downloads badly, because a file transfer interprets loss as congestion and deliberately backs off.

Read three results

Measuring it so the number means something

Four habits, none of them difficult:

• Twenty packets, not four. A four-packet test cannot show you jitter or a believable loss figure. One in twenty is 5%; one in four is noise.
• Ping a number and a name, separately. 1.1.1.1 tests reachability; example.com also tests name lookup. When one works and the other does not, you have found the fault without trying.
• Compare against your own router. A number to the internet means little on its own. The same test to your router separates your Wi-Fi from everything beyond it.
• Test on the device that has the problem, on the connection it has. A laptop on Ethernet cannot tell you why a phone on Wi-Fi is dropping calls.

What to use

Any ping tool does the basics, and what you want beyond that is per-packet detail rather than a single averaged number — because the average is the one figure that hides jitter and loss.

Ping Network Tool prints Linux-faithful output, one line per packet with its sequence number, TTL and round-trip time, plots a live graph where a gap is a lost packet, and gives you the sent/received/lost and min/max/average summary at the end. Its traceroute shows the round trip to every hop along the path, which is how you find the one adding the delay rather than guessing. It has no ads; a one-time upgrade adds TCP ping for hosts that block ICMP, and there is no subscription.

If the question you actually have is “why is nothing loading”, start with is it my Wi-Fi or the internet instead — it is the diagnostic order, and these numbers are what it reads. The rest of our utilities are on the Tools page, including AI Wallet Pass, and the reasoning behind selling any of them once rather than monthly is in what a puzzle game subscription costs.