‹ Back to Q&A 中文

Network Investigation

Latency vs Packet Loss vs Jitter: What's the Difference?

Latency is delay. Packet loss is missing data. Jitter is unstable delay.

Many gaming issues are simply called lag, but the network cause can be different. Understanding latency, packet loss and jitter helps identify where the problem starts.

Short answer

Latency, packet loss and jitter are three different network indicators.

Latency tells you how slow the response is. Packet loss tells you whether data failed to arrive. Jitter tells you whether the delay is stable. When a game feels bad, one ping number is not enough.

Latency: how long data takes to travel

Latency is usually measured in milliseconds. It describes how long it takes for your action to reach the server and for the server response to come back.

Higher latency makes the whole game respond more slowly. Skills, shots, movement and server confirmation may all feel delayed.

Packet loss: data that fails to arrive

Packet loss means some packets do not successfully reach their destination.

In games, packet loss can cause rubber-banding, teleporting, missing actions, short freezes or disconnects. Even if average ping looks fine, packet loss can make gameplay feel unstable.

Jitter: delay that keeps changing

Jitter is unstable latency.

If latency moves from 60ms to 200ms and back again, the game rhythm becomes uneven. Compared with a fixed delay, unstable timing is often harder to adapt to and can affect aim, movement and team fights.

How they usually feel in games

  • High latency: slow response, late feedback, delayed actions
  • Packet loss: rubber-banding, disconnects, missing skills, short freezes
  • Jitter: ping jumps, uneven response, sudden instability during fights
  • All three together: the game can feel extremely unstable and hard to diagnose by feeling alone

Why ping alone is not enough

Many games show a simple ping number, but that number does not always describe route quality fully.

For example, a game may show 80ms while packets are occasionally lost or delayed. The opposite can also happen: a stable 150ms connection may feel more playable than a route jumping between 80ms and 250ms.

What should you check first?

Start with the local network, then check the route direction.

Compare wired Ethernet and WiFi, check whether the network is shared, look for uploads or downloads in the background, and observe whether the problem appears only at peak hours, on one server, in one region or in one specific game.

Our observation

Online games do not only need low latency. They need a stable, continuous real-time path with minimal packet loss.

Latency, packet loss and jitter should be read together. Looking only at the lowest ping often hides the real instability that damages gameplay.

Search more network issues ›View gaming route guides ›