Download—Mbps
Cloudflare edge testPerformance, not guesswork
Counter-Strike 2 connection check.
Test your connection, then follow the game-specific fixes and settings below.
Jump to fixes, settings & platform help ↓DownloadUploadPingJitterLoss
Upload—Mbps
Ping—ms
Jitter—ms
Packet loss—%
Counter-Strike 2: fix lag, high ping and packet loss
Use CS2 telemetry to investigate jitter, missed updates and rubber-banding, and understand the latency cost of buffering.
Find out what is actually lagging
CS2's network-quality display and frame-time display describe different parts of the experience. A problem in packet delivery can resemble a machine-performance hitch. Keep both visible during diagnosis and note which changes when movement becomes inconsistent.
High ping or jitter
Actions arrive late, or delay fluctuates. Compare the in-game latency reading with your usual baseline.
Packet loss
Updates may be missing and movement can snap back. Look for a loss reading, not just a low average ping.
Low FPS or input delay
A choppy image or delayed controls can come from the device or display. Check an offline/local mode when available.
Settings worth checking in Counter-Strike 2
Menu names can change with patches, editions and platform. Use the controls available in your build; do not apply PC-only instructions to a console.
Telemetry HUD
Open Settings → Game and find the Telemetry options. Show network and frame-time information while troubleshooting.
What it does: Valve's Source 2 telemetry guide explains the displays; wording can change with updates.
Maximum acceptable matchmaking ping
In Settings → Game, reduce the maximum acceptable matchmaking ping to a realistic value for your location.
What it does: May narrow matchmaking options or increase waiting time; it cannot guarantee a perfect match.
Buffering to smooth over packet loss / jitter
Find this option under Settings → Game. Compare the lowest setting that improves your unstable connection.
What it does: Additional buffering can smooth interruptions but adds latency. Revert if it makes response worse.
PC troubleshooting, step by step
- Close Steam downloads and background uploads, then compare several matches on Ethernet. Keep the same matchmaking ping preference during the comparison.
- If telemetry shows frame-time spikes without a matching network problem, lower demanding video settings and compare a stable FPS limit. Avoid copying old CS:GO console-command bundles into CS2.
- Record the displayed network figures and the match time. Intermediate-router traceroute loss alone is not proof of game packet loss, because a router can deprioritise diagnostic replies while forwarding gameplay traffic.
Console support and fixes
- Counter-Strike 2 has no native PlayStation or Xbox version. There are no CS2 console-network or console in-game settings to apply.
- A controller connected to a PC still uses the PC version and its settings. Remote streaming introduces another connection and should be tested separately.
A controlled checklist for ping spikes and loss
- Record a baseline. Note your game mode, platform, time, connection type and the in-game reading. Run RaceMyNet outside a match. Keep two or three results rather than relying on one unusually good test.
- Remove local wireless uncertainty. Compare Ethernet directly to the main router where possible. A cable into a wireless mesh satellite may still use a wireless backhaul. If Ethernet is unavailable, compare close to the main router.
- Pause heavy traffic. Stop downloads, cloud backups and livestream uploads across the household for one comparison. If lag disappears only when traffic stops, investigate congestion and your router's supported queue-management options.
- Check the simple physical causes. Reseat Ethernet plugs, try a known-good cable or another router port, and restart network equipment once using its manufacturer's instructions. Do not factory-reset it as the first step.
- Change one thing and retest. Compare similar matches at your normal playing time. Keep improvements that repeat. A faster DNS service, a VPN or more Mbps is not a guaranteed reduction in game-server ping.
Prefer the game's own loss display for game traffic. If RaceMyNet reports an HTTPS fallback, request failures are not a direct measurement of the game's UDP packet loss.
If Counter-Strike 2 still has connection problems
- For a community server, compare another nearby server before blaming matchmaking. That server's host, plugins or load may be involved.
- If buffering helps, still investigate why packet delivery is uneven. Treat it as a mitigation, not a repair to Wi-Fi or ISP routing.
If several games and devices struggle on a wired connection, give your ISP the times, results and affected services. If only this game or mode is affected, start with the publisher's support and service information below. Include the platform, region, timestamps and a short clip of the indicators. Share diagnostic logs privately through official support.
Should everyone use the maximum buffering setting?
No. Start with the default and compare only if you have uneven network delivery. Choose the smallest change that helps; adding buffering to an already stable connection can introduce unnecessary delay.
Official guidance and further help
Menu instructions were checked against the publisher guidance below. General comparison steps are troubleshooting suggestions, not a promise of a particular ping or a guaranteed fix.
GAMING CONNECTION GUIDE
Use the test as a baseline. Verify the result in your game.
A browser test and a game match use different servers. Compare repeat measurements, in-game indicators and the same playing conditions before deciding whether a change helped.