CS2 lag: what causes it and how to fix it

"Lag" in Counter-Strike 2 is at least four different problems that feel alike: a high ping, a ping that jumps, packets that never arrive, and frames your PC can't draw in time. Each has its own fix, so the first job is telling them apart.

How CS2 connects you

A CS2 matchmaking game doesn't send your traffic straight to the game server. It enters Valve's own network at one of Valve's relays (Steam Datagram Relay) and travels the rest of the way inside it, to the data centre your match is in. In Europe those relay points sit in the big hubs: Frankfurt, Amsterdam, London, Paris, Stockholm, Vienna, Warsaw and Madrid.

So the part of the path that differs from one player to the next is the stretch between your provider and Valve's nearest relay. When CS2 lags for you and not for your friend in the same city, that stretch is usually why: your provider takes a longer or busier road to Valve than theirs.

CS2's servers also work differently from CS:GO's. With sub-tick updates, the server knows the moment within a tick when you clicked, so a shot is judged by when you fired, not by the next tick. That makes a steady connection matter more than ever. Late or missing packets are what break it.

See which kind of lag you have

Open Settings → Game → Telemetry and set ping, packet loss and frame time to show. Then play a match and watch them.

• Ping high but steady: distance, or a detour on the way to Valve. Everything feels a little late, all the time.
• Ping that jumps: something on the path is queueing. Usually your own line (an upload, a download, Wi-Fi), sometimes your provider in the evening. What causes ping spikes shows how to find which.
• Packet loss or misdelivery: data that arrives late or never. Shots that don't register, enemies that jump. One percent is already noticeable.
• Frame time spikes with a normal ping: that's your PC, not the network. A smooth connection can't fix a stutter in the drawing.

What helps

1. Play on a cable. Wi-Fi rarely adds much ping on average, but it adds jitter and loss, which CS2 punishes. Wi-Fi or Ethernet covers what to do when a cable isn't possible.
2. Keep the line quiet. A Steam download, cloud backups or a 4K stream in the next room make your game's packets wait their turn.
3. Limit how far matchmaking sends you. Settings → Game → Max Acceptable Matchmaking Ping keeps you off distant data centres, at the cost of a longer queue now and then.
4. Fix the router's queue if others share it: SQM or a well-set QoS stops someone's upload from stalling your round.
5. Change the route when the ping is higher than your distance explains, or rises every evening. That's your provider's path to Valve, and it's the one thing on this list you can't change from your settings.

A faster plan won't help: CS2 uses very little bandwidth. Neither will old "rate" commands and launch options. How to lower your ping in CS2 goes through those one by one.

Where NoSpike fits

NoSpike's CS2 entry is verified: Valve publishes where its servers are, so NoSpike knows exactly which traffic is CS2's and moves only that. It measures your own route and the route through each of its relays to the data centre you pick, or to the one your match is on once it starts, and uses a relay only when it's faster.

It checks again every minute and doesn't move you in the middle of a match unless the route you're on is failing. If your provider already has a good path to Valve, the app says so and leaves you on it: there's nothing to win by routing for its own sake.

FACEIT runs its own servers, separate from Valve's. What this page says about routing is for Valve's matchmaking.