Treat sustained RTT, short jitter, raw packet loss, and frame-time spikes as separate problems. CS2's network-quality figure is not another ping value, and a community server is not a baseline for every official match.
Start with the symptom
- High ping throughout the match: compare the match value with several regional medians.
- Occasional warping at low ping: inspect raw jitter and loss.
- Stable network values with visual freezes: check FPS and frame time.
- Only one community server is slow: retest that same server instead of generalizing.
Compare the affected direction
Run the CS2 ping test during your normal play window. Median latency shows the regional order; P10–P90 shows short variation. PartyPing measures its own probes, not Valve or community servers, so it identifies the scope of a route problem rather than the exact match RTT.
Valve changed the network-quality calculation in November 2024. Read raw packet loss, raw jitter, and the affected-event metric separately. Old screenshots labelled “bad packets” may use a different definition.
Account for Steam routing and server type
If a connection uses Steam Datagram Relay, traffic may enter Valve's backbone through a relay and follow a different path from a browser test. PartyPing cannot identify the relay used by a match or reveal a hidden server IP.
Official matchmaking and community servers may use different locations, operators, and configurations. Record the server type, time, match ping, loss, jitter, and regional result before comparing.
Sources
- Valve: Counter-Strike 2 and sub-tick
- Valve: November 12, 2024 network-quality update
- Steam Datagram Relay documentation
Sources reviewed: 2026-09-16.