Knowledge base·4 min read·2026-10-08

Ping, Jitter and Packet Loss Explained: What’s Good and What’s Not

What do ping, jitter and packet loss mean, which values are good, acceptable or bad, and how do you fix problems? A clear guide with practical thresholds.

A speed test tells you more than just Mbps. Alongside download and upload, you’ll see three numbers that are often overlooked: ping, jitter and packet loss. These are exactly the values that decide whether a video call runs smoothly, whether you react in time in a game, and whether a web page opens instantly or hangs for a moment. This article explains what each term means, which values are good or bad, where problems come from and what you can do about them.

Ping (latency): your connection’s reaction time

Ping, also called latency, is the time a small data packet takes to travel from your device to a server and back again. It’s measured in milliseconds (ms). The lower, the more responsive your connection.

Ping depends on three things: the distance to the server (light in optical fibre travels roughly 200 kilometres per millisecond), the type of connection, and everything that happens along the way in routers and queues. From the Netherlands you can often reach a server in Amsterdam in a few milliseconds, whereas a server in the United States will never be below 70 to 80 ms, however good your connection is.

Ping thresholds

  • Below 20 ms: excellent. Ideal for competitive gaming.
  • 20–50 ms: good. Fine for almost everything, including most games and video calls.
  • 50–100 ms: acceptable. Noticeable in fast-paced games; calls usually still work well.
  • Above 100 ms: poor. Noticeable delay in conversations and games.

These values apply to nearby servers. If you measure to a server on the other side of the world, a higher ping is normal.

Jitter: how consistent is your ping?

Jitter is the variation in ping. Say you measure ten times and the results range between 10 and 12 ms: your jitter is low. If they jump between 10 and 80 ms, your jitter is high. For real-time applications such as video calls, internet telephony and gaming, jitter is often more disruptive than a slightly higher but steady ping. Apps absorb variation with a buffer, but that buffer adds delay of its own. When the variation gets too large, you hear robotic voices, the picture freezes or players “teleport” in your game.

Jitter thresholds

  • Below 5 ms: excellent.
  • 5–20 ms: fine for calls and most games.
  • 20–30 ms: borderline; you may notice occasional glitches.
  • Above 30 ms: problematic for real-time applications.

Packet loss: packets that never arrive

Packet loss is the percentage of data packets lost on the way. During downloads you barely notice, because lost packets are simply resent; it just costs some speed. Real-time traffic has no time for resending. There, packet loss means dropped words, blocky video or game actions that don’t register.

Packet loss thresholds

  • 0%: what you should see on a fixed connection.
  • Below 1%: acceptable, but not ideal.
  • 1–2.5%: noticeable in calls and games.
  • Above 2.5%: poor; something is structurally wrong.

Where do problems come from?

Wi-Fi

Wi-Fi is the most common cause of high jitter and packet loss. A weak signal, interference from neighbours on the same channel, too many devices or walls between device and router all lead to retransmissions and fluctuating delay. A wired connection is almost always more stable.

Bufferbloat

When your connection is full, for example because of a download, an update or a cloud backup, the queues in your router or modem can grow enormously. Your ping then rises from 10 to 200 ms or more, and jitter shoots up. This is called bufferbloat. PulseSpeed measures it by testing your ping while the connection is under load. Read more in what is bufferbloat.

Your line or provider

A faulty cable, an old modem, a local outage or congestion at your provider during peak hours can all cause packet loss and fluctuating ping. On DSL, interleaving sometimes plays a role: an error-correction technique that makes the line more stable but increases ping.

The route to the server

Sometimes the problem lies outside your own network and outside your provider, for example in overloaded links between networks or at the server itself. You can recognise this when only one service or game misbehaves while everything else works fine.

How to fix it

  1. Test wired. Connect a laptop with an Ethernet cable and run a speed test. If jitter and packet loss disappear, the problem is your Wi-Fi.
  2. Improve your Wi-Fi. Use 5 or 6 GHz, move the router, pick a quieter channel or add an access point closer to your device.
  3. Tackle bufferbloat. Enable Smart Queue Management (SQM, using fq_codel or CAKE) if your router supports it, or set QoS slightly below your real line speed, for example 85 to 95 per cent.
  4. Check cables and equipment. Replace old network cables, check your modem’s connection and restart modem and router.
  5. Pick a nearby server. Games and apps often let you choose a region. Closer means lower ping.
  6. Involve your provider. If packet loss or extreme jitter persists on a wired connection, collect measurements and contact your provider.

Short test versus longer measurement

A speed test lasts a few seconds. Problems that come and go, like a connection that hiccups every few minutes, are easy to miss. The stability test measures ping, jitter and packet loss for five minutes, so you can see whether there are spikes or brief drop-outs. For video calls, the video call test is useful; it simulates the traffic of a real call.

In short

  • Ping: below 20 ms excellent, below 50 ms good, above 100 ms poor.
  • Jitter: below 5 ms excellent, below 20 ms fine, above 30 ms problematic.
  • Packet loss: 0% is the norm; above 1% you’ll notice it.
  • Test wired to rule out Wi-Fi, and check bufferbloat.
  • Measure for longer with the stability test if problems come and go.

Measure it yourself

Speed test with bufferbloat, jitter and AI explanation. Free and ad-free.

Start the speed test →
← Back to knowledge base