# CS2 lagging with good ping: network, packet loss or your PC? > Ping only measures the round trip to the server. Lag with good ping is usually packet loss, jitter (packets arriving late) or your PC’s frame time. Turn on CS2’s network telemetry: if missed ticks climb when the lag hits, it’s the network; if frame time climbs, it’s your PC. Canonical: https://risefps.com.br/en/guides/cs2/lagging-good-ping Last updated: 2026-11-12 Low ping tells you the route to the server is fast. It doesn’t tell you whether packets arrive whole and on time. ## First, find out what is holding you back **Symptom, likely cause and what to do** | Symptom | Likely cause | What to do | | --- | --- | --- | | Enemies teleport or you get pulled back | Ticks missed due to packet loss or jitter [1] | Turn on "Show network problems" and see which arrow climbs [1] | | High down arrow in the telemetry | Server data arriving late or getting lost on the way to you [1] | Test with a cable and pause downloads | | High up arrow in the telemetry | Your commands don’t reach the server in time [1] | Cut background uploads and check your FPS [5] | | [Stutter with a clean network in the telemetry](https://risefps.com.br/en/guides/cs2/stutter-high-fps) | Your PC’s frame time, not the network [1] | See the CS2 stuttering with high FPS guide | | High ping in every match | A match on a server far from you [1] | Lower "Max Acceptable Matchmaking Ping" [1] | ## Why low ping doesn’t mean a good connection Ping measures the round trip to the server. It doesn’t show lost packets or jitter, which is packets arriving late or bunched up with others. For games, a late packet is usually just as bad as a lost one. Valve itself says a network test that only measures packet loss is incomplete. CS2 runs at 64 ticks per second. When the data for a tick doesn’t arrive in time, the game misses that tick, and that’s what you feel as lag. ## How to turn on CS2 network telemetry 1. Open CS2’s settings and go to "Game" › "Telemetry". 2. Under "Show network problems (ticks missed due to loss / jitter)", pick "Always". 3. Turn on "Use the detailed network quality display" to see loss and jitter as numbers. 4. To see it packet by packet, turn on "Show network jitter / misdelivery graph". The up arrow shows what goes from your PC to the server. The down arrow shows what comes from the server to you. Since November 2024, this number only counts what actually hurts gameplay. Zero missed ticks with some loss in the detailed view means the game covered the gap. It doesn’t mean your network is perfect. ## What to do when the network is the problem - Play a match on a cable. If the missed ticks go away, Wi-Fi is the cause. - Pause downloads, updates and cloud uploads during the match. They compete for the same connection. - If jitter comes in rare spikes or you have packet loss, raise "Buffering to smooth over packet loss / jitter" in "Game". It hides both problems, but adds delay. - If your ping is high in every match, lower "Max Acceptable Matchmaking Ping". Matchmaking then picks only from the data centers with lower ping. > **CS:GO network scripts make lag worse** > - In February 2024, Valve locked cl_interp because scripts with high values caused rubber-banding. > - To smooth over loss and jitter, only use "Buffering to smooth over packet loss / jitter" in the game menu. ## Where the loss starts: pathping pathping, built into Windows, shows packet loss at each hop to a destination. Run it in Command Prompt with a website address and wait for the result. If the loss already shows up at the first hop, which is your router, the problem is at home. Loss at a single router along the way, with no loss at the hops after it, doesn’t affect the traffic passing through it. ## When the lag is your PC If the network is clean in the telemetry and frame time climbs when the stutter hits, the problem is your PC. CS2’s release notes mention commands that don’t reach the server in time due to packet loss or to frame rate problems on the player’s PC. Unstable FPS shows up as lag too. ## What Rise does in CS2 Everything here shows what changes before you apply it. - **Windows, graphics card and network.** What matters in any game: power plan, background programs and your PC’s Windows, graphics card and network settings. Each optimization shows what changes before you apply it. (Optimizations · Rise Basic and Premium) - **Before-and-after Benchmark.** Runs the same Rise 3D scene before and after your tweaks and compares average FPS, 1% low and stutters on your PC. It helps you tell FPS problems apart from network problems. (Benchmark · Rise Basic and Premium) ## What Rise does not do in CS2 - Doesn’t improve your internet’s route to the server. - Doesn’t touch VAC and doesn’t inject anything into CS2. - Doesn’t promise an FPS number: measure before and after on your PC. ## Frequently asked questions ### Why does CS2 lag with good ping? Because ping doesn’t show packet loss or jitter. Turn on "Show network problems" in CS2’s telemetry. If missed ticks climb when the lag hits, it’s the network. If frame time climbs, it’s your PC. ### What is jitter in CS2? It’s the variation in when packets arrive: a packet shows up late or bunched up with others. For games, a late packet is usually just as bad as a lost one. ### What do the arrows in CS2’s network telemetry mean? The up arrow shows your commands that didn’t reach the server in time. The down arrow shows server data that didn’t reach your PC in time. ### Is it worth raising the buffering in CS2? It is when you have packet loss or jitter in rare spikes. "Buffering to smooth over packet loss / jitter" hides those problems, but adds delay. With a clean network, you don’t need it. ### Cable or Wi-Fi for CS2? Test both with the telemetry on. If the missed ticks go away on a cable, Wi-Fi is the cause. ### Does Rise lower my CS2 ping? No. Rise tunes your PC’s network settings, but doesn’t improve your internet’s route to the server. High ping from a distant server is fixed with "Max Acceptable Matchmaking Ping" or with your connection’s route. ## Sources 1. [Steam Support: CS2 telemetry (Source2 Telemetry HUD)](https://help.steampowered.com/faqs/view/5E6F-5B36-5485-F6B9) (checked on 2026-11-03) 2. [Valve: CS2 update from November 12, 2024 (network quality)](https://steamcommunity.com/games/CSGO/announcements/detail/4472731215261073716) (checked on 2026-11-03) 3. [Valve: CS2 release notes for February 6, 2024 (buffering)](https://steamcommunity.com/games/CSGO/announcements/detail/4064004264605234736) (checked on 2026-11-03) 4. [Valve: CS2 release notes for February 7, 2024 (cl_interp)](https://steamcommunity.com/games/CSGO/announcements/detail/4064004735507957800) (checked on 2026-11-03) 5. [Valve: CS2 release notes for February 28, 2024 (late commands)](https://steamcommunity.com/games/CSGO/announcements/detail/4124805233776026715) (checked on 2026-11-03) 6. [Microsoft: pathping command](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/pathping) (checked on 2026-11-03) _Guide written by the Rise team. The steps work with or without Rise; the facts about the game come from the sources at the end of the page, with the date we checked them._ ## Related - [CS2 low FPS, stuttering or input lag: how to fix it](https://risefps.com.br/en/guides/cs2/how-to-increase-fps) - [CS2 stuttering with high FPS or on a high-end PC: how to fix it](https://risefps.com.br/en/guides/cs2/stutter-high-fps) - [CS2 FPS capped at 60 or at your monitor’s refresh rate: how to uncap it](https://risefps.com.br/en/guides/cs2/fps-capped-fps-max) - [CS2 FPS commands and launch options: what works and what’s a myth](https://risefps.com.br/en/guides/cs2/fps-commands-launch-options) - [CS2 stuttering with high FPS or on a high-end PC](https://risefps.com.br/en/guides/cs2/stutter-high-fps) - [CS2 FPS commands and launch options: what still works](https://risefps.com.br/en/guides/cs2/fps-commands-launch-options) - [CS2 low FPS, stuttering or input lag](https://risefps.com.br/en/guides/cs2/how-to-increase-fps) - [See the plans](https://risefps.com.br/en#planos)