Ping Test – measure ping, jitter and packet loss online

Ping (also called latency or response time) is the time in milliseconds it takes a small data packet to travel from your device to a server and back. This ping test sends requests from your browser to one test endpoint per location and shows the ping, minimum and maximum, jitter, and estimated packet loss for each location. If the table shows 12 ms for FFM/Eygelshoven, for example, a round trip to that location typically takes 12 milliseconds (the median of all measurements).

Under 30 ms is considered excellent, under 60 ms good, and under 100 ms playable. At 100 ms or more, you'll notice delays in fast-paced games; at 150 ms or more, interruptions and rubberbanding are likely. So 14 ms is excellent, 30 ms good, 70 ms playable, and 100 ms noticeably delayed. Sensitivity depends on the genre: competitive shooters like CS2 need low ping, while survival and building games like Minecraft, Rust or Valheim are much more forgiving.

Jitter is the average variation in ping from one measurement to the next. A location with 25 ms ping and 2 ms jitter feels consistent; one with 25 ms ping and 40 ms jitter stutters despite its low ping. The tool therefore marks a location as unstable at 30 ms jitter or 10% packet loss. Ping varies between tests because of network load, your Wi-Fi and the time of day – results are often worse during the evening peak. On the “Accurate” setting, the test takes 20 measurements per location, and the median filters out isolated outliers.

Packet loss means data packets are lost in transit. In games, this shows up as stuttering, characters jumping around (rubberbanding), or hits not registering. A browser can't send ICMP packets, so the test counts requests that receive no response within 2.5 seconds. This is an estimate of connection instability, not an exact packet loss rate. For a more accurate measurement, run a longer command-line test such as ping -n 100 <IP address> on Windows, ping -c 100 <IP address> on macOS/Linux, or mtr.

The command line measures using ICMP; the browser uses HTTPS requests. The browser also adds a little processing overhead, so the values here are usually 1 to 5 ms higher. The first request to each location is discarded because it includes connection setup (DNS, TCP, TLS); counted measurements use an existing connection. The browser result is therefore just as useful for comparing locations. To check an individual server, use ping <address> on the command line.

The one with the lowest stable ping for most of your fellow players. Run the test yourself and ask them to run it too – you can send them your results with “Copy result”. If everyone lives in the same region, choose the location with the best result. If players are spread out, choose a location where even the player with the highest ping stays below about 100 ms. The tool recommends the location with the lowest ping but excludes locations with 20% packet loss or more. If other locations are no more than 15 ms slower, it shows you up to 2 of them as nearly as fast alternatives.

To lower your ping, choosing a closer location usually helps most. Also, use an Ethernet cable instead of Wi-Fi, stop background downloads, streams, and cloud backups, turn off your VPN, and restart your router. Then test again using the “Accurate” setting to account for fluctuations. If ping to a location remains high, distance or your provider's routing is usually the cause—choosing another location is the only solution.

Yes, the ping test is free and requires no account. You don't need a download or an app; the test runs in your browser, including on smartphones, though Wi-Fi or mobile data can affect the result. Each measurement sends a tiny request to the test endpoint, with no more than 168 requests in total on the “Accurate” setting. Your results are processed in your browser; we don't store them. Like any web server, the test endpoints can see your IP address in their access logs.