blamethelagValorant Ping Test
Measure your real latency to Valorant servers — then find out if it was lag, or you.
Region auto-picked from your location — tap another region to compare.
How this works: game servers don't answer web pings, so this times your browser's round trip to the game's regional entry point in the same city — the same network distance your game traffic covers. Warm-up first, then 4 samples, median shown.
What ping is normal for — Valorant
| Rating | Ping | How it feels |
|---|---|---|
| Excellent | 0–25 ms | Riot-grade. Flicks and counter-strafes land exactly when you click. |
| Playable | 25–55 ms | Totally fine for ranked. You will not lose a duel because of this. |
| Noticeable | 55–100 ms | Peeker's advantage starts swinging fights. Wide swings feel unfair. |
| Unplayable | 100+ ms | You are playing in the past. Fix the connection before you queue. |
Valorant runs on 128-tick servers — double the classic 64 — which is why small ping differences feel so sharp: the server samples the world 128 times a second, so a late packet is a genuinely late action, not a rounding error. Riot also routes most matches through its own Riot Direct network, so two players in the same city can see very different in-game pings on different ISPs.
Lagging? Work through this list
- Go wired — Wi-Fi adds 3–15 ms of jitter even on a good router. An ethernet cable is the biggest Valorant upgrade that isn't a new monitor.
- Pick your server in the lobby — On the Play screen, open the server list on the lobby card and lock the lowest-ping shard instead of letting the game guess.
- Kill background downloads — Riot Client patches, Steam and cloud sync all share your line. Pause them before ranked — one update can add 40 ms.
- Turn on the in-game network stats — Settings → Video → Stats → Network Round Trip Time: set it to Text Only so a spike is visible the moment it happens, not after the round.
- Use router QoS / SQM — If anyone else streams or downloads at home, enable QoS and prioritise your PC. Bufferbloat, not raw speed, causes most evening spikes.
- Restart the router weekly — Cheap ISP routers bloat their buffers over days of uptime. A reboot before a session quietly fixes mystery lag.
Frequently asked questions
What ping is normal for Valorant?
Most players on their home shard sit between 10 and 45 ms. Under 25 ms is excellent, under 55 ms won't cost you fights, and anything over 100 ms is a real handicap in a 128-tick game.
Why is my in-game ping different from this test?
This test measures your browser's round trip to Valorant's regional entry point. In game, you connect to a specific match shard through Riot Direct, and the number also includes server processing. Treat this as your baseline: if this is high, in-game will not magically be low.
Does packet loss matter more than ping?
Often, yes. 40 ms with 2% loss feels worse than a stable 70 ms: lost packets mean shots and movement updates arrive in bursts, which is exactly what rubber-banding is. The in-game stats panel shows loss right next to ping.
How do I show ping in Valorant?
Settings → Video → Stats → Network Round Trip Time → Text Only (or Graph + Text). It appears in every match, no third-party tools needed.
Is 60 ping playable in Valorant?
Playable, yes — plenty of high-rank players live at 50–70 ms. But you will feel it on jiggle peeks and AWP duels. At 60+ ms, play for trades and pre-aimed angles instead of dry peeking.