Home / Knowledge Center / Ping & Latency
What Is a Good Ping?
8 min read · Updated 2026-09-17
Under 20 ms is excellent, 20–50 ms is good, 50–100 ms is usable and above 100 ms starts to feel sluggish in anything interactive. But the honest answer is that a good ping depends on the activity and on how consistent the number stays, not just on the average a speed test reports.
Key takeaways
- Competitive shooters and fighting games want under 30 ms; most other online games are fine up to 60 ms.
- Video calls tolerate 100–150 ms before conversation feels awkward.
- Streaming barely cares about ping at all — it cares about sustained bandwidth.
- A stable 45 ms beats an average of 25 ms that spikes to 300 ms, because jitter is what you actually notice.
- Distance to the server sets a physical floor no plan upgrade can beat.
Good ping ranges by activity
Ping is the round trip from your device to a server and back. What counts as good depends entirely on how quickly the application needs that round trip to complete.
- Competitive FPS, fighting and racing games: under 30 ms ideal, under 50 ms playable.
- MOBAs, MMOs, strategy and most console games: under 60 ms is comfortable.
- Cloud gaming: under 40 ms, because your input and the video both cross the network.
- Video calls and VoIP: under 100 ms is transparent, 150 ms is noticeable, 250 ms causes people to talk over each other.
- Browsing: under 100 ms feels instant; page load time is dominated by DNS and server response anyway.
- Streaming video: essentially irrelevant — the player buffers seconds of content ahead.
Why the physical floor matters
Signals travel at a finite speed, and routing is never a straight line. A round trip across a continent costs tens of milliseconds before any equipment is involved, and an intercontinental trip costs well over 100 ms. No plan upgrade removes that.
This is why choosing a nearby game server usually improves latency far more than anything you can buy. If your ping to a local server is 15 ms and to an overseas server 180 ms, both numbers are healthy — they simply describe different distances.
Consistency beats the average
Two connections can both report 40 ms and feel completely different. If one varies between 38 and 44 ms and the other swings between 12 and 400 ms, only the first will feel responsive. That variation is jitter, and it is the single most common reason a connection with good numbers still feels bad.
Latency under load is the related trap: many connections measure well when idle and collapse when someone starts an upload. That symptom is bufferbloat, and it is fixable at the router.
What raises your ping
In rough order of how often each turns out to be the cause:
- WiFi instead of Ethernet — wireless adds a few milliseconds and much more variance.
- Distance to the server or an inefficient route through your provider.
- A saturated uplink: an upload in the background inflates every round trip.
- Connection type: satellite and some fixed-wireless links have a high floor by design.
- Background devices and updates competing for airtime and queue space.
- A VPN, which adds both encryption overhead and a routing detour.
How to check where you stand
Measure while idle, then measure again while a large upload runs. Repeat both on Ethernet if you can. If the idle number is fine but the loaded number triples, your problem is queue management rather than raw latency. If both are high, look at distance, connection type and your route.
Put this into practice with a real measurement.
Measure your ping now