Ping under 30: why HvH players are obsessed with low-latency servers

Ping doesn't feel important in matchmaking. Valve's prediction and lag compensation hide it well — you can hold an angle at 80ms and still trade most peeks. HvH is a different game. At 80ms, your anti-aim is broken and you cannot hit your shots. At 20ms, you're competitive. The gap is not subtle.

Why anti-aim cares about latency

Anti-aim works by lying to the server about which way the player is facing. The cheat picks a yaw the moment a shot is fired, sends a small bundle of network packets that confuse the hit-detection model, and resolves the player's hitbox to a position no one can shoot.

That trick depends on the server processing those packets in a tight time window. At 20ms RTT, the server sees the spoofed yaw and the actual shot in a single tick. At 80ms, the spoofed yaw arrives during a different tick than the rest of the player's update, and the server's hit detection ends up using whichever yaw was most recent — usually a real one. Anti-aim collapses, and the cheat user becomes a hitbox.

Worse: the resolver in the enemy's cheat — the part that figures out where you really are — runs at the enemy's local view of your packets. At 80ms ping, your packets are old by the time their resolver sees them. The resolver locks on to your last-known position, which is still close to your real one, and head-clicks you. You can't hide because your hide-state was computed against fresh server data and they're shooting against stale state.

The double-tap window

Double Tap (DT) — even on the few servers that still allow it — needs the cheat to fire two shots inside a single sub-tick window. That window is tiny in network terms. At low ping, both shots make it. At high ping, the second one arrives after the tick rolls over and registers as a normal delayed shot, which counts as zero advantage.

The same applies to backtrack: the cheat firing at a 200ms-old hitbox needs the server to still have that hitbox in its lag-comp ring buffer. The server's buffer holds about 1 second of state. If your ping is high enough that your shot arrives 700ms after you fired, you've eaten 70% of the buffer just on transit, and there's almost no backtrack window left.

What "low ping" means for HvH

The community converged on a rough rule: under 30ms is good, 30-50ms is workable, 50-80ms is rough but playable, anything over 80ms is hopeless. This is why HvH server hosting clusters in a small set of locations — Frankfurt for EU, Singapore or Hong Kong for Asia, Chicago or Dallas for NA — and why players will happily cross continents to bookmark a server in their region rather than play on a closer mixed-region one.

It's also why server directories show ping prominently and why the "EU" / "Asia" tags on servers actually matter. HvH players sort by ping first, then by slot count, then by ruleset.

How to actually measure your ping

The CS2 net_graph 1 console command shows latency and jitter per-server. The number that matters is the second one (var, jitter): a stable 50ms is far more useful than a spiky 30ms that fluctuates to 100ms.

For a server you're considering joining, you can also ping <server-ip> from your terminal to get the raw network latency, which is the floor your in-game ping will sit at.

If you're routinely above 60ms on every HvH server you can find, it's not the cheats — it's the route. Most HvH players in that situation either move ISPs, get a tunnel like ExitLag, or just accept the ceiling.