What causes rubber-banding in games?
If your character snaps backwards and opponents freeze then reappear elsewhere, the cause is usually packet loss. Trace rubber-banding to its source, step by step.
Updated
When one update never arrives, the game tries to fill the gap.
Short answer
Rubber-banding is your on-screen position diverging from the position the server accepts, then being forcibly reconciled. It is almost always a symptom of packet loss or very high jitter — not simply high ping. The first thing to check is Wi-Fi and a saturated home connection.
How rubber-banding actually happens
Online games use prediction to feel responsive. As you run forward, your computer draws the movement immediately rather than waiting for the server to confirm it. Under normal conditions the confirmation arrives within milliseconds and both sides agree.
But if the packets carrying your movement never arrive, the server still believes you are at your old position. When the connection recovers, the server imposes its own version and your character snaps back. That is what you are seeing.
The same thing happens in reverse: if opponents' position updates do not reach you, they appear frozen, then suddenly materialise at their real location.
Rubber-banding is a correction symptom, not a delay symptom. The prime suspect is packet loss.
Why 'low ping but still rubber-banding' is possible
Ping and packet loss measure different things. Ping is how long the packets that do arrive take to return. Packet loss is the proportion that never arrive at all. A connection can show 25 ms ping while simultaneously dropping two percent of packets.
Because the average only counts packets that came back, it hides loss entirely. So if you are rubber-banding, look at the loss readout rather than the ping number.
- Ping: round-trip time of packets that arrive.
- Packet loss: share of packets that never arrive.
- Rubber-banding: the visible result of loss or extreme jitter.
Isolate where the loss occurs
Loss can occur between your PC and the router, between the router and your ISP, between your ISP and the game server, or at the server itself. Each needs a different fix, so eliminate them in order.
The first step is always a cable: a short Ethernet test rules out in-home wireless. The second is emptying the connection. The third is checking whether the same symptom appears in other games or other server regions.
If the symptom shows up only in one game on one server, ask what your friends are experiencing at that moment. If you are all affected simultaneously, the problem is almost certainly server-side.
Collect evidence
If the problem recurs, screenshot the game's network readout. Recording the date, time, server region and loss percentage together makes both your own diagnosis and any provider report far stronger.
The network performance graphs in Rocket League and similar games are particularly useful here; you can line up the moment you felt the symptom with the peak on the graph.
An ordered check for rubber-banding
- 1Look at the packet loss readout, not ping.
- 2Run a short Ethernet comparison.
- 3Stop large downloads and uploads.
- 4Check the modem and cables.
- 5Try the same symptom in another game and region.
- 6Ask whether friends are affected at the same time.
- 7If it recurs, keep records with screenshots.
When the symptom stays on the route
Compare the path to the same CS2 server.
ZeroLag's Windows app compares your normal Counter-Strike 2 route with its Istanbul exit. Measure the difference on your own connection during a three-day no-card trial.
See the free trialNo card required. It cannot fix local Wi-Fi, modem or game-server problems.