Starlink Gen2 Orbit Changes: What They Mean for Your Ping
LOWER ORBITS • GEN2 SHELLS • V3 PLANS • REAL-WORLD LATENCY
Starlink is still lowering the constellation — but “everything is moving to 480 km” is now too simple
Starlink’s current constellation plan says its V1 and V2 broadband satellites are being moved below 500 km, into several operational shells between roughly 450 km and 490 km by the end of 2026.
The lower altitude can trim a small amount from the pure speed-of-light part of latency, but that is not the main reason your gaming ping changes. Congestion, satellite handoffs, radio scheduling, gateway and PoP routing, Wi-Fi and the route to the game server still matter far more from one session to the next.
What Starlink’s current 2026 orbit plan actually says
Starlink’s current space-safety page says the company is in the process of lowering satellites from initial operating altitudes above 500 km and plans to complete that shell lowering by the end of 2026.
| Starlink group | Current planned mean shell altitudes | What changed from the old article |
|---|---|---|
| V1 + V2 broadband | 485 km, 472.5 km, 463 km and 462.5 km shells | The end state is not one single 480 km shell. |
| V1 direct-to-cell | 360 km and 358.5 km | These sit much lower than the traditional broadband shells. |
| V3 broadband | 330–360 km region planned | Starlink says future V3 vehicles are expected in this lower region through late 2026 and 2027. |
The 480 km figure still matters. The FCC has authorised 480 km and 485 km Gen2 shells, and some existing Gen2 satellites can be lowered into nearby authorised shells. But Starlink’s own current constellation-management page now describes a broader set of final operational altitudes.
What the FCC authorised for Gen2
The FCC order also allows SpaceX to distribute satellites more flexibly across authorised shells, including 340, 345, 350, 355, 365, 480 and 485 km configurations within the conditions in the order. It does not mean every authorised satellite is already launched or operating at those altitudes.
For the broader altitude picture, see our separate guide to how high Starlink satellites orbit.
How much can the lower orbit reduce ping by itself?
In a deliberately simplified vertical path, a 70 km reduction removes about 280 km from a full round trip when you count the user-to-satellite and satellite-to-ground legs in both directions. At the speed of light, that is roughly 0.9 milliseconds.
Real satellite links are not perfectly vertical, and traffic may use different gateways, laser links and routing paths, so you should not expect a neat 0.9 ms improvement in a game. The useful point is the scale: the altitude change alone is a small latency saving, not a 20 or 30 ms transformation.
Starlink’s current fixed-service specification lists expected latency around 25–50 ms for fixed plans, while noting that users can see higher latency in remote locations or during high load. Starlink’s engineering material continues to describe a long-term goal of stable 20 ms median latency with minimal packet loss.
Why Starlink is lowering the shells in the first place
The main stated reason is space safety, not gaming. Starlink says that operating lower reduces the time a failed satellite would remain in orbit if it could no longer perform a controlled deorbit.
Its current space-safety page says the lower shells can reduce ballistic decay time by more than 80% around solar minimum, turning a potential period of more than four years into a matter of months under the scenario it models.
That safety change can still have network side effects. Lower shells can support smaller coverage footprints and different capacity planning, but any real improvement to peak-time gaming consistency depends on the whole network rather than altitude alone.
The next change to watch: V3 at 330–360 km
Starlink now says future V3 broadband vehicles are planned for the 330–360 km region through late 2026 and 2027. That is materially lower than the traditional V1/V2 broadband constellation.
It is too early to turn that into a guaranteed customer ping figure. The eventual result will depend on V3 capacity, beam design, routing, gateway strategy, laser links, user density and how the new shells are integrated with the rest of the constellation.
For context on how the network reached this point, our history of Starlink covers the expansion from the early constellation to Gen2.
What should Starlink users actually watch?
If you want to compare your own connection over several weeks, test from the same device, preferably over Ethernet, at similar times of day and against the same nearby endpoint. Then repeat the test against the server region you actually use for gaming.
Customer hardware still matters as well. Our guide to the newer Starlink dishes covers the terminal side of the connection.
What not to expect from the 2026 orbit changes
The bottom line
Starlink’s 2026 orbit changes are real, but the current picture is more nuanced than the original 550 km-to-480 km headline. V1 and V2 broadband satellites are being consolidated into several shells below 500 km, while future V3 broadband satellites are planned much lower at roughly 330–360 km. Lower altitude helps propagation delay a little; the bigger customer gains will depend on capacity, routing and how consistently the whole network performs.
Starlink orbit and latency FAQs
Are all Starlink satellites moving to exactly 480 km?
No. Starlink's current constellation plan shows several V1 and V2 broadband shells below 500 km, including mean altitudes around 463 km, 472.5 km and 485 km. The 480 km figure remains important, but it is not the single final altitude for the whole constellation.
How much latency can a 550 km to 480 km drop save by itself?
In a simplified vertical round-trip path, reducing altitude by 70 km removes about 280 km of total space path across the four satellite legs, which is roughly 0.9 milliseconds at the speed of light. Real routes use slant paths and other network stages, so actual latency changes will not match that simple figure exactly.
Does a lower orbit automatically mean lower gaming ping?
Not necessarily. Orbit height affects propagation delay, but Starlink also identifies congestion, routing, gateways and points of presence, radio scheduling, Wi-Fi and other network delays as important parts of total latency.
Sources checked
- Starlink Space Safety: constellation altitudes — current 2026 shell-lowering plan, final V1/V2 broadband shells and planned V3 altitude region.
- FCC DA 26-36 — additional Gen2 authorisation and orbital-shell flexibility.
- Starlink: Improving Starlink’s Latency — Starlink’s explanation of latency, routing, congestion and its 20 ms median-latency goal.
- Starlink network update — current explanation of network latency and the role of Starlink’s ground network.
- Starlink specifications — current fixed-service expected latency and performance ranges.