Valorant Ping Test

At 128 ticks per second, a Valorant server processes a new world state roughly every 7.8 milliseconds. That high refresh rate means the network delay between you and the server becomes the dominant source of lag — there is very little server-side buffering left to hide behind. If you hold an angle on 80 ms while the enemy swings you on 25 ms, peeker's advantage lets them see and shoot you a noticeable fraction of a second before you ever see them move.

Riot also operates its own backbone, Riot Direct, which peers with ISPs to shorten routes to its data centers. That helps, but it cannot beat geography: your physical distance to the data center still sets the floor for your ping.

Your Valorant account lives on a shard (EU, NA, AP, KR, BR, or LATAM), and inside each shard Riot spreads matches across multiple data centers — EU players, for example, bounce between Frankfurt, Paris, London, Stockholm, and Warsaw. In the in-game settings you can set preferred servers, and matchmaking weighs those preferences against queue times.

Run the test below and note your two or three fastest regions. Those are the geographies you should prefer in Valorant's server selection — deprioritizing everything else stops matchmaking from dropping you onto a 90 ms server at 3 a.m. just to fill a lobby.

Valorant's latency number can stay reassuringly low while packet loss disrupts a round. A missing movement update may make an opponent appear to skip into an angle, while a dropped outbound packet can delay a weapon switch or ability input. Unlike steady latency, loss tends to arrive in short bursts, so it produces isolated fights that feel inexplicably wrong rather than making every duel consistently sluggish. That distinction matters before changing data centers: a closer route is not automatically better if it drops traffic under load.

Enable Valorant's packet-loss graph and network round-trip-time graph for several matches, then separate persistent delay from brief transport failures. Loss that appears when another device starts uploading points toward the local network or ISP uplink; loss confined to one data center suggests the route beyond the home connection. Also check whether the loss is incoming or outgoing. Incoming loss disrupts the world state the client receives, while outgoing loss interferes with commands reaching the match. That direction can narrow the fault before changing router settings or involving the provider.