CS2 ping test — catch the spikes the scoreboard hides

CS2 shows your ping on the scoreboard, but only as a right-now number — not the spike that hit as you swung the angle. CS2 is surprisingly tolerant of a high-but-steady ping (sub-tick helps), and up to about 120 ms is playable — what kills you is variance: spikes, jitter and loss. The 25-second test below measures exactly those.

What your numbers mean for CS2

CS2’s sub-tick architecture means the server timestamps your actions instead of sampling them, which softens steady ping — but no netcode absorbs a 300 ms spike or lost packets. Up to ~120 ms is playable for matchmaking; under 60 ms is where it feels crisp; under 40 ms is faceit-tryhard territory.

One more thing averages hide: a single spike over 300 ms or 1% packet loss will cost you rounds no matter how low the average sits. That’s why the test above counts spikes and loss separately — a connection can be “fine on average” and still throw the fight.

Fixes that actually work for CS2

1. Cap matchmaking ping. Open the console and set mm_dedicated_search_maxping 50 (or whatever your ceiling is). It stops Valve from placing you on a far server when your region’s queues are thin — the single most effective CS2 ping fix that isn’t hardware.
2. Know that Valve routes through relays. Official servers are reached through Valve’s relay network (SDR), and the chosen relay isn’t always the shortest path. If your ping jumped one day and never came back, your ISP’s route to the relay probably changed — A/B test a gaming VPN to see if a different path is shorter, and use the result as evidence with your ISP.
3. Use the server browser for casual. Community servers show live ping in the browser — sort by ping and favorite the ones that are consistently low for you.
4. Fix the spikes, not the average. A steady 70 ms beats 40 ms with spikes every round. If spikes show up in the test above, the usual suspects are Wi-Fi interference and bufferbloat — both fixable at home for free.

Frequently asked questions

What is a good ping for CS2?

Under 40 ms feels crisp, up to 60 ms is comfortable, and up to about 120 ms is playable thanks to sub-tick — as long as it’s steady. Variance matters more than the number: spikes over 300 ms and any packet loss cause the teleport-y deaths and shots that don’t register.

What does mm_dedicated_search_maxping do?

It caps the maximum ping Valve matchmaking will accept when placing you on official servers. Set it to the highest ping you consider playable — for example mm_dedicated_search_maxping 50 — so thin queues can’t dump you on a far-away server.

Why is my CS2 ping high when my internet is fast?

Speed is bandwidth; ping is distance and queueing. Common causes: Valve’s relay network routing you on a detour, your ISP changing its route to Valve’s backbone, Wi-Fi interference, or bufferbloat when the line is busy. None of these show up on a speed test.