Ping, jitter and packet loss: what they are and where the game shows them

Ping: how long a packet travels

Ping is the time a packet takes to get from your PC to the game server and back. It is measured in milliseconds. The higher the ping, the later the server learns about your key press and the later you see what has already happened on the server: an opponent comes around the corner before they appear on your screen, and your shot lands where they no longer are.

Ping is made up of the distance to the server, the route the packets take and the queues at overloaded nodes along the way. Distance sets the floor: a signal cannot outrun light, and to a server on another continent ping will be high with any settings.

Keep in mind: the ping a game shows is an average over a short window. Two players with the same average ping can have completely different matches if one has a steady ping and the other's jumps around. That is why ping alone is not enough — you need two more numbers.

Jitter: how steady the ping is

Jitter is the spread of latency: packets arrive unevenly, sometimes earlier and sometimes later than expected. The game counts on a steady stream of updates from the server; when a packet is late, it either waits or extrapolates the movement itself, and when the packet finally arrives it snaps the picture into place. That is how you get stutter with a ping that looks normal.

In CS2 this number is shown separately: according to Valve's help page, the network problems line in the telemetry shows how often ticks are lost to packet loss or jitter, and the raw jitter and delivery graphs are turned on in the same place.¹

Games can hide jitter behind a buffer: in CS2 the setting that smooths packet loss and jitter adds latency, as Valve warns. It trades smoothness for responsiveness, and you should make that trade by the numbers, not by guesswork.¹

Where jitter comes from: Wi-Fi with interference, an overloaded ISP node in the evening, downloads on the same line, a route change in the middle of a match. Almost all of it can be checked at home in one evening — how exactly is in the guide on ping spikes.

Packet loss: what never arrived

Packet loss is data that never reached its destination. Game traffic usually goes without retransmission: there is no time to ask for a lost packet again, the next one arrives a moment later. So the game simply lives without the missing piece — models “teleport”, a hit is not counted, and with heavy loss the connection breaks.

Where to see it: in CS2 the network problems line shows two numbers with arrows — how often ticks are lost on the way out and on the way in; in Apex Legends the performance display shows frame rate, latency and packet loss; in Fortnite the net debug stats show ping and loss right in the match.^1,2,3

The causes of loss are the same as for jitter, plus faults: a damaged cable, an overheating router, an old Wi-Fi adapter. Loss on the ISP's path is rarer but more noticeable: it comes in bursts and coincides with stutter for everyone on your line.

Where to see it in the game

Counter-Strike 2

Settings → Game → Telemetry: for ping and network problems choose “always” or “in poor conditions”.¹

Dota 2

According to the wiki: Options → Advanced → Miscellaneous → Display Network Information — FPS, ping and loss appear in the corner.⁴

Deadlock

Settings → Game, the telemetry block: frame rate, ping and network problems, with a mode that shows them only when the connection is poor.⁵

Apex Legends

Settings → Gameplay → Performance Display: frames per second, latency and packet loss.²

Battlefield 6

Options → System → Network: Scoreboard Ping adds ping to the scoreboard, Network Graph turns on the network bar and graph.⁶

Fortnite

Settings → Game UI → “Net Debug Stats”: ping and loss appear in the match.³

Rocket League

When there is a problem, a “!” lights up next to the ping on the scoreboard: the game tells packet loss, latency spikes, high ping and server trouble apart.⁷

Detailed paths and menu screenshots are on the game pages: Counter-Strike 2 · Dota 2 · Deadlock · Apex Legends · Battlefield 6 · Fortnite · Rocket League

How to read the three numbers together

1. Ping is high but steady and there is no loss — the server is far away or the route is roundabout. Check the region in the game; if nothing closer is available, the route is what is left to work on.
2. Ping is normal but jumps — that is jitter. Most often Wi-Fi or downloads on the same line; less often an overloaded ISP node.
3. There is loss — look for a fault or interference: a cable instead of Wi-Fi, a router reboot, a check with the ping command to the router and beyond.
4. All three numbers are steady and the game still stutters — it is not the network. Look at the frame rate and the load on your PC.

Of these four cases SLARP works with the first and partly with the second: it routes the game's traffic through its own network, picks the route to the server and optimizes ping and jitter on that route. Distance, Wi-Fi, a faulty cable and the load on your PC it will not fix — and the game pages say so.