High ping is the silent enemy of competitive gamers. At 200 ms, by the time you see the enemy on screen they have already moved. Your shots land late. You die behind cover. It feels unfair, but it is network physics.
Here is the part nobody tells you: most of what people call "high ping" is not ping. It is delay variation and packet loss, which ruin a match in different ways and are fixed in different ways. That is why this guide starts by measuring, not by changing settings.
Before You Change Anything, Measure
Changing settings without measuring is like swapping parts without testing. Run these three tests with the game closed and write the numbers down. They tell you where the problem is, and whether whatever you do next actually helped.
1. Test your own router
Open Command Prompt and run ping 192.168.0.1 -n 50, replacing that address with your router's, which appears as "Default Gateway" in ipconfig. On Ethernet, expect under 2 ms and zero loss. If the number already swings here or packets go missing, the problem is inside your home: the cable, the network card or the router itself. Nothing you change in Windows will fix that.
2. Test the way out
Run ping 1.1.1.1 -t and leave it going for two or three minutes while you use the PC normally. Stop it with Ctrl+C and read the summary. Three things matter: minimum, maximum and loss. A minimum of 12 ms with a maximum of 180 ms means your connection spikes, and it is the spike that kills you in a match.
3. Find out where the delay appears
Run tracert followed by the game server address, or a known target. Each line is one hop toward the destination. What matters is not the number of hops, it is the point where the time jumps and never comes back down. If hop 2, your ISP's own network, already shows 90 ms, the rest of the path is innocent and no tweak on your PC will fix it.
Ping, Jitter and Packet Loss Are Not the Same Thing
All three show up as "lag" and all three need different fixes:
- Ping is the round trip time to the server. High but steady ping is bad, yet predictable, and the game compensates for part of it.
- Jitter is how much that time varies. It is the worst of the three for competitive play, because the server cannot predict your next packet. It is what produces the teleporting character and the death that lands after you are already behind a wall.
- Packet loss is information that simply never arrives. At 2% loss, one in every fifty shots you fire may not exist as far as the server is concerned.
If your test showed low ping but a maximum far above the minimum, your problem is jitter. If it showed loss, do not bother with game settings: it is physical connection or saturation.
Where Ping Comes From
The number in the corner of your screen is a sum:
- Local latency: PC to router. Under 2 ms on Ethernet, 5 to 20 ms on Wi-Fi.
- ISP latency: router to game server. Depends on your provider and the route it picks.
- Server latency: processing time on the other end. You do not change this.
- Your own system delay: the packet queue inside Windows and how long the network card takes to hand data to the game.
Only the last two are within your reach, and the last one is the one most people ignore.
Wi-Fi or Ethernet
Wi-Fi adds variable delay, which is exactly the harmful kind. A 30 ms connection with 20 ms of swing either way bounces between 10 ms and 50 ms, and that seesaw is what shows up as a stuttering character.
Use a cable whenever you can. When you cannot, prefer the 5 GHz band, stay close to the router, and avoid gaming with a microwave running on the same wall, since it interferes with 2.4 GHz. A cheap USB Wi-Fi adapter is usually worse than the laptop's built-in card.
What Is Stealing Your Connection While You Play
This is the most common cause of ping spikes at home, and the easiest to test. While the second test is still running, have someone start a 4K video or begin a large download. If the number jumps, you found your culprit.
- Windows and game store updates downloading in the background. Steam and Epic keep updating other games while you play.
- Cloud backup uploading files. A saturated upload delays even the game's tiny packet, because it waits in line behind your file.
- Bufferbloat. When the line saturates, the router queues packets instead of dropping them, and that queue becomes delay. It is why a download pushes ping to 300 ms even on fast internet. If your router offers QoS or smart queue management, turn it on and cap bandwidth at about 90% of what you pay for: you lose a little download speed and gain stability.
Server and Route: What You Choose and What You Do Not
Server region. The highest impact decision, and the most forgotten one. Playing on a North American server from South America costs 100 to 150 ms that no tweak recovers. Check that the game did not get stuck on the wrong region after an update.
Exclusive tips
Want more guides like this?
Leave your email and we'll let you know when a new optimization guide drops. No spam, unsubscribe anytime.
Only optimization guides worth your time. Unsubscribe anytime.
Two paths to a faster PC
Forget endless tutorials. Find out in 1 minute what your setup needs — or let our technicians do everything for you, live.
Find my ideal plan
Answer a few questions and UPGUIDE estimates your FPS gain in your main game.
Run free analysisDone by techniciansLet UPBOOST handle it
Full remote optimization, live on Discord, in a 1 to 3 hour session. 15-day guarantee.
View plans & pricing+12,000 PCs optimized
Still comparing? See UPBOOST vs. DIY vs. free boosters
Gaming VPN. It serves one specific case: when tracert shows your ISP's route to the server is bad and the VPN offers a better path. There it genuinely helps. Everywhere else it adds a hop and makes things worse. Test it during the free trial and compare against the numbers you wrote down.
DNS. Switching to 1.1.1.1 or 8.8.8.8 speeds up loading websites and can speed up the game's login. It does not reduce in-game ping, because the match is already connected by IP and no longer queries DNS. Anyone promising otherwise is selling something.
What to Adjust in Windows
These target the delay born inside your PC. Write down the original value of each setting before changing it, and change one at a time, measuring in between.
Network adapter advanced properties
In Device Manager, under your adapter's advanced properties:
- Interrupt Moderation: disabled. It batches interrupts to save CPU, at the cost of delay.
- Flow Control: disabled.
- Green Ethernet and Energy Efficient Ethernet: disabled. Power saving on a network card costs milliseconds.
- Large Send Offload: disabled, helps reduce variation.
- Receive Side Scaling: enabled, spreads network processing across cores.
Not every card exposes every option, and some use different names. If an option does not exist on your adapter, move on.
Nagle's algorithm
It bundles small packets before sending, which is great for file transfer and bad for games, which live on small frequent packets. You disable it in the registry by creating TcpAckFrequency=1 and TCPNoDelay=1 under your network interface key. Touching the registry calls for a backup first, and the gain here is a few milliseconds: leave this one for last.
TCP auto-tuning
On unstable connections, automatic buffer tuning can increase variation. To test, run netsh int tcp set global autotuninglevel=disabled in an elevated PowerShell. If your measurements do not improve, put it back with netsh int tcp set global autotuninglevel=normal. Do not leave it disabled out of habit: on a good connection it helps.
System interrupt latency
When a badly behaved driver holds the processor for too long, the game's packet waits in line even with perfect internet. The symptom is periodic stuttering alongside ping swinging for no visible reason. That problem has its own diagnosis, covered in the guide on what DPC latency is and how to measure it.
When the Problem Is Not Your PC
If you are on Ethernet, the router test is clean, nothing is downloading, and tracert shows the time jump at the second or third hop, you have hit the limit of what you can do from here. The next step is opening a ticket with your ISP with the tracert output in hand, which is a far stronger argument than "my internet is bad for gaming".
Worth remembering: ping and input responsiveness are different things. If the character reacts slowly even with low ping, the culprit is probably input lag between your mouse and the screen, which has nothing to do with the network.
High Ping in One Specific Game
When the number is fine everywhere and bad in a single game, the cause is usually the application itself: wrong server, corrupted cache or a game setting. Some cases have their own fix:
- high ping and desync in FiveM, where the city's server weighs as much as your connection
- high ping and lag in Free Fire, which on PC still goes through the emulator layer
- server lag in Minecraft, where it pays to separate ping from the server choking
- telling lag from ping in Roblox, since the two get confused in that game
When It Is Worth Calling Someone
If you measured, moved to a cable, cut the downloads, checked the server region and the number is still bad, what is left is the tedious part: network driver, system queue, interrupt latency and the dozens of adapter options nobody wants to go through one by one. That is exactly what UPBOOST does live, with you watching the screen, measuring before and after on your own machine. It is not magic and it does not fix an ISP route, but it settles everything on this side of the line. The optimization plans include the network side.
Frequently asked questions
Not during the match. DNS only turns a website name into an IP address, and that happens before you enter the game. Switching to 1.1.1.1 or 8.8.8.8 can speed up page loading and the login screen, but once the match starts the game is already connected by IP and no longer queries DNS.