Game ping test

Ping is how long a packet takes to reach the server and come back, in milliseconds. Packet loss is the share of packets that never make it, which in game shows up as a rubber-band or a swallowed input. Jitter is how much the ping swings from packet to packet: a line that sits at 60 ms is more comfortable than one bouncing between 20 and 100.

We time small datagrams echoed by each PartyPing probe over WebTransport. WebTransport carries them over QUIC/UDP, which is closer to real-time game traffic than an ordinary page request, but it is not the same protocol or route as the game itself.

Each region gets dozens of packets, not one or two. That makes the test take a little longer, but one unlucky spike or dropped packet can no longer skew the result.

Probes sit in the same regions as the game servers, not on the same machines, and every game decides for itself what it folds into the number it prints — so the two land close rather than identical. Which region comes out ahead here is the part that carries over.

There is no single cutoff for every game or player. As a general guide, under 50 ms usually feels smooth in fast real-time games, 50–100 ms is often still playable, and input delay becomes easier to notice above 100 ms; packet loss, latency swings, and the in-game result still matter.

Network paths change by the minute, and evening peaks are visible in most home connections. A single test is one slice of your network, not a verdict on it. Test in the hours you actually play, and run it more than once before drawing a conclusion.

The two numbers stop at different doors: we time UDP datagrams from your browser to a probe in each region, while your client times its own traffic to the publisher's servers over its own routing, and every game decides what it folds into the figure it prints. What carries over is which region is fastest from where you sit, and whether your line is losing packets or swinging. The client's number is the exact latency of the match you are already in, which is the one thing a browser cannot measure for you.

Download speed measures how much data moves per second; game latency measures how long a small packet takes to make a round trip. High bandwidth does not prevent Wi-Fi interference, queues caused by background uploads, evening congestion, or an inefficient route from raising ping and packet loss.

Often yes, once you know which half of the problem you have. If every region got worse at once, it is local: switch to a cable, check what is uploading in the background, call your ISP. If only the distant regions are bad, the path or the distance is the problem and picking a closer region beats any tweak.

Ethernet is usually the most stable option when available. 5 GHz and 6 GHz Wi-Fi can also deliver low latency at short range with few obstructions, while mobile hotspots vary more with signal, tower load, and handoffs; compare each option against the same region at the same time instead of judging by connection type alone.

No. It can help only when its relay route is better than your ISP's original route; an extra hop can instead add latency or packet loss when the original route is already reasonable. Compare it on and off against the same server region and time window, using several runs and checking both latency range and packet loss.

Use "Test with your squad" to open a room and send the link around. Everyone measures the same regions from their own connection, and the ranking is decided by the worst player in the group rather than the average — the goal is a region everyone can play on.

No. The whole test runs in the browser with nothing to install and no account required. It only needs WebTransport over HTTPS, which current versions of major browsers support; an older browser may need to be updated.

Nothing is tied to you, because there is no account here. If sample collection is switched on, we keep one anonymous row: game, region, latency percentiles, packet loss, country and network provider (ISP). Your IP is dropped as soon as the country and provider are read, and no precise location, user id or cookie is stored.