The fastest way to lower ping in Valorant is to cut the wireless and go wired with a LAN cable, then manually lock the nearest regional server instead of leaving it on auto-select. Doing just these two things properly solves more than half of most ping problems.
The rest you work through carefully in order: clearing the background, router settings, and DNS and routing fine-tuning. Follow the steps below.
First, Check Your Own Ping
Valorant shows your ping in real time inside the game. Turn on Network Round Trip Time under Settings > Video > Stats, and the ms value appears at the top of the screen during a match; that is the number to check. The standards are simple.
- 30ms or below: Best. Nothing more to touch.
- 30 to 60ms: A normal range where you can play comfortably.
- 60 to 80ms: A range where you are slightly disadvantaged in fast fights.
- 80ms or above: A range where hit registration lags and you lose out, needs improvement.
Write down your number, apply each step below one at a time, then measure again, and you will know clearly which setting made a difference.
Why Your Valorant Ping Spikes: Diagnose by Symptom
A ping that is always high and a ping that is low but suddenly spikes have different causes, and different steps fix them. Start in game by going to Settings > Video > Stats and turning on the Network Round Trip Time, Network RTT + Processing Delays, Packet Loss, and Network RTT Jitter graphs.
The names below come straight from Riot's own definitions of the four instability icons (High Average Ping, Low Client FPS, Low Server FPS, Network Problem) and the three network graphs. Checked on September 14, 2026; menu labels may have changed in the current client, so trust what the game shows. Watch one full match, then find the row in the table that matches what you see.
| Symptom | What the stats screen shows | Likely cause | Go to |
|---|---|---|---|
| Always high | Network RTT stays high (80ms or more on this guide's scale), packet loss at 0 | Distant server or a tangled route | Step 4, then Step 6 if still high |
| Low, then sudden spikes | RTT shoots up for a moment and the RTT Jitter graph swings, loss near 0 | Wireless interference (Riot: the environment and other radio signals) | Step 1 |
| Spikes at certain hours or when the family is online | RTT Jitter grows, sometimes with outgoing loss | Background uploads and sync, no QoS set (a common cause) | Steps 2 and 3 |
| Low ping but teleporting or shots not registering | Packet loss above 0, Network Problem icon | Line quality or the router (Riot: router diagnostics, then contact your ISP) | Step 1, then your ISP |
| Network stats look fine but it still lags | RTT + Processing Delays sits far more than 20 to 30ms above RTT, Low Server or Client FPS icon | Not the network: processing delay on the server or your PC | Check Riot service status; if it is your PC, check FPS |
The steps in the table are this guide's Step 1 wired connection, Step 2 background cleanup, Step 3 router QoS, Step 4 server lock, Step 5 DNS and IPv6, and Step 6 routing. Step 4 comes with one condition.
According to Riot's Server Select page, your account's shard cannot be changed, and you can only pick a server inside your own shard when you are the party leader or playing solo. The KR shard has a single server, Seoul, while the AP shard chooses among Hong Kong, Tokyo, Singapore, Sydney, Mumbai, and Manila.
If what you actually want is to play on another region's servers, see how to play Valorant in another region. The wireless-interference wording in the table comes from Riot Support's Troubleshoot PC Connection.
Low Ping but Still Laggy: Check Packet Loss and Jitter First
If your ping sits in the 30ms range yet enemies teleport and your shots do not register, the problem is not ping but packet loss and jitter. The packet loss graph is split into Incoming and Outgoing.
Incoming loss is on the path from the server to your PC, outgoing loss is on the path leaving your PC, so the direction tells you where to look. In Riot's own words, high quality wireless and most wired connections should have near-zero packet loss at all times.
Jitter is read on the Network RTT Jitter graph, which shows how your Network RTT changes from packet to packet; Riot explains that ping spikes and high network jitter are often the causes that necessitate additional buffering.
One more thing: in normal operation, Network RTT + Processing Delays should sit roughly 20 to 30ms above your Network RTT. If the gap is much larger, look at processing delay on the server or your PC instead of the network.
- 1Go wired and play one matchRiot lists this, alongside restarting your router, in its response steps for both High Average Ping and Network Problem. If loss drops to 0 and the jitter graph flattens, wireless was the cause.
- 2Stop anything uploadingPause cloud sync, backups, and any other traffic going out, then look again. If outgoing loss or jitter disappears, finish with Steps 2 and 3.
- 3Power-cycle the router and measure againIf loss remains, capture the stats screen and contact your ISP along with the tracert result from Step 6. Riot's own order is the same: router diagnostics, then your ISP.
Network Buffering is an option that cushions jitter, not one that lowers ping. How to tell whether you actually have grounds to raise it is covered separately in Valorant Network Buffering.
The official checks that follow going wired (the Windows network troubleshooter, public DNS, firewall exceptions, and so on) are in Riot Support's Troubleshooting Your Network Connection, and to rule out a server-side problem, open Riot's Technical Support page and click VALORANT under Service Status at the bottom.
One caveat: packet loss and jitter cannot be reproduced once the moment has passed. Which round it spiked in has to be kept on screen, and how to do that continues in the recording section below.
Valorant Ping High or Unstable Only in the Evening? Check the Time of Day and Your Home Line
If your Valorant ping is fine in the morning but climbs, or the network round trip time variance graph starts jumping, only in the evening, the cause is more likely outside your PC than inside it.
When everyone on the same network gets home and starts streaming, the provider's side of the connection, or shared equipment in your building, gets busy.
In apartment buildings and on connection types where neighbors share capacity, a speed test can look healthy while latency still swings with other people's usage. If the congestion sits on your own line, switching servers often does not help, so check the timing and the line first. Find the row in the table that matches your situation.
| Situation | Where to look | How to check |
|---|---|---|
| Normal in the morning, high only in the evening | Peak-hour congestion on the provider's network | Log network round trip time on the same server during the day and at night, then compare |
| Ping swings every evening in an apartment building | Shared line or in-building equipment | Measure again on a wired connection at the same hour and ask the provider to check the building's equipment |
| Connected through a 4G or 5G home router or hotspot | Variance on the mobile wireless link | Compare with a fixed wired line, or another location, at the same time of day |
| Spikes at fixed times regardless of who is online at home | A middle hop on the route beyond your provider | Run tracert (Step 6) to see which hop the delay grows on |
Time-of-day problems rarely respond to PC settings, and if you describe them to a provider over the phone you are likely to hear that your speed is fine. The fix starts with records.
Collect a few days of when, on which server and how many milliseconds, and the pattern shows whether it is peak-hour congestion or a routing issue. Those notes also give the provider something concrete to investigate. Work through it in this order:
- 1Log ping by time of dayPlay one match in the morning, one in the evening and one late at night, and note network round trip time, its variance and packet loss from the stats screen. If only the evening is high, the line is the more likely suspect.
- 2Re-measure wired at the same hourIf you were on Wi-Fi, switch to an Ethernet cable at the same time of day and play one more match. If it is still high only in the evening, your home Wi-Fi is not the cause.
- 3Check how your building and line are set upFind out from your provider's support or your account page whether you are on a shared building line or fiber to your unit. If you use a mobile home router, compare it with a fixed line where possible.
- 4Contact your provider with the recordsSend several days of timed records plus your tracert results from Step 6, and ask for an evening-hours quality check. Ask whether a different plan or connection type is available too.
Step 1: Cut the Wireless and Go Wired
This is the most basic step and the one with the biggest effect. Wi-Fi ping spikes constantly because of walls, distance, and signal interference from other devices. Running a LAN cable directly from your router to your PC noticeably reduces both delay and ping variation (jitter).
If your router is far and running a cable is hard, you can also use a powerline adapter or the wired port on a mesh node.
Step 2: Clear Out Background Traffic
Even if your line is fast, your ping goes up if someone or something eats up the bandwidth. Check the following before you launch the game.
- Pause automatic downloads from Steam, Epic, and Windows Update.
- Close streaming tabs like YouTube and Netflix.
- Pause cloud backup sync (Google Drive, OneDrive).
- Check whether someone else in the house is doing a large download.
It is common for ping to drop by double digits just by stopping a single background download. It is the same principle that applies across fast shooters in general, not just Valorant but also games like Counter-Strike.
Step 3: Prioritize Game Traffic with Router QoS
QoS (Quality of Service) is a feature that lets your router prioritize game packets so they are handled before other traffic. Go to your router's admin page (usually 192.168.0.1 or 192.168.1.1) and set your PC as a priority device under QoS or the gaming mode section. Gaming routers like ASUS and Netgear come with game traffic prioritization and bufferbloat prevention built in.
Step 4: Lock Your Regional Server to a Nearby Location
Valorant lets you pick your server manually. Do not leave it to auto-select; choose and lock the server with the lowest ping directly from the play screen.
Note that your account's shard cannot be changed: a KR-shard account only sees Seoul, while an AP-shard account picks only from servers in its own shard such as Hong Kong, Tokyo, and Singapore.
If you are playing with a friend in a different region, it is better to discuss and pick the server where both of your pings are most balanced.
Since each region's ping is shown as a number on the server selection screen, you just compare them directly and pick the lowest. Distance equals delay, so the closer the server, the better.
Step 5: Tweak DNS and IPv6
From here on is the fine-tuning stage. DNS itself does not greatly reduce game latency, but a stable DNS reduces initial connection drops. Using your ISP's default DNS gives the fastest access to the internal network.
- KT (Korea): 168.126.63.1 / 168.126.63.2
- SK Broadband (Korea): 219.250.36.130 / 210.220.163.82
- LG U+ (Korea): 164.124.101.2 / 203.248.252.2
- Universal alternatives: Google 8.8.8.8, Cloudflare 1.1.1.1
Turning IPv6 off is not a ping fix but an optional test to narrow down the cause. If your ping spikes for no reason, disable IPv6 only in your PC's network adapter settings for a moment, compare, and turn it back on if nothing changes. If your line carries IPv4 over IPv6, do not disable IPv6 on the router.
Step 6: The Last Card if Your Routing Is Tangled
If you have gone through all the steps above and your ping is still abnormally high only during certain hours, the bottleneck is at an intermediate hop on the path from your ISP to the game server. You can use the tracert command in the Command Prompt to find which hop the delay spikes at.
If the path itself is the problem, a gaming-focused routing service (ExitLag, NoPing, etc.) can sometimes reduce your ping by sending packets along a shorter route.
If You Want to Protect Your Ping While Recording
It is a shame to finally get your ping down, then turn on a recording program to save a clip and have your frames drop and ping spike. DOR uses a low-load capture method, so it has little impact on ping and frames even while recording Valorant. You can capture your fight moments without missing them while keeping the full effect of your network optimization.
There is one more use for this. The packet loss and jitter from the table above cannot be reproduced after the fact, but DOR detects Valorant automatically, records the full match, and keeps highlights like kills as auto-clips in its library, so the fight where your ping spiked is saved as video.
Share that clip as a dor.gg link and you have evidence for a before-and-after settings comparison or an ISP ticket that needs no explaining. Cutting and sharing a clip is covered in how to clip Valorant.
Summary: In Order of Impact
It is always most efficient to tackle ping improvement starting with what has the biggest effect.
Lock down the big gains with a wired connection and a nearby server, add stability with clearing the background and router QoS, then approach DNS, IPv6, and routing as fine-tuning that polishes the last few ms. If you measure your ping again after each step to confirm the effect, you can quickly find the optimal combination for your setup.
