Packet Loss and Rubber-Banding in Online Games
Rubber-banding is not lag. It is packets going missing, and a two-minute test tells you whether the fault is yours or theirs.
The short answer
Rubber-banding is caused by packet loss rather than high latency, and the two produce different symptoms: high ping makes actions feel delayed while packet loss makes your character snap backwards as the server corrects a position it never received. A sustained ping test to your router and then to an external address identifies whether loss originates inside your home network or beyond it. Loss inside the home is usually fixable; loss beyond it is your provider's problem.
Verified and last updated August 12, 2026.
- Time needed
- 14 min
- Difficulty
- Intermediate
- Read time
- 3 min
Rubber-banding and lag feel similar and are not the same problem. Treating one as the other is why people spend an evening changing settings that were never involved.
Lag delays things. Loss rewrites them. If your character runs forward and then snaps back to where it was two seconds ago, packets are going missing.
The distinguishing symptom
High ping makes actions feel late but the world stays consistent. Packet loss makes you teleport backwards, because the server never received where you went and corrects you to where it last knew you were.
Step 1: Confirm it is loss rather than latency
The last row matters. A great deal of what gets blamed on the network is local frame pacing, and a network fix will never touch it.
Step 2: Locate the loss with two ping tests
Ping your router 2 minutes
Open Command Prompt and run a sustained ping to your router's address, typically 192.168.1.1 or 192.168.0.1, with a count of a hundred: ping 192.168.1.1 -n 100. Read the loss percentage at the end. Any loss here is inside your home and is yours to fix.
Ping an external address 2 minutes
Run ping 1.1.1.1 -n 100. If the router test was clean and this one shows loss, the problem is beyond your home network. Follow it with tracert 1.1.1.1 to see which hop the loss begins at.
Loss beginning at your first external hop points at your line or your provider's equipment. Loss appearing several hops out is usually a congested route, which nobody local can fix but which frequently resolves itself within days.
Document it before you call
A traceroute showing loss starting at a specific hop is evidence a provider will act on. A description of a game feeling bad is not.
Step 3: Fix what is inside your control
If the router test showed loss, work through these in order:
- Wired connection. Wireless loss is common and often invisible in speed tests. An ethernet cable eliminates the largest source in one step. The wired versus wireless comparison covers when this is and is not practical.
- Cable condition. A damaged or cheap ethernet cable produces intermittent loss that looks like a network fault. Swap it before anything else.
- Channel congestion. If wireless is unavoidable, use the five gigahertz band and pick a channel your neighbours are not on.
- Saturation. A download, a cloud backup or someone streaming can push a connection to full and produce loss. Check what else is running.
- Router load. Old routers drop packets under load. A restart is worth trying; a persistently overloaded router is worth replacing.
Powerline adapters deserve a mention because they are frequently the hidden cause. They work well on good wiring and badly on bad wiring, and the difference is invisible until you test for loss specifically.
The ping reduction guide covers the latency side, which is a separate problem with separate fixes.
What works
What doesn't
Key takeaways
Frequently asked questions
What is the difference between lag and packet loss?
High latency delays everything uniformly, so shots register late but the world stays consistent. Packet loss means data never arrives, so the server and your client disagree about where you are and the server wins, snapping you backwards. The visual signature of loss is teleporting or rubber-banding rather than sluggishness, and the two require completely different fixes.
How much packet loss is acceptable?
Zero, in practice, over a short test. Even one percent sustained loss produces noticeable rubber-banding in fast-paced games because the correction is visible every time. Occasional single lost packets over a long test are normal and not worth chasing; consistent loss across a hundred-packet test is a real fault.
Can I fix packet loss on my provider's network?
Not directly, but you can document it and report it, which is more effective than most people expect. A traceroute showing consistent loss beginning at a specific hop is concrete evidence, and providers respond to that far better than to a description of a game feeling bad. If the loss starts at your first external hop, the fault is likely their equipment or your line.
Does a VPN help with packet loss?
Sometimes, and unpredictably. A gaming VPN can route around a congested path and genuinely reduce loss, but it can equally add a hop and make things worse. It is worth testing if loss is confirmed to be outside your network and your provider is unresponsive, but it is not a fix for in-home loss and it always adds some latency.
About the author
PC Hardware & Performance Editor
Marcus has been building, breaking and repairing gaming PCs since 2011, first as a weekend favour for friends and then for eight years as a bench technician at an independent repair shop in Portland, where roughly a third of the job was diagnosing machines that "ran fine yesterday".
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.