Discover how Edgegap works

Discover how Edgegap works

Jitter

Jitter is variation in latency between packets rather than latency itself. A connection averaging 40 ms but swinging between 20 and 90 often plays worse than a steady 70, because prediction and interpolation struggle to settle on a moving target. Consistency often matters as much as the average.

Also called

network jitter, server jitter, packet delay variation

By

By

By

Philip Coté

Philip Coté

Philip Coté

,

CTO

CTO

CTO

Published

Published

Published

What Is Jitter in a Game, and What Is Server Jitter?

Jitter is about timing, not speed, and the word is used in a few ways:

  • Network jitter is how much the travel time changes from one packet to the next. Real-time protocols such as RTP measure it as interarrival jitter, a running estimate that moves one sixteenth of the way toward each new difference, so a single spike moves it only slightly (RFC 3550). Many speed tests report the average difference between consecutive pings.

  • Server jitter can mean two things. In a narrower sense, it is a server whose updates leave unevenly because its ticks don’t run on schedule. In everyday use, it is what players call the network jitter they see while connected to a server, as in searches about Counter-Strike 2, Deadlock or Palworld servers.

  • Clock jitter in time servers (NTP) and camera or graphics jitter are related ideas in other fields, not what a multiplayer readout shows.

For a multiplayer developer, network and server timing end up in the same place: whether updates arrive on the rhythm the game was built for.

Article's key insights

  • Latency has a floor, and everything else stacks on top of it: The physical travel time between two machines is the minimum delay any online game can have. Routing, tick rate, update rate and processing all add to it. Netcode cannot remove that delay. It can only decide where players feel it.

  • The shortest path is rarely the fastest: A direct peer-to-peer connection looks like the shortest route between two players, but packets still cross both players' ISPs and whatever routes those networks choose. A well-placed server between them is often both faster and fairer.

  • Lag compensation moves the cost, it doesn't erase it: Lag compensation rewinds the server so a high-ping player's shot counts, which means the target can be hit after reaching cover. The only real fix is keeping ping gaps small, which makes it a matchmaking and server placement problem as much as a netcode one.

  • Tick rate is a time budget: A server's tick rate sets how many milliseconds it has to simulate each step of the game. Higher rates cut delay and sharpen hit registration, but cost more CPU and bandwidth. A server that overruns its budget stutters for everyone in the match.

  • Two separate choices, not one: Where the game runs (peer-to-peer, relay or dedicated server) and how state is shared (lockstep, rollback or state replication) are independent decisions. Any sync model can run on any hosting model.

How Does Jitter Change What Players See?

Many games send updates on a regular schedule, often tied to the tick rate. Two connections with the same average latency can deliver that rhythm very differently: one steady, one where some updates arrive early and others late. An update that arrives after the moment the game needed it leaves the same gap as a lost one until it lands. Counter-Strike 2’s network readout now “measures how often a tick is missed due to network loss or jitter” (Valve patch notes, 12 November 2024).

Lateness hurts in both directions:

  • Server to client: The client draws other players from a short buffer of recent updates. When the next one is late, the buffer runs dry: the client holds the last position or guesses forward, then snaps or smooths to the correct position when the update lands.

  • Client to server: In fixed-tick netcodes, a late input means the server has nothing for that tick. Many servers reuse the last input, and the player’s own client-side prediction is corrected afterwards, which players often feel as rubberbanding.

Updates that never arrive are covered under packet loss. Jitter is the same problem arriving late.

How Big Should a Jitter Buffer Be?

A buffer turns uneven arrivals into an even rhythm, and every millisecond of buffer is a millisecond of delay. A bigger buffer absorbs more jitter and makes everything a little later. A smaller one keeps the game responsive and stutters more often.

Unity’s Netcode for Entities shows how one netcode sizes it (Unity docs):

  • Other players: an interpolation buffer with a 2-tick base by default, plus an allowance for jitter scaled by 1.25, a multiplier “used to compensate received snapshot rate jitter”.

  • The player’s own inputs: the client tries to stay 2 ticks ahead of the server by default. Higher values “increase command arrival reliability, at the cost of a longer client prediction window”.

Its interpolation delay is “calculated by taking into account round trip time, jitter and packet arrival rate” and adjusts gradually (Unity docs), so a jittery connection gets more buffer than a steady one. Interpolation covers what that delay costs. The useful sizing question is how much jitter most of your players have, measured per region, and how often the worst of it still gets through.

Where Does Jitter Come From, and What Can a Server Host Control?

Much of the jitter players see starts outside the game server:

  • The player’s home network: Wi-Fi and busy connections can add jitter. The FCC found that latency under a download “generally is significantly higher than idle latency” (FCC, 2023), so load that comes and goes makes latency swing.

  • The route: Congestion on links along the way, and routes that change mid-match, make travel time uneven.

Two sources sit with whoever hosts the server:

  • Server timing: A server whose ticks overrun, or that runs short of CPU at peak, sends updates late for every player at once. Sizing each server for its peak with headroom makes late ticks much rarer.

  • The length of the path: A server near its players sends traffic across fewer networks, which leaves fewer places for delays to build up.

On Edgegap, the vCPU and memory allocated to a game server are reserved for it, by design, and are not used by other studios or other servers (Edgegap docs). On Pay as You Go, container metrics at one-second intervals help spot CPU spikes. Each match’s server can be placed at the best available location for its players at request time.

A word from our sponsor (ourselves!)

Most lag comes from distance, not from code. Edgegap's Edge Cloud is a distributed network with up to 615+ locations available on demand, so each match runs at the best available location for its players. Independent replays of live studio traffic measured a 58% drop in average round-trip time compared with public cloud.

Edgegap's Take (just our opinion, take it with a grain of salt!)

Keep Your Server’s Ticks Steady and Its Path Short, Then Size the Buffer for the Rest

Players often read jitter as “server jitter”, even when it starts on their own Wi-Fi. The fix that matters most is often outside the game, but the blame lands on it, so the parts you do control are worth getting right.

Start with the server: confirm its ticks leave on time at peak, with CPU headroom to spare. Then the path: place each match’s server near its players. Then the buffer: size it for the jitter your players actually have.

A useful check, per region: the share of ticks where clients miss an update, alongside the server’s tick time for the same matches. Valve’s network graph has long split it the same way, showing the server’s frame rate and the variation in its frame time next to packet loss (Valve). When both rise together, look at the server, for example with Edgegap’s CPU and networking insights. When only the first rises, look at the path, starting where packets leave the server.

Philip Coté, CTO

-

-

-

Philip Coté

Philip Coté

Philip Coté

,

CTO

CTO

CTO

Frequently Asked Questions

Are jitter and ping the same?

Is 25 jitter good?

How do you test ping and jitter?

Is jitter caused by the server or by my connection?

Get your Game Online Easily & in Minutes

Start Integrating Now!

Get your Game Online Easily
& in Minutes