Is Starlink good for gaming?
Short answer: good for casual and mid-core gaming, risky for competitive play. Starlink's low-orbit design brought satellite ping down from 600+ ms to a workable 25–60 ms — but the variance between best and worst packets is what competitive games punish. Here is what to expect and what you can actually fix.
Typical Starlink latency profile
Typical ranges reported by the community and Starlink's own statistics — your line varies by dish placement, congestion cell and weather. Measure your own with the free test below.
| Metric | Typical Starlink | Typical cable/fibre |
|---|---|---|
| Idle ping (regional server) | 25–60 ms | 5–35 ms |
| Worst-1% ping | 100–300+ ms (handoffs, fades) | 40–120 ms |
| Download | ~50–250 Mbps | 100–1000+ Mbps |
| Upload | ~10–20 Mbps (the bottleneck) | 10–1000 Mbps |
Where the lag actually comes from
- Narrow uplink + queues — the biggest fixable factor. When anything uploads (cloud backup, a stream, another player's update), the small upstream saturates and queues balloon: bufferbloat. SQM/CAKE pacing to your measured upload removes most of it.
- Satellite handoffs and path changes — physics and routing you cannot fix locally; they show up as occasional spikes between otherwise stable pings.
- Weather fades — heavy rain/snow causes loss bursts. SQM cannot help here; dish placement (clear sky view) can reduce it.
Make your Starlink line game better
- Measure first: run the bufferbloat test idle and under load, plus the packet loss test on a clear day.
- If loaded latency explodes: enable SQM/CAKE on your router — on OpenWrt it is one toggle with NetSteer (settings explained in the SQM guide; set the WAN interface to the Starlink router side).
- Keep the dish clear and wired to your router over ethernet — avoid WiFi double-hop before the satellite leg even starts.
- For competitive play, prefer local servers and off-peak hours; for everything else, modern Starlink is genuinely playable.
Other ISPs we checked
Xfinity · Cox · AT&T Fiber
FAQ
What ping does Starlink have for gaming?
Typical idle ping to nearby servers runs about 25-60 ms, noticeably better than legacy geostationary satellite (600+ ms) but still above most cable or fibre lines (10-35 ms). The catch is variance: satellite handoffs and ground-station routing add occasional jumps, so the worst 1% of packets matters more than the average. Competitive shooters feel this variance; slower-paced games mostly do not.
Why does Starlink lag spike when others download?
The uplink is the constrained resource: Starlink plans carry modest upload speeds, and when that narrow pipe saturates, queues build on both your router and the network path — classic bufferbloat. SQM/CAKE on your own router (pacing to your measured upload) removes the queue on your side; see the NetSteer OpenWrt SQM guide. It cannot fix radio-path variation, but it removes the self-inflicted part of the lag.
How do I test whether my Starlink line is the problem?
Run the free NetSteer bufferbloat test twice: once on a quiet line and once while something is downloading. If idle latency is acceptable but loaded latency explodes, your router queue is the fixable part. Packet loss that appears in clear weather but not during rain points to the dish or path, not your router.