June 14, 2026 Β· 9 min read
What Is a Good Ping? Latency Benchmarks for Gaming, Video Calls & Streaming (2026)
A good ping is under 50 ms for gaming, under 100 ms for video calls, and under 150 ms for general use. See the full latency, jitter, and packet-loss benchmarks by activity β and how to test and lower yours.
"What's your ping?" is shorthand for latency β the round-trip time (RTT) for a small packet to reach a server and come back, measured in milliseconds. A good ping is under 50 ms for gaming, under 100 ms for video calls, and under 150 ms for general browsing. Under 20 ms is excellent; over 150 ms feels laggy for anything real-time. But the headline number is only half the story: jitter (how much ping wobbles) and packet loss often decide whether a call or game actually feels smooth.
Quick answer: good ping by activity
| Activity | Excellent | Good | Playable | Painful |
|---|---|---|---|---|
| Competitive FPS / fighting games | < 20 ms | < 50 ms | 50β100 ms | > 100 ms |
| Online gaming (general) | < 30 ms | < 60 ms | 60β120 ms | > 150 ms |
| Video calls (Zoom, Meet) | < 50 ms | < 100 ms | 100β200 ms | > 250 ms |
| Browsing & 4K streaming | < 80 ms | < 150 ms | 150β300 ms | > 300 ms |
| Cloud gaming (GeForce NOW etc.) | < 30 ms | < 50 ms | 50β80 ms | > 100 ms |
These are RTT rules of thumb to a nearby server, not guarantees. Want your own number right now? Run the latency test β it samples your real round-trip time in the browser and rates it for gaming, video calls, and browsing.
Latency, jitter, and packet loss β the three that matter
Ping alone can lie. Three numbers together describe a connection's real-time quality:
| Metric | What it measures | Good target | What bad looks like |
|---|---|---|---|
| Latency (ping) | Average round-trip delay | < 50 ms (gaming), < 100 ms (calls) | Sluggish aim, delayed reactions |
| Jitter | How much ping varies between samples | < 10 ms | Choppy audio, stutter, rubber-banding |
| Packet loss | % of packets that never arrive | < 1% | Freezes, dropouts, teleporting |
A 25 ms average ping with 60 ms of jitter feels worse than a steady 45 ms. That's why our latency tool reports jitter and a failed-sample rate alongside the median β a single average hides the instability that ruins calls and matches. For a deeper explanation of why a browser measures HTTPS round-trip rather than true ICMP ping, see Browser Latency: Ping vs HTTPS RTT.
Why geography sets a floor
You cannot beat physics. Light in fiber travels at roughly two-thirds of c, and packets take an indirect path, so distance imposes a hard minimum:
| Route | Realistic best ping |
|---|---|
| Same city | 1β10 ms |
| Same country / region | 10β40 ms |
| Neighbouring continent | 40β100 ms |
| Across the world | 150β300 ms+ |
This is why a "good" ping is always relative to the destination. A 30 ms reading to a server in your city is great; 30 ms to one on another continent is impossible. Always compare on the same endpoint, and use the game client's own ping meter for the actual game region.
How to test your ping correctly
- Use a nearby target. Testing against a distant server measures distance, not your line. Our latency test times the round-trip to the nearest edge.
- Take many samples. One reading is noise. Look at the median and the spread, not a single spike.
- Watch jitter, not just the average. A low average with high jitter still breaks calls.
- Test idle and under load. Ping that's fine when idle but explodes during a download is bufferbloat β see below.
- Compare wired vs Wi-Fi, VPN on vs off. Change one variable at a time.
How to lower your ping
Most lag has a fixable cause. Work from physics outward:
- Go wired. Ethernet removes Wi-Fi contention, interference, and retransmits β usually the single biggest win for jitter.
- Pick the closest server region. Don't chase friends onto another continent unless you accept the penalty.
- Fix bufferbloat. If ping is 18 ms idle but jumps to 250 ms during a download, oversized router queues are the culprit. Enable SQM / Smart Queue Management (fq_codel or cake). Confirm the problem first with our speed test, which measures latency under load β and read How to Read Your Speed Test Results to interpret the bufferbloat grade.
- Reconsider the VPN. A VPN usually adds latency (extra hop + encryption), but can occasionally lower it if your ISP peers badly. Measure both with the same tool instead of trusting "gaming mode" marketing. If you use one, verify it isn't leaking with our VPN leak test.
- Cap background uploads. Cloud backups and big uploads saturate the link and spike ping for everyone in the house.
The 30-second verdict
| Your reading | What it means |
|---|---|
| < 30 ms, jitter < 10 ms | Excellent β ready for competitive play |
| 30β80 ms, jitter < 20 ms | Good β fine for nearly everything |
| 80β150 ms or jitter 20β40 ms | Fair β calls and fast games degrade |
| > 150 ms or jitter > 40 ms or loss > 1% | Poor β fix Wi-Fi, server choice, or bufferbloat |
A "good ping" isn't one universal number β it's low enough for what you're doing, to where you're doing it, and stable. Check yours now with the latency test, then pair it with the speed test to see how your latency holds up under load.