Online Play, Lag & Connection Terms

By Treesz · Updated Oct 12, 2026

When an online match feels wrong, players reach for the same handful of words: lag, ping, desync, rubber banding, "the servers are 20 tick". They are often used as if they meant the same thing, but they describe different problems with different causes, and only some of them are something you can fix at home.

This glossary explains the connection terms you will meet in patch notes, settings menus and voice chat. Each entry says what the term means, how it shows up on your screen and what, if anything, you can do about it. The quick table comes first; the full explanations follow in the order you would normally troubleshoot a bad connection.

Term	What you notice	Usually caused by	Can you fix it yourself?
High ping	Everything reacts a fraction late; you die "behind cover"	Distance to the server, routing, a busy network at home	Partly: wired connection, right server region
Jitter	Fine one second, sluggish the next	Wi-Fi interference, congested home or ISP network	Often: switch to cable, stop background uploads
Packet loss	Enemies teleport, shots don't register, you snap back	Bad Wi-Fi, faulty cable or router, ISP or server problems	Sometimes: test wired, restart router, report trace to ISP
Rubber banding	You run forward, then get pulled back	Packet loss or a server that is overloaded	Only the home-network part
Desync	What you see doesn't match what the server decided	Latency plus the game's netcode	Rarely
Low tick rate	Hits feel "late" even with good ping	Server design choice	No
Strict / Type 3 NAT	Can't join friends, voice chat fails, long matchmaking	Router settings	Yes: UPnP or port forwarding

Ping and latency

Ping is the time it takes for a small message to travel from your device to the game server and back, measured in milliseconds (ms). Strictly speaking that round trip is called latency or RTT (round-trip time) and "ping" is the tool that measures it, but in games the two words are interchangeable.

Most of your ping is set by physical distance and by the route your internet provider sends traffic along. Playing on a server on another continent will always add tens of milliseconds, however good your connection is. That is why choosing the right server region matters more than any setting.

How much ping is "too much" depends on the genre. Turn-based and most MMO content is comfortable well above 100 ms. Fast shooters are a different story: Riot Games has said it aimed for most VALORANT players to be under 35 ms, and it built its own network backbone (Riot Direct) partly to get there. In practice:

Under ~50 ms — feels immediate in almost any game.
50–100 ms — fine for most games; in duels you start to notice that the other player reacts "first".
Over ~100–150 ms — clearly delayed; abilities and shots land late, and you lose close fights you should win.

Note that the number shown in-game is not always comparable between titles: some show the full round trip, others include processing time on the server. Compare your ping within one game, not across games.

Jitter

Jitter is how much your ping varies from moment to moment. A steady 60 ms is often more pleasant than a ping that jumps between 25 and 90 ms, because the game's smoothing (see netcode) is tuned for a predictable delay.

Jitter is mostly a home-network problem: Wi-Fi interference from neighbours, a microwave on the same 2.4 GHz band, several people streaming video, or a console downloading an update in the background. Moving to an Ethernet cable or to the 5 GHz band is the single most effective fix.

Packet loss

Games send your inputs and receive the world state in small chunks of data called packets. Packet loss means some of those packets never arrive. Unlike a web page, a game cannot wait for a missing packet to be resent — by the time it arrives the information is out of date — so the game has to guess, and the guesses are what you see as glitches:

enemies freezing and then jumping to a new position;
your shots or abilities not registering;
being pulled back to where you were a second ago (rubber banding);
voice chat breaking up into robotic fragments.

Even 1–2% loss is noticeable in a shooter; sustained loss above that makes competitive play frustrating.

Where the loss happens decides who can fix it. Work through the chain from your side outward:

Wi-Fi first. Plug the PC or console in with a cable and play a few matches. If the problem disappears, it was your wireless link.
Home network. Pause downloads, cloud backups and streams on other devices. Restart the router; check the cable and the router's firmware.
Provider. If loss persists on a cable, run a trace to the game's server (for example tracert on Windows, mtr on Linux/macOS, or a tool such as PingPlotter) for a few minutes while the problem happens. Loss that starts at a hop inside your provider's network and continues to the end is something only the provider can fix — send them the trace.
Server. If many players on the same server complain at the same time, it is the server or the game. Check the game's official status page or social channels before changing anything at home.

Loss that appears only at one middle hop of a trace, but not at the hops after it, is usually harmless: many routers simply don't prioritise replying to trace requests.

Some games have their own specific symptoms and fixes; for Escape from Tarkov, see our Tarkov packet loss guide.

Rubber banding

Rubber banding is the feeling of being snapped back to an earlier position, as if tied to an elastic band. Your game client moves your character immediately when you press a key (so the game feels responsive), but the server has the final say. When the server didn't receive your movement — because of packet loss — or rejects it, it sends back the position it believes is correct and your client corrects itself.

Occasional rubber banding during a busy moment is usually the server struggling; constant rubber banding on your side only is almost always your connection.

Desync

Desync (desynchronisation) is when your game and the server disagree about what is happening — you see an enemy in one place while the server has them somewhere else, or you see a door open that is still closed for everyone else. A little desync is built into every online game because information takes time to travel; it becomes a problem when latency is high or the game's netcode handles it badly.

Read the full explanation, with examples from different games, in our article on desync in gaming.

Tick rate

The tick rate is how many times per second the game server updates the world: reads everyone's inputs, simulates movement and hits, and sends out the new state. A 20 Hz server ticks every 50 ms; a 128 Hz server roughly every 7.8 ms. Between ticks, nothing new is decided, so a higher tick rate shortens the extra delay on top of your ping.

Real examples show how differently studios weigh this:

Game	Server update rate	Notes
VALORANT	128 Hz	Riot chose 128-tick servers so that defenders holding an angle have time to react; each server frame has to finish within 7.8125 ms.
Counter-Strike 2	64 Hz + "sub-tick"	Servers still tick 64 times per second, but inputs are time-stamped between ticks so the server can evaluate the exact moment you clicked.
Overwatch	63 updates/s (PC, since 2016)	Blizzard's 2016 "high bandwidth" update raised the client update rate from 21 to 63 per second.
Apex Legends	20 Hz	Respawn has argued that going from 20 to 60 Hz would triple bandwidth and CPU cost to save about two frames of delay in the best case. More in our Apex tick rate article.
Fortnite	30 Hz	Figure from independent network analysis in 2019 that compared it with Apex.

A higher tick rate is not automatically "better netcode". It costs server CPU and bandwidth, and a high-tick server is still only as good as your connection to it. If you get killed behind walls with a 120 ms ping, the ping is the bigger problem.

Netcode, lag compensation and peeker's advantage

Netcode is the umbrella term for how a game hides network delay. Three techniques appear in almost every modern multiplayer game:

Client-side prediction — your own character moves the instant you press a key, without waiting for the server. When the server disagrees, you see a correction (rubber banding).
Interpolation — other players are shown slightly in the past, smoothly blended between the last two updates, so they don't stutter. The buffer is usually a tick or two.
Lag compensation — when you fire, the server "rewinds" other players to where they were on your screen at that moment and checks the hit there. This is why you can sometimes be hit after you have already reached cover: on the shooter's screen, you hadn't.

Peeker's advantage is a side effect of all three. The player who moves around a corner sees the defender a little before the defender's screen shows them, because the peeker's movement has to travel to the server and on to the defender first. Higher tick rates, low interpolation buffers and low ping all shrink that window; Riot has publicly discussed reducing it as one of the main goals of VALORANT's network design. Some players also try to exploit delay on purpose — see ping abuse in Tarkov.

Dedicated servers vs peer-to-peer

On a dedicated server, the publisher runs a machine in a data centre that hosts the match; every player connects to it and it alone decides what happened.

In peer-to-peer (P2P), players' own consoles or PCs connect directly to each other. In many P2P games one player is the host whose machine acts as the authority, while others connect to that host. P2P is cheap for the publisher and can give very low latency between players who live close together, which is why rollback-netcode fighting games commonly use it. GTA Online's free-roam sessions are another well-known example of a peer-to-peer design.

The downsides:

Host advantage — the host has zero latency to the authority, everyone else does not.
Host migration — if the host leaves, the match pauses or ends while a new host is chosen.
Exposed IP addresses — peers have to know each other's address, which is what makes some kinds of harassment and denial-of-service attacks possible.
NAT trouble — players behind restrictive routers may be unable to connect to each other (see NAT type).

Many games use a mix — dedicated servers for competitive modes and P2P for co-op or lobbies — so the same game can feel different from one mode to another.

NAT type

Your router uses NAT (network address translation) to share one public IP address between all your devices. How strictly it handles unsolicited incoming connections is summarised by consoles as a NAT type:

Xbox	PlayStation	What it means for you
Open	Type 1 / Type 2	Can host, join anyone and use party chat normally. Type 2 (behind a router that forwards correctly) is the normal good result on PlayStation.
Moderate	—	Can join most games, rarely chosen as host, some players can't connect to you.
Strict	Type 3	Can only connect reliably to players with an open NAT; party chat and joining friends often fail.

NAT type matters most in peer-to-peer games and voice chat, much less for dedicated-server matches. The usual fixes are enabling UPnP on the router or forwarding the ports the console maker lists for your platform. Avoid putting a console in the router's DMZ unless you understand the security trade-off.

Server region

The server region (EU West, US East, Asia and so on) is the data-centre location your matches are hosted in. It is the biggest single factor in your ping: pick the region closest to you, unless your friends or your preferred language community play elsewhere. Some games choose automatically by lowest ping; others let you lock a region.

Our separate article on server regions covers how region selection, region locking and cross-region play work.

Server browser

A server browser is a list of running servers you can pick from yourself, usually with columns for ping, player count, map and rules. It is the opposite of automatic matchmaking, where the game places you in a match.

Server browsers are typical for games with community-run or persistent servers — survival games such as Rust, or community servers in Counter-Strike 2 — where the specific server (its rules, mods, wipe schedule or population) matters as much as the match itself. When choosing, sort by ping first and check the player count: an empty server that shows great ping is no use if nobody plays on it.

Queue position

A queue position is your place in line when a game limits how many players can enter at once — a busy MMO realm at launch, for example — or while matchmaking looks for a match. The number and the estimated time usually update as players ahead of you leave the queue. Read more in our article on queue position.

Priority queue

"Priority queue" is used in two opposite ways:

Faster access — some games or services move certain players ahead in a login or matchmaking queue, for example players reconnecting to a match they were already in.
Penalty queue — in competitive games, players who leave matches or are reported often are sent to a separate, slower queue, usually matched with other penalised players. Dota 2 and League of Legends both call this "low priority" queue; it typically has to be cleared by finishing a number of games or waiting out a timer.

If a game says you are in a priority queue, check which of the two it means — the tooltip or the support page will tell you whether it is a perk or a penalty.

Disconnect timer and reconnecting

A disconnect timer is the window a game gives you to come back after your connection drops. While it runs, your slot is held — your character may stand still, be controlled by AI, or simply be missing — and you can usually rejoin from the main menu. If the timer runs out, the game treats you as having abandoned the match.

What happens next depends on the game and the mode: casual modes usually just replace you, while ranked modes commonly apply a rank loss, a matchmaking cooldown or a penalty queue. If your connection drops, reconnect immediately rather than restarting your PC or router unless you have to — a full restart can take longer than the timer.

Proxy servers and VPNs

A proxy or VPN routes your game traffic through another server before it reaches the game. Because it adds a stop on the way, it normally increases ping. It helps only in one situation: when your provider's own route to the game server is unusually bad and the VPN's route happens to be better. That is what paid "gaming VPN" or route-optimising services sell.

Things to know before you try one:

Test it: compare your in-game ping and packet loss with and without it on the same server.
Many games' terms of service forbid using a VPN to change your region — for example to reach easier lobbies or cheaper store prices — and some games act on it.
A VPN hides your home IP from other players in peer-to-peer games, which is why some streamers use one.

How to check your own connection

Before blaming the game, spend five minutes on these checks:

Turn on the game's network stats. Most shooters can display ping and packet loss on screen; Apex Legends, for example, added an on-screen performance display in Season 6.
Play one session on a cable instead of Wi-Fi.
Close background traffic — downloads, cloud sync, video streams on other devices.
Pick the nearest server region and compare.
Run a trace to the game server while the problem happens and keep the result if you need to contact your provider.
Check the game's status page — if everyone is lagging, it isn't you.