FACEIT ping test: check CS2 latency before you queue

Before the match, connect the Windows PC to the router over Ethernet. Pause Steam downloads, cloud backups, streams and large uploads elsewhere on the home network. Turn on ping and network-quality telemetry in CS2. Do not change settings once the measurement begins; record the normal state first.

Review your FACEIT server preferences, but do not rely on the preference alone. FACEIT does not guarantee that matchmaking will always land only on your selected locations. Record the actual server location shown in the match room, the start time and the connection address when it is available.

Do not compare the lowest numbers from two random matches. The same server location, a similar hour, the same PC and the same connection type make the result useful. Those controls let you separate Wi-Fi, household traffic, the server and the route.

Watch at least five minutes of ordinary play. Record the usual ping range, the largest repeated spikes and any network-degradation or packet-loss warning in CS2. A screenshot that includes the scoreboard and telemetry is better evidence than the single lowest number you remember after the match.

Average ping is not the whole result. A connection that stays near 45 ms can feel steadier than one that swings repeatedly between 30 and 90 ms. Packet loss can also disrupt movement and commands while the ping figure still looks low.

Repeat the test on the same location at a similar hour. If you are comparing the normal route with another route, change only the route. Keep the PC, Ethernet connection, server location and household traffic as similar as possible.

Ask whether other players see the problem at the same moment. FACEIT's official guidance separates high ping or loss affecting one player from a server-wide problem. When everyone is affected, the team captain can contact live support through the Match Page and ask for a new server configuration.

When only you are affected, return to the wired, idle-connection test. A problem that disappears over Ethernet points toward Wi-Fi. Spikes that happen only while someone uploads or streams point toward congestion at home. A stable problem limited to one FACEIT location makes the external route or that data centre more plausible.

You can also compare official CS2 matchmaking on the same day and at a similar hour. If official matchmaking is normal but FACEIT is high, check the data-centre locations first. The difference may be the destination or the path to it rather than your PC.

For high ping or loss affecting one player, FACEIT directs players to its server provider's Hiperz latency test. Open the link from FACEIT's official CS2 server lag article, select the relevant region and run the test while the problem is reproducible.

Run it once over Ethernet with the connection idle, then repeat during the hour when the problem normally appears. Keep the match-room link, date, time and server location with the result. That evidence helps support understand which path to investigate.

A Hiperz test does not recreate the exact match by itself. Do not paste random FACEIT server addresses into public tools or post connection details publicly. Send diagnostic results only through the support path requested by FACEIT or its server provider.

If you have a known public game-server address, ZeroLag's free ping test sends ICMP from each Istanbul exit to the target and adds your browser's time to those exits. That gives a rough indication for a possible route. It does not reproduce your FACEIT match or promise lower ping.

Browsers cannot send ICMP directly, so the first leg is measured over HTTPS and can read a few milliseconds higher than the desktop app. Use CS2 telemetry, the Hiperz test or a longer desktop measurement for jitter and real packet loss.

Some servers disable ping replies. An unanswered test does not mean the server is offline or the connection is bad. In that case, the in-match telemetry and official support test remain the useful evidence.

If the problem survives Ethernet, an idle connection and the correct server-location checks, and it repeats on the same destination, the normal route may be the limit. Measure the normal and alternate paths in the same session. Compare the usual ping range, repeated spikes and loss rather than choosing whichever run contains the lowest number.

ZeroLag's current scope is Windows, Counter-Strike 2 and the Istanbul exit. It cannot repair Wi-Fi, remove geographic distance or fix a bad FACEIT server. If the alternate route does not produce a repeatable improvement on your connection, do not use it and do not pay for it.