A good ping for gaming is under 50 ms for fast-paced online shooters and under 100 ms for most other genres. Ping is only one third of the picture, though. Jitter (how much the ping swings) and packet loss (data that never arrives) usually decide whether a match feels smooth, and a steady 60 ms connection with zero loss will play better than a 25 ms connection that spikes every few seconds.
Quick answer: Our top pick in 2026 is the Competitive tactical shooters — our #1 rated choice. See the full ranked comparison, alternatives and buying advice below.
What Ping Actually Measures
Ping is the round-trip time, in milliseconds, for a small packet to travel from your PC to a server and back. It is not the full delay between pressing a key and seeing the result. That total, often called input-to-photon latency, also includes your mouse and keyboard polling, the time the game takes to render a frame, and the display’s own processing. At 60 fps one frame lasts about 16.7 ms, and at 144 fps it lasts about 6.9 ms, so a slow frame rate can add as much delay as a long network path.
The server adds its own slice as well. Online games update the world a fixed number of times per second, called the tick rate. A server that ticks 64 times per second sends a fresh state roughly every 15.6 ms, a 128-tick server about every 7.8 ms, and a 20 Hz server every 50 ms. Your displayed ping does not include that wait, which is why two games can both show 30 ms and still feel different.
Distance sets the floor. Light in optical fiber covers roughly 200 km per millisecond, so every 100 km of cable between you and the server costs about 1 ms of round-trip time at minimum. Real routes are longer than the map distance and pass through routers that each add a little, so a server 1,500 km away rarely shows less than 25 to 35 ms.
Good Ping by Game Type
These bands are rules of thumb drawn from how each genre handles player input. They are not official standards, and your own tolerance matters, but they are a useful starting point.
| Game type | Comfortable | Playable | Problem zone |
|---|---|---|---|
| Competitive tactical shooters | Under 30 ms | 30 to 60 ms | Above 80 ms |
| Battle royale and large-scale shooters | Under 50 ms | 50 to 80 ms | Above 100 ms |
| Fighting games (rollback netcode) | Under 40 ms | 40 to 80 ms | Above 100 ms, or any visible jitter |
| Racing and sports games | Under 50 ms | 50 to 100 ms | Above 120 ms |
| MOBAs and real-time strategy | Under 60 ms | 60 to 100 ms | Above 150 ms |
| MMOs and co-op PvE | Under 80 ms | 80 to 150 ms | Above 200 ms |
| Turn-based and card games | Under 150 ms | 150 to 300 ms | Mostly a timeout risk |
The reason shooters sit at the strict end is that hit registration and peeking advantages are decided in tens of milliseconds. Slower genres hide delay behind animation times and cooldowns, so a 100 ms delay on an ability is far less visible than the same delay on a flick shot.
Jitter: Why Steady Beats Low
Jitter is the variation between consecutive ping values. If your pings arrive as 30, 31, 29, 30 ms, jitter is tiny. If they arrive as 30, 90, 28, 140 ms, the average might still look acceptable while the game stutters.
Game clients smooth over small timing differences by holding a short buffer of recent server updates and drawing positions between them. When arrival times stay inside that buffer, you never notice. When a packet arrives late, the buffer runs dry and the game either freezes other players in place or snaps them to a new position, which is the rubber-banding most players recognize.
| Jitter | What it usually feels like |
|---|---|
| Under 5 ms | Effectively invisible |
| 5 to 15 ms | Fine for nearly every genre |
| 15 to 30 ms | Occasional hit-registration oddities in shooters |
| Above 30 ms | Visible stutter, rubber-banding, missed inputs |
Packet Loss: The Quiet Killer
Packet loss is the share of packets that never reach their destination. Most games send position and input data over UDP, which does not resend lost packets automatically, so the game has to guess. Rollback fighting games re-simulate frames, shooters extrapolate player positions, and both look wrong when the guess is off.
The target is 0 percent. Occasional loss below 1 percent is usually survivable. Around 1 to 2 percent, shooters begin to feel inconsistent, with shots that appear to land but do not count. Above roughly 3 percent, play becomes unreliable in almost any real-time genre. Loss also tends to arrive in bursts, so a connection that averages 1 percent but drops thirty packets in a row is worse than the number suggests.
How to Measure All Three on Windows
- Find your router address. Open Command Prompt and run ipconfig, then note the default gateway. Testing the router first separates problems inside your home from problems out on the internet.
- Ping the router for about a minute. Run ping -n 60 followed by the gateway address. Wired, you should see 1 ms or less. Wi-Fi often shows a few milliseconds with occasional jumps. Any loss or large spikes here mean the fault is local.
- Ping a distant, reliable address. Repeat with a public DNS address or, better, the game’s server address if you know it. The difference between this result and the router result is the cost of your ISP and the route beyond it.
- Read the summary, not the average. The summary line gives minimum, maximum and average. A maximum several times higher than the minimum signals jitter. Lost packets show in the loss count.
- Run pathping for the route. The pathping command followed by the destination takes several minutes because it samples each hop. It shows where along the route loss starts.
- Compare against the in-game display. Most shooters have a network graph or ping overlay. Its value includes the game’s own measurements, so treat it as the number that matters for that title.
One interpretation trap: routers in the middle of a path often deprioritize ping traffic aimed at themselves. If a middle hop shows heavy loss but every hop after it shows none, the loss is almost certainly that router rate-limiting diagnostic traffic, not real loss. Real loss carries through to the final hop.
Reading the Symptoms
| Symptom | Likely cause | First fix to try |
|---|---|---|
| Steady high ping from the start | Server too far away or a poor route | Choose a closer region in the game’s server browser |
| Ping spikes only when someone streams or downloads | Bufferbloat, where a saturated link queues packets | Enable smart queue management or a bandwidth cap slightly under your line speed on the router |
| Spikes every minute or so on Wi-Fi | Channel interference or background scanning | Switch to a cable, or change the Wi-Fi channel |
| Loss at the router test | Bad cable, weak wireless signal, failing port | Swap the cable and test again |
| Loss starting at one hop and continuing to the end | Fault at the ISP or beyond | Report the hop to the ISP with the pathping output |
| Good ping but stutter and delayed hits | Low frame rate or CPU bottleneck, not the network | Check frame time before blaming the connection |
What You Can and Cannot Fix
You cannot reduce the physical distance to a server, so the first lever is choosing the nearest region and the closest data center your matchmaking allows. The second is removing the local causes that add jitter: use a wired connection, keep the router firmware current, and avoid running large uploads during matches.
Bufferbloat deserves special mention because it is the most common cause of ping that is fine at rest and terrible under load. When your upload or download link fills, packets wait in a queue inside the router or modem, and that wait appears as extra latency. A router with smart queue management, or a manual rate limit set a little below your actual speed, keeps the queue short.
Beyond your home, you depend on your ISP’s route to the game server. Some paths are simply indirect, taking detours through distant cities. If the pathping output shows the route leaving your region and returning, a different server location or a routing change at the ISP level are the only real remedies.
Frequently Asked Questions
Is 100 ms ping bad for gaming?
It depends on the genre. In competitive shooters and fighting games 100 ms is noticeably behind, because you see opponents later than they see you. In MMOs, MOBAs and turn-based games it is perfectly playable, especially if it stays steady.
Is 20 ms ping good?
Yes, 20 ms is excellent and about what a nearby server on a wired connection delivers. At that level the network is rarely the limiting factor, and frame rate, display and your own reaction time matter more.
What is worse, high ping or packet loss?
Packet loss is generally worse. A consistently high ping can be learned and compensated for by leading your shots, but lost packets make the game guess about what happened, and no adjustment on your side removes the resulting inconsistency.
Does a faster internet plan lower ping?
Not directly. Bandwidth is how much data fits through the link per second, while ping is how long a packet takes to make the trip. A faster plan helps only when your current link is saturated and creating bufferbloat.
Why is my ping different from the speed test result?
Speed tests measure latency to a nearby test server chosen for speed, while your game connects to a specific data center that may be much farther away. The game’s own ping display is the figure that reflects your real experience.
Ready to decide? Our #1 pick for 2026 is the Competitive tactical shooters.
Live price & availability on Amazon.






