Your stats overlay shows packet loss, you snap backward in the middle of a duel, and a speed test insists the connection is healthy. By the measure a speed test uses, it probably is. Loss is a different failure, and the first job is not fixing it. It is finding out where it happens, because a fix aimed at the wrong hop changes nothing.
What loss actually does to a Valorant match
Riot runs its servers at a fixed 128 ticks per second. Your client predicts your own movement locally so aiming feels instant, then the server confirms it a moment later.
When the packet carrying your input never arrives, the server doesn’t wait for it. In Riot’s own description of the netcode, “the server commits its prediction as truth, and that client is told to adjust their simulation state back to match the server.” That correction is the snap backward. The server is not wrong. It never heard you.
Shots run on the same machinery, and this part matters more than the rubber-band. Your client sends up the exact simulation time it was showing when you fired, so the server can rewind the world and judge the shot against what you actually saw. Lose that packet and the shot isn’t scored a miss. It is never adjudicated at all. The kill you watched land goes nowhere, because the evidence never arrived.
That is why loss punishes this game harder than it punishes a voice call. A dropped voice packet is a 20 ms gap you barely register. A dropped fire packet is a round.
Step 1: read the in-game number properly
Open Settings > Video > Stats and switch Packet Loss, Network Round Trip Time and Network RTT Jitter to Graph rather than Text. A single number describes one instant. The graph shows the pattern across a round, and that pattern is most of your diagnosis.
Bursts look like a flat zero, a spike to 5 or 10 percent for a second, then flat again. Something intermittent is doing it: Wi-Fi interference, a device waking up to push an upload, a router briefly out of its depth. A constant floor is the other shape, a steady 1 to 3 percent that never clears, and it points at a degraded link in the path. A crimped cable, a dying port, or a saturated hop upstream.
For scale, under 1 percent you won’t feel it. Between 1 and 3 percent is the occasional snap and the shot that did not count. Past 3 percent corrections are frequent enough to lose rounds, and past 10 percent voice chat starts dropping with everything else.
Step 2: measure the same line outside the game
Here is the step the rest of the guides skip, and it is the one that decides which fix is yours.
Valorant’s counter watches exactly one path: your machine to Riot’s edge. It can’t separate your Wi-Fi from your ISP from the route into Riot, and those three have nothing in common except the symptom. So take a second measurement on a path Riot doesn’t own. Right after a match where you saw loss, run the packet loss test in a browser on the same machine, before anything about your setup changes. It sends 300 numbered UDP packets through a relay and counts which numbers never come back, so it fails the same way a game does and sees what a speed test cannot.
Then read the two results as a pair.
- Both show loss. The problem is on your side of the internet: Wi-Fi, cable, router, or your ISP’s local segment. This is the good outcome, because everything in the next section applies to it.
- Valorant shows loss, the browser test is clean. Something specific to the game path or to your machine during play. The route into Riot, a VPN, or Wi-Fi that only falls apart under sustained load. DNS edits and port forwarding will do nothing here. Go to the escalation section.
- Neither shows loss, but you still rubber-band. Then it is not loss, and you are one search away from spending an evening on the wrong problem. Latency that swings, or a queue that fills whenever someone streams, feels identical in a fight. Run the jitter test and the bufferbloat test; if the second one grades badly, the bufferbloat fix is your actual answer.
Run each test twice. Loss moves with whatever else is on the line, so one sample describes a moment, not your connection.
The fixes that move the number
In order of how often they work, which isn’t the order the search results put them in.
Wire in. Wi-Fi is the largest single source of packet loss in home setups, and a cable is the first thing Riot’s own support guide tells you to try. Interference doesn’t show up in signal bars, so full strength proves nothing. If the loss vanishes on Ethernet, you found it, and no router setting fully replaces the cable.
Empty the line, then test again. A cloud backup or a console update filling your upload produces loss that disappears the moment it finishes. Pause uploads specifically, not just downloads. A full uplink degrades traffic in both directions at once, which is a problem of its own with a separate fix.
Power cycle the modem, then the router. Give the modem a full minute unplugged. It’s the one blind step worth taking, because a wedged modem is common and costs you two minutes to rule out.
Swap the cable, then the port. A cheap or crimped Ethernet run drops packets quietly, and a constant low floor on a wired connection is exactly its signature.
Drop the VPN. Riot is blunt about this: play without a VPN or proxy unless you have no choice.
What does not fix packet loss
Every page ranking for this question recommends at least one of these. None of them acts on a dropped packet.
- Switching DNS to 8.8.8.8 or 1.1.1.1. DNS resolves a name to an address, mostly once, at connect time. Your match is already running on a resolved session.
- Flushing the DNS cache. Aimed at a stale record. A stale record isn’t a lossy link.
- Port forwarding. It helps when a connection can’t form in the first place. You are in the match watching the number climb, so yours formed.
- Disabling IPv6. It changes which stack carries the traffic. Neither stack is inherently lossy.
- Paid reroute services. They shift your traffic around congested public routing, which is a real fix for a narrow case: loss that sits on the path to Riot and nowhere else. Step 2 is what tells you whether you are in that case. If your browser test also drops packets, the loss is happening before any of their servers can help.
Network Buffering is a trade, not a repair
Valorant’s Network Buffering control is the one game-side setting that touches this, and it’s widely sold as the fix. It isn’t. It holds arriving updates a little longer before rendering them, so a small gap in the stream gets covered instead of surfacing as a stutter.
Minimum keeps that buffer at a single tick, 7.8125 ms, which is what 128 updates a second works out to. Moderate and Maximum hold more frames before drawing them; Riot doesn’t publish the exact figures for those two.
What you buy is smoothness. What you pay is freshness: every enemy position you see is slightly older. On a clean connection Minimum is correct and anything above it is pure cost. When your loss is genuine, constant and outside your control, raising the setting makes matches less jarring while you chase the cause. It never removes a single lost packet.
When it stops being yours to fix
If loss survives a cable, an idle line and a rebooted modem, stop changing settings. You’re past the part you own.
Run a tracert to your game server so you have the hop where the path degrades, and follow Riot’s Gathering Logs guide before you open a ticket. Attach your browser test result too. That one is the piece Riot can’t collect. It shows whether your line drops packets on a route that has nothing to do with Riot, and that answer decides everything: a routing problem they can fix, or an ISP problem they can’t.
It also changes the ISP conversation. “My game lags” gets a script. A measured loss percentage on a wired, idle connection gets a technician.