Rubber banding in games: what causes the snap-back and how to fix it

What is rubber banding in a game?

In an online game the server decides where everyone is. Waiting for the server before showing each step would make movement feel slow, so your game shows your own movement at once and tells the server about it. This is called client-side prediction. Most of the time the server agrees and you never notice.

Rubber banding happens when the two disagree. Your updates reached the server late, out of order or not at all, so the server still has you at an older position. When its next update arrives, your game corrects itself and pulls you back, like a rubber band. The same thing makes other players teleport: your game guessed where they were going, then learned where they really were.

So rubber banding is not about how much data your connection can carry. Games send small packets many times a second, and what matters is that each one arrives, on time and in order. That is why it shows up on fast plans, and why a speed test that only reports Mbps can look perfect while the game snaps you around.

What causes rubber banding?

There are five common causes. Three are inside your home, one is on the line to your provider, and one is on the game's side. They are listed in the order worth checking, because the home causes are the most common and the ones you can fix yourself.

Packet loss is the cause people name most, and it is the one a ping counter hides. Your ping can read a steady 30 ms while one packet in fifty never arrives, and that missing packet is the snap-back. In fast shooters, loss of around 1 to 2.5% is already enough to cause missed hits and rubber banding. The packet loss guide covers what counts as acceptable and how to trace where the loss starts.

Jitter is the other. Jitter is how much your ping changes from one packet to the next. When packets arrive in uneven bursts, the game has to guess more, and it guesses wrong more often. Under about 10 ms of jitter is good for every game; over 30 ms usually means rubber banding. What is jitter? explains the numbers.

Is rubber banding caused by high ping?

Not usually on its own. A high but steady ping makes everything feel late: your shots land a moment after you fire and doors open after a pause. It is predictable, and the game can still keep you and the server in step. Rubber banding needs the connection to be uneven, with packets that go missing or arrive in clumps.

If your snap-backs come at regular intervals, such as every few seconds or once a minute, that is its own pattern with its own causes, usually a device scanning for Wi-Fi networks. Lag spikes every few seconds matches the interval to the cause.

How do I tell which cause is mine?

Four checks, about ten minutes in total. Do them in this order and stop at the first one that changes the result.

1. Ask the other players. If everyone in the match snapped back at the same moment, it is the server. Check whether the game has an outage on Is it down? and try another server or match before changing anything at home.
2. Turn on the game's own network display. Many games can show ping and packet loss on screen: Valorant has Network RTT and Packet Loss under Settings, Video, Stats; Rocket League has Performance Graphs; Overwatch 2 has Show Network Latency. The game pages list the setting for each game. Loss above zero during a snap-back points at your connection; zero loss while everyone snaps back points at the server.
3. Play one match on a cable, or stand next to the router if a cable isn't possible. If the snap-backs stop, the cause is Wi-Fi. The Wi-Fi room check compares the room you play in with the router's room.
4. Play while nothing else in the house is using the internet, then again while someone streams or uploads. If it only happens when the line is busy, the cause is bufferbloat. The speed and lag test shows how far your ping rises while the line is loaded.

If it still happens on a cable with the house quiet and other players are fine, look at the device and then the line. The spike finder records your ping for a few minutes and shows whether the hitches follow a pattern, and the device check shows whether the computer or phone itself is the bottleneck.

How do I fix rubber banding on Wi-Fi?

Wi-Fi is a shared radio channel. Every device, and every neighbour's network on the same channel, takes turns. When a packet collides or the signal is weak, the radio sends it again, and the retry arrives late. A few late packets in a row is all a snap-back needs.

• Use a cable if you can. It removes the radio from the path, and it is the one change that settles whether Wi-Fi is the cause. Ethernet vs Wi-Fi for gaming shows how much difference to expect.
• Use the 5 GHz band, or 6 GHz if your router and device both have it. The 2.4 GHz band reaches further but is crowded in most US neighbourhoods and shares its airwaves with Bluetooth and microwave ovens.
• Move closer, or move the router. A router on the floor, in a cabinet or behind a TV loses a lot of signal. One wall away is fine; two floors away usually is not.
• If the console is far from the router and you can't run a cable, a wired link over the home's coax or a mesh node with a cable to the console is steadier than plain Wi-Fi. MoCA vs mesh vs powerline compares them.
• Work through the Wi-Fi fix guide for the remaining steps, one change at a time, with a match between each so you know which one helped.

Why do I rubber band when someone else is online?

When a download, a stream or a cloud backup fills your line, the router holds the waiting data in a queue. Your game's small packets wait in the same queue behind the big ones, so they arrive late and in bursts. This is bufferbloat, and it is the most common reason a game is fine at 2 pm and unplayable at 8 pm in a busy house.

Uploads do it more often than downloads. Many US cable plans have far less upload than download, so one phone backing up photos or one person sharing their screen on a call can fill the upload side by itself, and your game's updates to the server are upload traffic.

• Find the device first. What's using all my bandwidth? shows where each router brand lists live usage.
• Pause or schedule the big jobs: game updates, cloud backups, console downloads. The background downloads guide has the setting for each system.
• Turn on Smart Queue (SQM) on the router. It keeps the queue short for everyone, so nobody has to stop what they're doing. The bufferbloat fix has the settings, and the router guides show where it is on each brand.

When is rubber banding the game's fault?

Sometimes there is nothing at home to fix. A game server that is overloaded falls behind and sends late updates to every player at once. These signs point at the server:

• Everyone in the match snaps back together, and the chat fills with people asking about lag.
• It started right after a big update, a new season or a free weekend, when servers are at their busiest.
• Your game's network display shows steady ping and no packet loss while it happens.
• It follows one server or one match and is gone in the next.

Player-hosted games are a special case. If a friend hosts a Minecraft world or a co-op session from home, every player's movement goes through the host's connection. A host whose upload is full makes everyone else rubber band while the host sees nothing wrong. Smart Queue on the host's router, or pausing the host's uploads, is the fix. The Minecraft page covers home-hosted servers.

Distance matters too. If the game put you on a server in another region, your ping is high and every small hiccup on the long route is more visible. Pick the nearest region where the game lets you; the game server ping test shows which cloud regions are closest to you.

What won't fix rubber banding?

• A faster plan, when the cause is Wi-Fi or packet loss. The game uses a tiny share of even a modest plan.
• Changing DNS. DNS turns a name into an address before the match starts and carries none of your game traffic.
• Port forwarding. Opening a game's ports fixes connection problems such as a strict NAT or voice chat that won't connect. It doesn't make packets arrive more reliably.
• Lowering graphics settings, unless the device is the bottleneck. If the picture is smooth and only your position snaps back, the cause is the network.
• A "gaming" Ethernet cable. Any undamaged Cat 5e or Cat 6 cable carries a game without loss.

Ping-lowering apps and gaming VPNs are a mixed case. They send your traffic over a different route, which can help when the loss is on the route between your provider and the game, and does nothing when the loss starts on your own Wi-Fi or in your router's queue. Rule out the home causes first, since those are free to fix.

When should I call my internet provider?

Call when the problem is still there on a cable, with every other device off the network, on more than one game, and other players aren't affected. That combination points at the line: a loose or damaged coax connector, a failing modem, signal levels that are out of range, or congestion in your area at peak hours.

Bring dates and times. Your last test results stay in this browser, so you can show when ping rose and by how much. A provider can check your modem's signal levels and error counts remotely, and a record of evenings with the same problem gets a technician sent sooner than "my game lags". The game lag guide walks through the full order of checks if you want to be sure before you call.