blamethelagCS2 Ping Test
Measure your real latency to CS2 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 — Counter-Strike 2
| Rating | Ping | How it feels |
|---|---|---|
| Excellent | 0–20 ms | LAN-adjacent. Your AWP flicks are limited by you, not the wire. |
| Playable | 20–45 ms | Standard ranked territory. Sub-tick keeps duels honest here. |
| Noticeable | 45–90 ms | Counter-strafing and jiggle peeks start to feel muddy. |
| Unplayable | 90+ ms | Every peek is a coin flip you already lost. Fix it first. |
CS2 replaced the old tick debate with a sub-tick system: your actions are timestamped between ticks and the server reconstructs exactly when you clicked. That makes ping feel different, not irrelevant — at high latency your shots still leave late. And because matches route through Steam Datagram Relay, your path to a Valve server can be longer than your path to the same city: two teammates in one town can legitimately have pings 30 ms apart.
Lagging? Work through this list
- Cap your matchmaking ping — Settings → Game → Max acceptable matchmaking ping: set it to 50–60 so the game stops volunteering you for far-away servers.
- Turn on the telemetry HUD — Settings → Game → Telemetry → Show Ping: Yes. CS2 replaced net_graph with this built-in readout — ping, fps and frame time in the corner.
- Pause Steam downloads — Steam happily saturates your line mid-match. Settings → Downloads: pause everything, or cap it hard, before you queue.
- Go wired — CS2 duels are decided in 20 ms windows. Wi-Fi jitter eats exactly those windows.
- Mind the relay route — Valve routes matches through Steam Datagram Relay. Occasionally a different network path reaches the relay more cleanly — test, and keep whichever measures lower.
- Use QoS at home — One housemate's 4K stream is your +40 ms. Prioritise your PC in the router and the spikes stop.
Frequently asked questions
What ping is normal for CS2?
On your home region, 10–40 ms is typical. Under 20 ms is excellent, under 45 ms is fully competitive, and past 90 ms counter-strafing and peeking degrade hard.
Why does my CS2 ping differ from this test?
This test times your browser to a regional entry point. CS2 matches run behind Steam Datagram Relay, which may route you through a relay in another city, and the scoreboard ping includes that whole path. Use this number as your floor.
Does sub-tick make ping not matter?
No. Sub-tick makes the server respect when you clicked, but your click still has to travel. At 80 ms, you see the enemy later and they see you later — sub-tick removes the rounding, not the distance.
How do I show ping in CS2?
Settings → Game → Telemetry → Show Ping: Yes. The old net_graph is gone; the telemetry HUD is its official replacement.
What does packet loss do in CS2?
Loss shows up as enemies micro-teleporting and shots feeling eaten. Even 1–2% is noticeable in a game this precise — and if it's constant, it's usually Wi-Fi or a struggling router, not Valve.