What Is a Good Ping for Gaming?

What is a good ping for gaming? A stable round-trip ping under 50 ms is a strong target; under 20 ms feels especially responsive, while under 100 ms is playable for many games. The game server's location, jitter and packet loss matter as much as the headline number.

What is a good ping for gaming?

Ping is the round-trip time between your device and a destination, measured in milliseconds. The bands below are practical rules of thumb, not requirements enforced by every game. Xfinity's current gaming guidance places 20–40 ms in the ideal range, under 100 ms in the playable range, and above 100 ms in the noticeable-delay range; latency is path-dependent, so the destination matters.

A slightly higher but stable result can be more enjoyable than a lower result that repeatedly jumps. A turn-based or slower game may also tolerate delay that would be frustrating in a competitive match. Judge the number against the game, the server region and the consistency you see while playing.

Ping is not the same as internet speed

Download and upload speed describe capacity: how much data can move at once. Ping describes responsiveness: how long a round trip takes. The ICMP Echo Request and Echo Reply defined by RFC 792 are the basis of the familiar command-line ping test. A large plan can still have high latency when the server is far away, the route is congested or Wi-Fi is unstable.

More Mbps helps downloads, updates, streaming and busy households; it does not move a distant server closer. For live play, check latency and consistency first, then use speed results to find capacity problems.

Measure the path you actually play

Start with Loqmi's browser speed test as a baseline, not a game-server guarantee. The game may use a different city, provider or continent. If it has a network overlay, its in-match ping is more relevant for that session.

1. Pause game downloads, cloud backups, video streams and other large transfers.
2. Run Loqmi's test and record ping, download, upload, jitter and packet loss when those metrics are shown. Cloudflare's AIM guidance evaluates these together because a single latency value can hide an unstable connection.
3. Repeat over Ethernet and from the normal Wi-Fi position, both during a quiet period and when matches feel worst.
4. Compare the baseline with the number shown inside the game. A low Loqmi result and a high in-game result usually means the destinations or routes differ, not that either test is automatically broken.

Check ping on each device

Windows 11

Confirm the connection under Start > Settings > Network & internet > Wi-Fi or Ethernet, the current Windows 11 path documented by Microsoft Support. Open Terminal from Start and run ping /n COUNT GAME_HOST; replace COUNT with the number of requests you want. The summary shows round-trip times and lost replies.

Worked example: Microsoft's documented sample returns 101 ms, 100 ms, 120 ms and 120 ms. The arithmetic mean is 110.25 ms, so that sample sits above the “usually playable” band in the table. It illustrates the calculation, not a promise that your game uses that host.

macOS and Linux

On macOS, check the interface at Apple menu > System Settings > Network, then run ping -c COUNT GAME_HOST in Terminal. On Linux, use the same command; the iputils ping manual documents -c as the count option. Replace COUNT and GAME_HOST. A public host is only a comparison, not the game server.

Android and iOS

Mobile systems vary, so use the browser test for a comparable result. On stock Android, check Settings > Network & internet > Internet; vendor labels vary. On iPhone, use Settings > Wi-Fi > Info beside the connected network. Run Loqmi where you play, then repeat near the router if the result is poor.

Read ping, jitter and packet loss together

Latency answers “how long?” Jitter answers “how much does that delay vary?” Packet loss answers “did the update arrive?” Cloudflare's model also includes loaded latency, showing whether delay grows when the connection is busy. Together, these metrics explain rubber-banding on a fast plan.

Do not treat one intermediate router in a traceroute as proof of the fault: diagnostic packets can be deprioritized. Repeated end-to-end results to the actual destination are stronger evidence.

Fix high ping in the right order

1. Use Ethernet for the gaming device. It removes most wireless variability. If a cable is impossible, move the device nearer the router and compare the available Wi-Fi bands; see Loqmi's slow Wi-Fi guide and 2.4 GHz versus 5 GHz.
2. Stop competing traffic. Pause patches, cloud sync, live video and large uploads. If ping improves immediately, the issue is congestion or queueing, not necessarily a weak ISP plan.
3. Choose the nearest practical game region. Physical distance and routing add delay. A VPN is not a default fix; it can add another hop. Test it only as a comparison for a specific route.
4. Check the busy-time pattern. Compare a wired test when the network is quiet with one during the problem. If the wired result is poor everywhere, keep the timestamps and results for the ISP; if only one game is affected, report the destination-specific issue to that game's support team.

Diagnose before you upgrade

Upgrade for a capacity problem: slow downloads, several simultaneous streams, or latency that rises only when the connection is saturated. An upgrade alone cannot repair a faraway server, a bad route, wireless interference or packet loss. For the household-side calculation, use Loqmi's guide to choosing internet speed.