How to lower ping
Ping is two things added together: the time light needs to cover the distance, and the time your packets spend waiting in queues. You cannot change the first. Almost every real improvement comes from attacking the second.
See server locationsYour ping has a hard floor
Before changing anything, work out what is actually achievable. Chasing a number below the floor wastes an afternoon.
Light in fibre travels roughly 200,000 km per second, and a round trip covers the distance twice. Real routes are about 1.4× longer than the straight line. That works out at roughly 1 ms of ping for every 70 km between you and the server, before anything else is added.
London to Frankfurt is about 640 km, so the floor is around 9 ms. London to New York is 5,570 km — a floor near 78 ms. No router setting, no ethernet cable and no VPN will beat those numbers, because nothing beats physics.
So the first question is not “how do I lower my ping” but “how far above the floor am I?” If you are playing on a server 5,000 km away and seeing 90 ms, your connection is close to perfect and the fix is a nearer server, not a setting.
If you are 300 km from the server and seeing 90 ms, roughly 85 ms of that is queuing — and queuing is fixable.
In order of how much it helps
Work down this list and stop when you are close to the floor.
Pick a closer server
The single biggest lever, and the only one that moves the floor itself. Most games let you choose a region — a server 500 km away instead of 5,000 km is a 70 ms difference that no other change can match.
Use a cable instead of Wi-Fi
Wi-Fi adds latency and, worse, adds variance. A stable 40 ms plays better than a 25 ms that spikes to 120 ms. Ethernet removes an entire class of problem.
Stop other traffic on the connection
A single large upload saturates the queue and every packet behind it waits. Cloud backup, video calls, streaming and game updates are the usual suspects. This is the most common cause of ping that is fine one minute and terrible the next.
Enable Smart Queue Management on the router
Look for SQM, fq_codel or cake. This is the real fix for bufferbloat — the phenomenon where your ping under load is five times your idle ping. On a router that supports it, this is often a bigger improvement than everything else combined.
Check the 2.4 GHz band
If you must use Wi-Fi, 5 GHz is less congested and lower latency at short range. 2.4 GHz is shared with microwaves, baby monitors and every neighbour.
Advice that does nothing
“Ping reducer” software
Consumer tools that claim to optimise your connection generally change TCP window settings that the OS already tunes better. Some are outright adware. None of them shorten the cable to the server.
Buying more bandwidth
Ping and bandwidth are different measurements. Going from 100 Mbps to 1 Gbps changes how much fits through the pipe, not how long the pipe is. If your ping is bad on an idle 100 Mbps line, a gigabit line will be bad too.
Registry and DNS tweaks
Changing DNS speeds up the first lookup for a domain. It has no effect on ping during a game, because the connection is already established and DNS is not in the loop.
Test your ping under load, not idle. Run a speed test while watching the latency figure — if idle ping is 20 ms and loaded ping is 200 ms, you have bufferbloat, and SQM on your router will do more than every other item on this page.
When a VPN helps, and when it hurts
The honest answer is: usually it adds a little, occasionally it removes a lot. Both happen for the same reason.
Usually it adds latency. Your traffic makes a detour through the VPN server before reaching the game. If that server is not on the direct path, you pay for the extra distance. Expect a few milliseconds on a nearby server and considerably more on a distant one. This is the normal case, and anyone promising a VPN always lowers ping is not being straight with you.
Sometimes it removes far more than it adds. Internet routing is not always sensible. ISPs occasionally send traffic on absurd paths — a connection between two cities in the same country routed through another continent because of a peering dispute. If your ISP's route to the game server is bad, a VPN can put you on a better-connected backbone and cut latency substantially.
It can also stop ISP throttling. Some providers shape gaming or P2P traffic. Because a VPN hides what the traffic is, shaping based on protocol stops working. This shows up as more stable ping rather than lower ping.
The way to know is to measure, not to argue. Note your in-game ping without the VPN, then with a server in or near the same city as the game server. If it drops, your ISP's route was the problem. If it rises by a few milliseconds, that is the detour and it is working as expected.
What ping is realistic
| Distance to server | Physical floor | Good result | Needs attention |
|---|---|---|---|
| Same city (<50 km) | ~1 ms | under 15 ms | over 40 ms |
| Same country (~500 km) | ~7 ms | under 30 ms | over 60 ms |
| Neighbouring country (~1,500 km) | ~21 ms | under 45 ms | over 80 ms |
| Cross-continent (~5,500 km) | ~78 ms | under 110 ms | over 150 ms |
| Opposite side of the world (~15,000 km) | ~214 ms | under 260 ms | over 320 ms |
Straight answers
What is a good ping?
Does a VPN lower ping?
Why is my ping fine then suddenly terrible?
Does more bandwidth lower ping?
Is Wi-Fi really that much worse?
Do ping-reducing programs work?
Measure first, then change one thing
LunoVPN runs WireGuard-based LunoGuard with split tunnelling, so you can route the game through a better path while everything else takes the normal one — or the reverse.