Valorant Packet Loss Is Rarer Than You Think (Because of Riot Direct)

Valorant has an unusual relationship with packet loss compared to most competitive shooters, because Riot Games operates its own private backbone (Riot Direct) that carries game traffic on their infrastructure rather than through the general internet. This is not a marketing claim; it's a real network operated with peering into most major ISPs in most regions where Valorant runs. What it means practically is that the failure modes people expect from a live shooter, packet loss on long-haul routes, ISP peering congestion, jitter from transit providers, are less common in Valorant than they are in games without dedicated backbone infrastructure.

Which makes Valorant packet loss weirdly diagnostic. If you're experiencing what looks like packet loss in Valorant, the odds are higher than in other shooters that the cause is on your side of the network, not out on the internet somewhere.

Before anything else, a useful thing to know: Valorant's in-client network graph (turn it on in Settings > Video > Stats) shows packet loss as a percentage and updates in real time. If you enable it and watch during play, you'll immediately see whether loss is actually happening or whether the game just feels off for another reason. Most players who assume they have packet loss are actually seeing frame drops or high ping variance, both of which look identical from the player's perspective.

Real packet loss cases in Valorant, in decreasing order of frequency

Wi-Fi loss inside your own house. By far the most common. Valorant's tick rate is 128 Hz and it depends on each packet arriving on time. A Wi-Fi network that drops 1% of packets, which most household Wi-Fi does at some point during any given evening, produces exactly the symptoms of a competitive-tier packet loss issue. Ethernet fixes this in ten seconds. If you can't run Ethernet, moving to 5 GHz Wi-Fi with the router in the same room as your PC is the next best thing.

Router NAT saturation. Older or budget routers get overwhelmed if many devices are active on the network. The router runs out of NAT session slots and starts dropping packets, including yours. If your household streams a lot on multiple devices while you play, this is worth ruling out. Rebooting the router clears the NAT table and buys time; upgrading the router fixes it properly.

Bad Ethernet cable. Genuinely happens. Cheap cables and old cables both quietly degrade. If you're wired and still seeing loss, try a different cable before assuming anything else. This is a five-minute fix that solves cases that no amount of software tweaking would touch.

Your ISP's last-mile equipment. Occasionally the cable modem or fiber ONT in your house is the source, especially older units. Loss that appears only at specific times of day, or that appears in every online game you play at the same time, points at this. ISPs will replace equipment on request but often only after some pushback.

ISP peering issues to Riot Direct. Rare because Riot has done a lot of work here, but not impossible. This shows up as loss that starts abruptly, lasts hours, and coincides with reports from other players on your ISP. Usually resolves itself within a day.

What's almost never the cause in Valorant specifically

A congested transit route across the internet. Riot Direct exists specifically to avoid this. If your ISP peers with Riot at all, your traffic is likely on their backbone by the second or third hop.

Server-side packet loss from Riot's datacenters. The infrastructure is engineered to a high standard and loss inside a Riot datacenter is rare enough that you can safely rule it out unless there's a public status update saying otherwise.

A VPN making things better. Adding a hop and moving your traffic off Riot Direct and back onto the general internet is almost always worse for Valorant. The rare exception is if your ISP has no peering with Riot at all in your region, in which case a good route to a datacenter that does peer with Riot could help. This is a small edge case.

What actually helps if the local checks don't fix it

If you've verified the local network (wired, cable known good, router recent) and Valorant's in-client graph still shows loss, the next check is your ISP's route. A route optimizer engineered for game traffic can help in the specific case where your ISP's default path to Riot's edge is slow or lossy. GearUP handles Valorant, and it works by finding a cleaner route into Riot's network rather than tunneling all your traffic through a random server. If the problem was a bad initial hop from your ISP, this closes it. If your problem is actually Wi-Fi in your house, no routing tool will help until you fix Wi-Fi.

A note on tickrate confusion. Valorant runs 128-tick servers, but that doesn't mean your ping is measured 128 times per second in a way that affects perception. What it means is that the server processes 128 updates per second, so any packet you lose costs 8 ms of accurate world state. Compared to a 20-tick game where losing a packet costs 50 ms, 128-tick is much more forgiving of low levels of loss and much more visible when loss is higher. This is why a 1% loss rate that feels invisible in a casual game feels devastating in Valorant.

The short version: check your Wi-Fi first, check your cable second, look at the in-client graph before believing you have loss, and treat the rest of the internet as unlikely-but-possible rather than the default suspect.