How to lower your ping in CS2

There is no launch option, config line or console command that lowers your ping in Counter-Strike 2. Ping is decided by the path between your PC and Valve's servers. Here is what that path consists of, and the parts of it you can change.

What decides your ping in CS2

Two things: how far you are from the data centre your match runs in, and the route your traffic takes to get there.

CS2 matchmaking doesn't connect you straight to the game server. Your traffic enters Valve's own network at one of its relays (Steam Datagram Relay) and travels the rest of the way inside it. So the stretch that varies from player to player is the one between your provider and Valve's nearest relay. That stretch is where a bad evening route shows up.

See what you actually have

In CS2, open Settings → Game → Telemetry and set ping and packet loss to show. Play a match and watch whether the number is high and steady, or mostly fine with jumps. They are different problems:

• High and steady means distance or a detour.
• Jumps and loss mean something on the way is queueing or dropping. See what causes ping spikes.

The things that help, in order

1. Use a cable. Wi-Fi adds jitter and loss, which CS2 punishes harder than a few extra milliseconds. If a cable really isn't possible, this guide covers what improves Wi-Fi.
2. Stop everything else on the line. Steam downloads, cloud sync, a stream in the next room. A full connection makes game packets wait.
3. Set your matchmaking ping limit. Settings → Game → Max Acceptable Matchmaking Ping keeps you off distant data centres. Lower means closer servers and sometimes a longer queue.
4. Sort out the router, if others share it. A QoS or SQM setting stops one device's upload from stalling your game.
5. Change the route. If your ping to Valve is higher than your distance explains, or it gets worse every evening, the path your provider uses is the problem. You can't change that path, but your game traffic can take another one.

What doesn't help

• Launch options and "rate" commands. They don't change the network path, and CS2 ignores most of the old ones.
• A faster internet plan. CS2 uses very little bandwidth. A 1000 Mbit line has the same ping as a 50 Mbit line on the same network.
• A general VPN, usually. It moves all your traffic through one server chosen for privacy, not for the path to Valve. Gaming VPN or game routing explains the difference.

Where NoSpike fits

NoSpike is step 5. Valve publishes where its servers are, so NoSpike knows exactly which traffic is CS2's and routes only that. It measures your direct route and the route through each of its relays in Europe, to the data centre you pick or the one your match is on, and uses a relay only when it's faster. It checks again every minute, and it won't move your connection in the middle of a match unless the route you're on is failing.

If your provider already has a good path to Valve, there's nothing to gain, and the app says "Direct is fastest" instead of routing you for the sake of it.

FACEIT runs its own servers, separate from Valve's. NoSpike's FACEIT entry is still being mapped and is marked as a beta: it may not carry all of a match's traffic yet.