Why is Counter-Strike 2 Lagging?

CS:GO's net_graph is gone. CS2 replaced it with the Telemetry HUD, in Settings under Game: switch on ping, packet loss, jitter and server tick and they appear at the edge of the screen during a match, colouring themselves once they pass a threshold you set.

Two of those numbers are worth separating, because they are routinely confused. Packet loss is data that left one end and never reached the other - your line, your router, or the path in between. Choke, the figure CS:GO players still look for, is the server deciding not to send you an update because it has hit its own bandwidth limit for you. The first is yours to fix; the second is not, and no amount of router configuration will change it.

The Telemetry HUD has one structural limitation, and it is the reason this page exists: it only runs while you are in a match, so it cannot tell you whether the connection was already dropping packets before you queued, and it keeps no history you can show anybody afterwards. The chart above runs outside the game, keeps the whole minute, and exports as a PNG or CSV. Run both - if the game's telemetry and this test disagree, the difference is the route to that particular relay, which the server picker lets you test directly.

Counter-Strike 2 kept the 64 tick server loop that CS:GO had and added a timestamp to the inputs travelling into it. Before, an action was filed under the tick it arrived in, so two players clicking 15 ms apart could be resolved as though they had clicked together. Now the packet carries the microsecond and the server orders the two shots correctly. That is a real improvement, and it is a narrow one: it fixes the rounding of information that arrived.

A lost packet carries no timestamp, because it is not there. The server does not learn that a shot was fired, has nothing to place, and simply continues from the last state it received from you. This is why players who bought a faster monitor and a lighter mouse still report shots that do nothing - the precision at both ends of the connection improved and the hole in the middle did not.

The 64 packets per second in each direction are small, around 250 bytes with headers, which is why CS2 runs happily on connections that struggle with a video call. Volume was never the problem. The problem is that at 64 Hz a single packet is 15.6 ms of your view of the match, and two consecutive drops put you 31 ms behind a duel that is decided inside a tenth of a second.

There is a second path worth separating out. Competitive matches do not run to one address: Valve routes match traffic through its own relay network, so what your provider actually carries is the leg between you and the nearest entry point. A connection that behaves against one location and falls apart against another is telling you about that leg, not about your router - and the server picker above exists so you can see the difference instead of guessing at it.