When a game suddenly gets laggy, most people assume it's either "my internet is bad" or "the servers suck" — but the fix for each is completely different. One means calling your ISP or replacing your router; the other just means switching regions. Get the diagnosis wrong and you'll waste a lot of time fixing the wrong thing.
Start by comparing regions, not staring at one number
Testing "my latency to this one server is 80ms" tells you almost nothing on its own — you don't know if 80ms is good or bad, and you have no idea which part of the network path is the problem. What actually works is testing multiple regions at once and comparing them side by side, using process of elimination to pinpoint the issue:
- Every region is slow and unstable → almost certainly a local network issue (router, Wi-Fi, your ISP line, something else on your network eating bandwidth) — unrelated to which server region you pick.
- Only a few specific regions are bad, others are fine → your ISP's routing to those particular regions is probably taking a bad path or hitting congestion. Switching to a region that tests well should fix it immediately.
- Latency looks fine but the game still stutters → don't just look at the latency number — check packet loss and jitter (latency fluctuation), which are covered below and are usually the real source of that stuttery feeling. (New to these three metrics? Start with Ping, Packet Loss and Jitter Explained.)
Low latency doesn't mean smooth: packet loss and jitter are the hidden culprits
A lot of people only watch one number — ping — but a lot of in-game stutter actually comes from two other things:
- Packet loss: whether the data you send actually arrives. Even at a solid 30ms average, occasional dropped packets show up in-game as sudden "rubber-banding" or your character freezing for a beat.
- Jitter (latency fluctuation): how stable your latency is. If it's 30ms one second and suddenly spikes to 150ms the next, it'll still feel laggy even if the average looks fine — games care more about consistency than about raw speed.
So when diagnosing a connection, don't rely on a single median latency number — look at the fluctuation range (where most samples land, and how high the occasional spikes go) and packet loss together. You need all three to know whether a network path is actually solid.
The 3-step process
Step 1: Test multiple global regions at once, don't test them one by one manually Use PartyPing's solo test — no download, no account. Hit the button at the end of this article and your browser tests latency and packet loss to regions worldwide, with full results in under a minute.
Step 2: Look at the latency range, not just a single number Each region shows a latency range (where most samples fall), not just one number — occasional spikes are captured without making the whole result look worse than it is. Packet loss is shown alongside it for every region.
Step 3: Use process of elimination to pinpoint the issue Scan every region's results: everything bad → check your own network; only some regions bad → switch regions; latency looks okay but packet loss is high or the range is wide → the path is unstable, and switching to whichever region tests cleaner (or reporting it to your ISP) is the move.
What to do once you've diagnosed it
- Confirmed local network issue: check if something else is hogging bandwidth (downloads, streaming, cloud backups), try a wired connection instead of Wi-Fi, and restart your router or contact your ISP if needed.
- Confirmed routing/region issue: just switch to whichever region tested with low latency, a tight range, and low packet loss — you don't need to wait on your ISP to fix anything, switching regions usually fixes it instantly.
- Confirmed jitter issue (latency looks okay but the range is wide): avoid that region regardless of what the average latency says — it'll probably still feel choppy in practice.
Don't guess whether it's your network or the wrong region — test every region at once, and the answer becomes obvious.