Satellite internet used to be a non-starter for gaming. Old geostationary services like HughesNet and Viasat sat 35,786km above the equator, which meant a round trip of 600ms or more before you even accounted for the game server's own ping. Starlink's low-Earth-orbit satellites sit roughly 550km up, and that difference has genuinely changed what's possible — but "changed" isn't the same as "solved." This is what the numbers actually look like in 2026, and where Starlink still creates problems that a fibre or cable connection doesn't.
The Latency Numbers, Without the Marketing
Starlink publishes median latency figures by region, and in most of the UK and US the current numbers sit between 25ms and 40ms during off-peak hours. That's a real result — it puts Starlink in the same rough band as a lot of cable connections, and comfortably ahead of any previous satellite service.
The caveat is "off-peak." Starlink's network is shared capacity per cell, and during 7–10pm local time — exactly when most people are gaming — congestion pushes latency up. Users commonly report 40–80ms during peak hours on residential plans, and in oversubscribed cells it can spike higher. This isn't a fixed number you can rely on; it moves with how many other households are active on your satellite cell that evening.
SpaceX's Gen 3 satellites, which started rolling out through 2025 and continued into 2026, improved on this materially over the original Gen 2 constellation, and the V3 satellites due later in 2026 are aimed at pushing best-case latency toward the 15-20ms range. None of that changes the peak-hour congestion problem, which is about shared capacity, not satellite hardware.
Practical comparison:
| Connection type | Typical latency | Peak-hour variance |
|---|---|---|
| Fibre (FTTP) | 5-15ms | Minimal |
| Cable | 15-30ms | Low-moderate |
| Starlink (2026) | 25-40ms | High (up to 80ms+) |
| 4G/5G home broadband | 30-60ms | Moderate-high |
| Old geostationary satellite | 600ms+ | N/A — unplayable |
For most competitive shooters and fighting games, anything consistently under 40ms is workable. The problem with Starlink isn't the median — it's the variance.
Jitter Is the Real Issue, Not Raw Ping
A single ping number doesn't tell you what a satellite connection feels like to play on. Starlink's dish is constantly handing your connection off between satellites as they pass overhead, and each handoff can introduce a brief latency spike. Most of the time this is small enough not to notice. Occasionally it produces a jitter spike of 100-200ms for a fraction of a second — enough to cause a visible rubber-band in a fast-paced shooter even if your average ping looks fine on a speed test.
Two things make this worse:
- Obstructions. Starlink's dish needs a clear view of the sky. Tree branches, a nearby roofline, or even heavy rain can cause brief dropouts. The app's own obstruction map is worth checking before you assume a jitter problem is the network's fault rather than your mounting position.
- Wi-Fi on the stock router. The Starlink router (and the built-in router on the Mini) is designed for coverage, not for low-latency gaming. Running your console or PC over Wi-Fi from it adds its own jitter on top of whatever the satellite link is doing. This stacks two variable-latency problems on top of each other, which is a big part of why "Starlink feels laggy" reports are often partly a home-network issue. See our guide on bufferbloat if ping spikes coincide with anything else on the connection downloading or uploading — Starlink is not immune to bufferbloat, and SQM-capable third-party routers can help.
If you're serious about gaming on Starlink, put the dish's router into bypass mode and run your own router with a proper wired connection to your console or PC. A cheap USB Ethernet adapter for a laptop or handheld removes one variable source of jitter entirely, and it's the single highest-value change most people can make.
The CGNAT Problem: NAT Type on Starlink
This is the part that catches people out, and it's directly related to what we've covered in our Strict NAT and CGNAT guide. Starlink's standard residential service runs behind Carrier-Grade NAT (CGNAT) for IPv4. That means your home isn't the only "customer" sharing a public IPv4 address — Starlink pools multiple households behind one — and traditional port forwarding, which needs to open a port on a public IP that's actually yours, simply doesn't reach far enough upstream to work.
In practice this shows up as:
- Your console reporting a Strict or Moderate NAT type no matter what you change in your own router settings
- Peer-to-peer game connections (party chat, some co-op modes, certain older titles) failing to connect directly, and instead falling back to slower relay servers
- Port forwarding guides that work perfectly on a normal ISP connection doing nothing at all on Starlink, because there's no public IP on your side of the CGNAT boundary to forward a port to
There are three real workarounds, in order of how much they cost you:
- Enable IPv6, if it isn't already on. Starlink supports IPv6 by default in most regions, and if your router and console both use it, IPv6-capable games get a genuinely open connection without the CGNAT problem at all — because IPv6 doesn't need NAT the way IPv4 does. This is free and is the first thing to check.
- Pay for a static/public IP add-on. Starlink's Local and Global Priority plans include an option for a dedicated public IPv4 address, which restores normal port forwarding. This isn't available on the standard Residential plan and adds a meaningful amount to the monthly cost.
- Use a gaming VPN or relay service such as ExitLag or a mesh VPN like Tailscale/ZeroTier for specific use cases (hosting a private server, remote access to a NAS). This routes your traffic through a server with its own public IP, which sidesteps CGNAT but adds a small amount of latency on top — see our ExitLag review for what that latency trade-off actually looks like in practice.
If your goal is simply ranked matchmaking in the games most people play, NAT type matters less than it used to — most modern shooters and battle royales are built around dedicated servers rather than peer-to-peer connections, so a Strict NAT type is an annoyance rather than a blocker. It matters much more for older titles, party chat reliability on console, and anything that explicitly needs an inbound connection (self-hosting, certain co-op games).
Who Should Actually Consider Starlink for Gaming
Starlink isn't competing with fibre for anyone who has fibre available. The honest use case is narrower:
- Rural areas with no cable or fibre option, where the alternative is DSL at 10-20ms... no, realistically the alternative is DSL at high latency and low bandwidth, or 4G/5G home broadband with its own congestion problems. Here, Starlink's 25-40ms off-peak median is a genuine upgrade.
- Off-grid or mobile setups — the Mini in particular, for camping, vanlife, or temporary locations — where any low-latency option beats no option.
- Backup connections for streamers or competitive players who need failover if their primary line drops, accepting that the backup won't match the primary's consistency.
It's a weaker choice if you're in an area with any fibre or decent cable coverage, purely on latency consistency and the CGNAT complication. It's also worth factoring in hardware cost — the dish and router are an upfront purchase on top of the monthly subscription, unlike a standard ISP install.
Setup Checklist for Gaming on Starlink
If you're already on Starlink or committed to it, this is the order to work through:
- Check the obstruction map in the Starlink app and confirm you're getting close to a fully clear view of the sky. Even minor obstructions cause disproportionate jitter.
- Switch the Starlink router to bypass mode and connect your own router behind it, so you get proper QoS and SQM controls rather than the stock router's limited settings.
- Wire your console or PC directly with Ethernet. Don't game over Wi-Fi from either the Starlink router or your own — the jitter savings are significant.
- Enable IPv6 on your router and check your console picks it up, before you assume you need a paid public IP.
- Run a ping/jitter test during peak hours (7-10pm) as well as off-peak, so you know what you're actually working with before a ranked match, not just what the marketing page promises.
- Consider a gaming VPN only after the above — it fixes CGNAT symptoms but doesn't fix satellite jitter, and adding a hop always costs a few milliseconds of baseline latency.
The Bottom Line
Starlink in 2026 is the first satellite internet service that's genuinely playable for most online games, not just technically connected. Median latency in the 25-40ms range is real and represents a huge jump from older satellite technology. But it comes with two problems fibre and cable don't have: latency that varies meaningfully between off-peak and peak hours, and a CGNAT setup that breaks assumptions built into a lot of port-forwarding and NAT-type guidance written for standard ISPs. If you have a real alternative, it's still the better choice for competitive play. If you don't, Starlink with a wired setup and IPv6 enabled is a legitimate way to game — just go in knowing what "good enough" means on a satellite link, rather than expecting fibre-level consistency.