Fix guide
Packet loss in only one game: what that actually tells you
Players report this constantly: every other game is fine, this one rubber-bands. It feels like the game is broken. Sometimes it is — and sometimes the game is simply the only application that pushes your connection hard enough to expose the fault.
Reading the clue
If the other games you play use a nearby server and low tick rates while the problem game connects to a distant region or runs high tick rates, the difference is not the game — it is the path and the load. The "broken" game is the messenger.
Cross-check with a neutral test, not another game: measure repeatedly, look at the worst samples and jitter, and repeat it while the line is busy.
Not sure where your problem is? Run the free test first — it takes about 45 seconds and tells you which of the fixes on this page actually apply to you.
Run the connection checkWhen the game really is the problem
- Everyone in the match complains at the same time and it clears up later the same day — server load.
- It started after a specific patch and affects a whole region — server-side change.
- It affects one game mode only, typically the highest player-count one — capacity, not your line.
When it is your line after all
- It gets worse when someone else is uploading.
- Wired or wireless changes how often it happens.
- It shows up in a neutral test too, just less visibly.
What to do
Capture evidence for a week: time, region, whether anyone else was using the connection, and how bad it was. That single note removes the guesswork, and it is also the only thing an ISP or a support ticket will act on. Paid route tools are worth testing only after the evidence points at a specific path at specific hours.
