# What ping, jitter and packet loss actually mean

> A good ping depends entirely on what you are doing. Here is what each number measures, what counts as fine, and which one ruins a video call.

Source: https://apps.swtlm.com/blog/what-ping-jitter-and-packet-loss-mean · TLM Apps — focused mobile apps from a team of engineers.
Published: 2026-07-21 · Updated: 2026-07-21 · TLM Software Design

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](https://apps.swtlm.com/ping-network-tool) 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](https://apps.swtlm.com/blog/is-it-my-wifi-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.

File transfers use TCP, which treats a lost packet as a sign the network is
congested and reduces its sending rate on purpose. A link with steady low loss
therefore spends its life throttling itself. It is not the missing 3% that
costs you the speed; it is the response to it.

## 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](https://apps.swtlm.com/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](https://apps.swtlm.com/blog/is-it-my-wifi-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](https://apps.swtlm.com/tools), including
[AI Wallet Pass](https://apps.swtlm.com/ai-wallet-pass), and the reasoning behind selling any of them
once rather than monthly is in
[what a puzzle game subscription costs](https://apps.swtlm.com/blog/what-a-puzzle-game-subscription-costs).

## Frequently asked questions

**What is a good ping?**

Under 30 ms is excellent for anything, 30 to 80 ms is fine for calls and most games, 80 to 150 ms is noticeable in fast games and invisible while browsing, and above 150 ms makes conversation awkward. Downloads barely care at any of these.

**What is jitter and why does it matter more than ping?**

Jitter is how much the ping varies between packets. Live audio and video have to play at a steady rate, so a connection swinging between 20 ms and 200 ms sounds broken even though its average looks healthy.

**How much packet loss is acceptable?**

On your own network, none. Across the internet, under 1% is normal and usually invisible; 1 to 3% starts to be audible on calls; above 5% breaks most live traffic and slows downloads badly, because every lost packet is resent.

**Does a fast download speed mean a good ping?**

No. Speed is how much fits through the pipe and ping is how long the pipe is. A satellite link can move a large file quickly and still be unusable for a call.

**Why is my ping to a game server so much worse than to a speed test?**

Distance and routing. A speed test picks a nearby server on purpose, while a game server may be on another continent — and light in fibre covers about 200 km per millisecond, which a round trip pays twice before any equipment is involved.