How to lower ping in Valorant (and what won't help)

Most guides to lowering ping in Valorant list the same six tips and then sell you something. This one starts with diagnosis, because the fix for a bad route is useless if your actual problem is wifi. It also tells you which popular fixes do nothing, and why people believe in them anyway.

We build a routing product, so we have an obvious interest here. We also measure routes all day, which is exactly why we won't promise you a number. Nobody can, honestly.

What your ping number actually means

Turn on the in-game stats first. In the client, go to Settings, then Video, then Stats, and set Network Round Trip Time to Text or Graph (that is the current path as of July 2026; Riot moves settings around occasionally). Turn on Packet Loss while you're there.

The number you see is round trip time: your input travels to the server, and the server's response travels back. It is not one-way delay, so a 40 ms reading means roughly 20 ms each way. Riot's own network guide confirms this and is worth ten minutes of your time.

Some context for what counts as good. Valorant has run every match on 128-tick servers since launch, with no announced change as of July 2026, and that gives the server a 7.8 ms budget per tick. When Riot launched the game in 2020, their stated goal was ping under 35 ms for most players. In a 2021 engineering post they described anything over 60 ms as a problem for how the game is designed. Both numbers are from 2020 and 2021; Riot hasn't published newer targets, so treat them as rough guidance, not current spec.

One more distinction before you touch anything: constant high ping, ping spikes, and packet loss are three different problems with three different causes. A steady 85 ms points at distance or routing. Spikes from 30 to 200 ms point at your wifi, your router, or someone on your network watching 4K video. Packet loss on a good connection should be near zero, and if it isn't, no amount of server switching will save you.

Find your problem before you fix it

Fifteen minutes of testing beats an evening of random tweaking. Work through these in order.

Check ping to every server region. The Riot client has a Server Select tool that shows a live ping estimate for each datacenter and lets you set preferred servers per queue (current behavior as of July 2026). Write down your best number. That is your baseline, and everything else is measured against it.

Test your connection under load. Run the Waveform bufferbloat test twice: once with nothing else running, once while something downloads. The bufferbloat project treats a loaded-latency rise of 15 to 25 ms as under control; if yours jumps by far more, your router queues packets badly, and that is your real problem. Skip ahead to the router section.

Compare cable and wifi. Play one match wired, one on wifi, with the ping graph on. If the wired match shows a flat line where wifi showed spikes, you've found it.

Trace the route. Riot support has instructions for running tracert against their servers. You're looking for the hop where latency jumps. A jump at hop 2 is your home network or ISP's local segment. A jump at hop 8, after your traffic left your city, is a routing problem you cannot fix with settings.

If your ping is fine everywhere except Valorant, the usual suspects are a background update saturating your line, or your ISP routing Riot's network differently from the speed-test servers everyone benchmarks against. Speedtest results say almost nothing about game routes.

Fix 1: pick the right server region

The biggest free win, and the one the game partly hides from you.

Riot assigns your account a region when you create it, based on where your IP address appears to be. That geolocation gets it wrong often enough that Riot wrote a public explanation back in 2020, after Turkish players kept landing on the wrong servers because their ISPs' address blocks geolocated incorrectly. If your whole region is wrong, the fix is a Riot Support ticket, since you cannot change account region yourself.

Within your region, use Server Select to set preferred datacenters for each queue. Two things to know about it. The preference is a request, not a guarantee; Riot will still place you elsewhere when queue health demands it, or when your party spans regions. And the ping estimates in that list are the single most useful latency readout you have, because they measure the actual game path, not a generic internet test.

The payoff scales with geography. As a rough illustration: inside a small country the difference between two datacenters might be 5 ms, while across a large region it can be 40 ms or more. Check the list, don't assume.

Fix 2: stop your router from queueing game packets

This is the fix most likely to help people who "have fast internet" and still spike.

When anything on your network pushes bulk traffic (a cloud backup, a game download, someone streaming), your router buffers the excess instead of dropping it. Your game packets wait in that queue behind everything else. The bufferbloat project documents this adding hundreds of milliseconds, sometimes seconds on connections that look perfectly fast on paper. Worse for games: Riot's engineers observed that congested routers preferentially drop small UDP packets, which is exactly what game traffic is.

What actually works:

1. Stop the bulk traffic while you play. Pause updates, backups and torrents on every device, not just your PC. This is free and often enough.
2. If your router supports smart queue management (look for SQM, fq_codel or cake in its settings), turn it on and set the bandwidth to about 85 percent of your measured line rate. fq_codel is a published internet standard (RFC 8290), not a gaming gimmick.
3. Re-run the Waveform test and confirm the under-load latency stopped jumping.

Be clear about what this fixes: latency under load. It will not lower your idle ping by a single millisecond. If your problem is a steady 90 ms at 3 am with nothing else running, this section was never going to help, and a router that advertises itself as a gaming router will not either.

Fix 3: use a cable, for the right reason

Every ping guide says "use ethernet." Almost none of them say why, and the why matters, because it tells you what to expect.

A cable does not move you closer to the server, so your base ping barely changes. What it removes is the wireless link's variance: retransmissions when a frame gets lost, contention when your neighbor's network overlaps your channel, latency wobble when you're two walls away from the router. Those show up in game as spikes and micro-stutter, not a high steady number.

So: if your ping graph is flat but high, a cable won't fix it. If the graph is jagged, a cable is probably the best thing you can do, and it costs less than a skin. If you genuinely cannot run a cable, at least get the router and the PC in the same room, and prefer the 5 GHz band.

Fix 4: the route between you and Riot

Here is the part of the problem that lives outside your house, and the part most guides skip because there's no settings menu for it.

Your ISP does not route your packets down the fastest path. It routes them down the cheapest acceptable path, because the protocol that glues the internet together, BGP, deals in business relationships rather than milliseconds. Riot's engineers wrote the clearest public explanation of this we know, with a real example: a route between two nearby cities that should have taken 14 ms took 70 ms, because the traffic detoured to follow cheaper transit.

Riot attacked this from their side by building Riot Direct, their own network with peering points around the world. It worked: by their published numbers, the share of NA players under 80 ms went from 31 to 80 percent. But Riot's network can only start helping once your packets reach its edge. The leg from your ISP to that edge is yours, and when Riot's own troubleshooting advice runs out, it literally ends with "contact your ISP."

That leg is what rerouting tools operate on, so let's be honest about the category, including our own product. If your ISP already hands traffic to Riot cleanly, and thanks to Riot Direct many do, a tunnel adds a detour plus encryption overhead, and your ping goes up, not down. One independent test we found measured a VPN improving game ping in 2 out of 60 scenarios, and adding 5 to 40 ms in the rest. Blind rerouting is a coin flip weighted against you.

Rerouting earns its keep in one situation: your traceroute shows a genuine detour, the kind of 14-versus-70 path Riot described, and an alternative path exists. Flick doesn't guess. It sends your game traffic down three relay paths at once, keeps whichever copy arrives first, and when the direct route wins, it tells you so and stands down. If your route is already good, it will tell you that you don't need it that day. The principle holds whatever tool you use: measure with it and without it, per server, and believe the measurement.

Notes for Turkey, Europe and the Middle East

Riot doesn't publish a live datacenter map, but community-maintained lists (as of late 2023) put EU-region servers in Frankfurt, Paris, London, Warsaw, Madrid, Stockholm and Istanbul, and the in-client Server Select list is the authoritative check for what your account can reach today.

Turkey is the interesting case. Istanbul has its own datacenter, yet plenty of Turkish players end up on Frankfurt anyway. Two separate reasons show up in community threads. The old one is the geolocation problem Riot acknowledged in 2020: some Turkish ISPs' addresses looked non-Turkish, so accounts got misplaced. The current one is voluntary: high-rank players report choosing Frankfurt because Istanbul's small high-elo queue takes too long, and they accept 50 or 60 ms as the price of finding a match. If that is your situation, no network fix changes queue population; the tradeoff is the tradeoff. Istanbul also drops off some players' server lists from time to time; check Server Select before assuming it's gone.

For the Middle East, Riot opened a Bahrain datacenter in 2020, which put a server far closer to Gulf players than the old EU-only setup. As of July 2026, servers in the region have been in flux for several months and players widely report being placed on Riyadh and Mumbai instead; the cause is unclear and we won't guess at it here. If you're in the region, treat the Server Select ping list as the ground truth for any given week.

In all three regions, your best server is an empirical question. It changes with Riot's infrastructure, your ISP's routing and even time of day.

Things that will not lower your ping

Each of these survives because it either used to matter, helps a different metric, or benefits whoever sells it.

Changing DNS servers. DNS translates names to addresses before a connection starts. Once the match begins, Valorant sends UDP packets (ports 7000 to 8000) straight to a server address that is already known. There is no DNS lookup on the path your game traffic takes, so no DNS provider can shorten it. Faster DNS can make websites feel snappier and that is where the belief comes from, but the in-game number cannot move. Even DNS vendors admit this when asked directly.

Registry tweaks and Nagle's algorithm. The famous TcpNoDelay tweak disables Nagle's algorithm, which batches small TCP writes. Valorant's game traffic is UDP. There is no Nagle on UDP, so there is nothing to disable. This one is a fossil from 2000s-era games that really did run over TCP.

RAM cleaners and game boosters. Independent testing has put their effect at somewhere between nothing and placebo on adequate hardware. Whatever they do to your frame rate, none of them touch the network path, because they can't.

Windows Game Mode and closing idle apps. Game Mode manages CPU and GPU priority. It can help frame rates on busy systems; it does not touch networking. Closing apps only helps your ping when the app was using bandwidth, which is the router-queue story from Fix 2 wearing a different hat. Closing an idle browser does nothing.

Hardware upgrades sold as ping fixes. A gaming router, a new network card or more RAM will not reroute your packets. The one router feature that genuinely matters for latency is the queue management from Fix 2, and plenty of cheap routers running decent firmware have it.

If you notice a theme: your ping is made of distance, routing and queueing. A tweak that touches none of those cannot help, whatever its marketing says.

Small things worth checking

None of these deserve their own section, all of them have fixed a real problem for someone.

• Run Repair from the Riot client settings if your ping is normal but the game feels wrong; a damaged install can produce symptoms that look like lag.
• Valorant has a Network Buffering setting. Leave it on Minimum unless you get frequent packet loss; Riot suggests raising it only for genuinely unstable connections.
• If a strict firewall sits between you and the internet, confirm UDP 7000 to 8000 is open, per Riot's port list.
• Laptops on battery sometimes throttle the wifi radio. Plug in.

Common questions

Why is my ping suddenly high when it was fine yesterday?

Something changed, and it usually isn't Riot. Check for a background download first, then re-run the bufferbloat test, then check whether Server Select is quietly placing you on a different datacenter than usual.

Why is my ping high only in Valorant when the rest of my internet is fine?

Because Valorant's servers sit in different places, on different routes, than whatever your speed test measured. Trace the route to Riot and to anything else, and compare where they diverge.

Is 60 ms good enough for Valorant?

You can play well at 60 ms. Riot's own engineering posts treated sub-35 ms as the launch target and 60-plus as where problems start, so if a better server or a fixed route can get you lower, it is worth the fifteen minutes.

Do VPNs lower ping in Valorant?

Occasionally, and only when your ISP's route to Riot is genuinely bad. In the one independent test we found, a VPN helped in 2 of 60 cases. Never pay for a rerouting product, ours included, without measuring your before and after on your own connection.