LEO vs GEO vs MEO Satellites: The Complete Industry Comparison

When SES closed its acquisition of Intelsat in 2025, the industry’s largest pure-GEO operator effectively ceased to exist — the combined company sells GEO, MEO and partner LEO capacity from one order book. That transaction is the clearest signal yet of how the LEO vs GEO vs MEO satellites question has changed: it is no longer about which orbit wins, but about which orbit wins which workload, at what cost structure, for which customer.

On this page

• Why the Orbit Debate Resurfaced
• LEO vs GEO vs MEO: The Physical Parameters That Drive Everything
• LEO vs GEO vs MEO Satellites: Latency and Capacity Compared
• Cost Structures: Three Different Businesses Wearing One Label
• Where Each Orbit Wins: The Commercial Map
• The Multi-Orbit Endgame
• Industry Implications
• What to Watch

This comparison lays out the physical parameters that drive everything downstream, the latency and capacity math professionals actually use, the cost structures each orbit imposes, and the commercial territories where each still wins. The argument, supported by the numbers below: the three orbits are converging into complementary layers of one network stack — and the operators structured to sell across them hold the pricing power.

Why the Orbit Debate Resurfaced

For four decades the answer was simple: communications meant GEO, navigation meant MEO, and LEO was for imaging, science and the ISS. LEO mega-constellations broke that settlement in under a decade — tracking data as of late 2025 puts the large majority of the 11,000+ active satellites in LEO, and consumer broadband subscriber counts in the millions. [INTERNAL LINK: what is low earth orbit → our LEO explainer covering the physics and constellation economics]

But the resurgence of the comparison is not just LEO triumphalism. GEO operators are repositioning rather than disappearing, MEO found a defensible enterprise niche, and enterprise buyers increasingly face genuine three-way choices in procurement. Understanding the trade space is now a purchasing skill, not trivia.

LEO vs GEO vs MEO: The Physical Parameters That Drive Everything

Every commercial property of a satellite system — latency, coverage, satellite count, capex profile — falls out of altitude. The reference numbers:

Parameter	LEO	MEO	GEO
Altitude	160–2,000 km	2,000–35,786 km	35,786 km
Orbital period	90–110 min	2–24 hr	24 hr (appears fixed)
Round-trip latency (typical)	25–60 ms	~130–150 ms (O3b)	~600 ms
Satellites for continuous global service	Hundreds–thousands	Tens	3–4 (non-polar)
Design life	5–7 yr	10–12 yr	15–20 yr
Typical satellite class	Small, mass-produced	Mid-size, hardened	Large, bespoke

Three second-order consequences matter as much as the headline rows. LEO satellites move fast across the sky, so user hardware must track and hand off — solved by phased arrays, but at terminal-cost premiums. MEO transits the Van Allen radiation belts, so spacecraft need radiation-hardened electronics that raise unit costs and favor long-lived, higher-value missions. GEO’s fixed position means a simple dish pointed once — still the cheapest ground segment in the industry.

GEO: The Fixed Point

At exactly 35,786 km over the equator, a satellite’s orbital period matches Earth’s rotation and it hangs motionless in the sky. That single property built the satellite industry: broadcast networks, weather observation and military communications all standardized on it. The limits are equally structural — coverage degrades toward the poles and disappears above roughly 75–80° latitude, and each spacecraft is a bespoke, high-consequence asset. Roughly 500 active satellites occupy the GEO arc as of recent tracking compilations, managed through ITU slot coordination that remains some of the most valuable regulatory real estate in telecommunications.

MEO: The Compromise Band

Everything between 2,000 km and GEO is MEO, but commercial activity clusters in two zones. Navigation owns the ~20,000 km band: GPS at 20,200 km, Galileo at 23,222 km, GLONASS and BeiDou nearby, because that geometry gives each satellite a wide, slowly changing footprint — near-optimal for global positioning with a few dozen spacecraft. Communications MEO clusters lower, at O3b’s 8,062 km equatorial shell, where a fleet in the tens of satellites serves committed enterprise capacity. Radiation exposure is the tax: hardening requirements make MEO spacecraft the most expensive per kilogram of the three orbits.

LEO: The Production-Line Orbit

Below 2,000 km, physics forces scale — small footprints and fast transits mean constellations or nothing — and scale forces industrialization. The commercially dominant shells sit between 500 and 1,200 km, balancing drag against debris-decay obligations. What LEO uniquely offers besides latency: polar and ocean coverage no GEO arc can see, graceful degradation when individual satellites fail, and a five-to-seven-year hardware refresh that lets operators ride the semiconductor cost curve instead of freezing 2015 technology in orbit for two decades.

LEO vs GEO vs MEO Satellites: Latency and Capacity Compared

Latency is the comparison’s hardest currency because it cannot be engineered away. A signal to GEO and back travels at least 71,572 km; at the speed of light that is roughly 480 ms round trip before any processing, and real consumer services measure 600 ms or worse. O3b’s MEO shell at 8,062 km delivers approximately 130–150 ms — deliberately positioned as the compromise orbit. LEO at 550 km costs about 7 ms of physics, and operator-reported service figures cluster at 25–60 ms. [INTERNAL LINK: LEO vs GEO latency comparison → our full technical latency analysis]

Capacity tells a subtler story. A modern high-throughput GEO satellite concentrates terabit-class capacity over a fixed region and amortizes it across 15–20 years — extraordinarily efficient where demand is dense and predictable. LEO capacity is distributed and refreshed continuously: total constellation throughput is enormous, but per-cell capacity over any one point is finite and shared. This is why GEO still carries broadcast and why LEO oversubscription in dense markets remains the metric enterprise buyers should interrogate.

Two operational caveats belong in any honest comparison. LEO links ride on constant satellite handoffs, so worst-case jitter — not median latency — is the number that matters for real-time applications; well-designed constellations keep it low, but buyers should demand the distribution, not the average. And all three orbits share sensitivity to rain fade at Ka-band and above, which is a link-budget question independent of altitude. Neither caveat reverses the ranking; both belong in procurement language.

Cost Structures: Three Different Businesses Wearing One Label

A GEO program is project finance: analyst estimates put a large GEO satellite at several hundred million dollars built and launched, recovered over two decades from committed capacity contracts. Failure risk concentrates in single assets — one launch failure is a material corporate event.

A LEO constellation is manufacturing economics: hundreds of small satellites, serial production, continuous launch cadence and a permanent 5–7 year replacement cycle. Capex never stops, but risk is distributed — individual satellite losses are operationally irrelevant. MEO sits between: O3b mPOWER’s build-out is measured in the low tens of satellites, each hardened and long-lived, serving contracted enterprise and government demand rather than consumer volume.

The investor translation: GEO cash flows look like infrastructure, LEO economics look like industrial manufacturing plus subscriber acquisition, and MEO looks like specialty enterprise networking. Comparing operators across orbits on the same multiples misprices all three.

Where Each Orbit Wins: The Commercial Map

Workload	Best-fit orbit	Why
Consumer & enterprise broadband	LEO	Latency parity with terrestrial; scale economics
Video broadcast & content distribution	GEO	One-to-many over fixed regions; cheapest ground segment
Navigation / timing (GNSS)	MEO	Orbital geometry balances coverage and signal strength
Cruise, energy & carrier backhaul	MEO + LEO	O3b-class committed capacity, LEO for latency-sensitive overlay
Direct-to-device messaging & broadband	LEO	Link budgets require short path to unmodified phones
Government persistent surveillance & missile warning	GEO + LEO layers	Staring coverage from GEO, proliferated resilience in LEO

Two entries deserve emphasis. GNSS is MEO’s permanent franchise — GPS at roughly 20,200 km, Galileo at 23,222 km — because that geometry is close to optimal for global navigation coverage; no LEO constellation replaces it, though LEO augmentation services are an active investment theme. And direct-to-device is LEO’s alone: the physics of closing a link to an unmodified smartphone effectively mandates low altitude. [INTERNAL LINK: AST SpaceMobile direct to cell → our analysis of direct-to-device commercial viability]

The Multi-Orbit Endgame

The market has voted against orbit purism. SES paired its GEO fleet with MEO mPOWER and closed the Intelsat acquisition in 2025; Eutelsat’s merger with OneWeb bolted a LEO constellation onto a GEO broadcaster; and GEO incumbents increasingly resell LEO capacity inside managed enterprise contracts. [EXTERNAL LINK: SES investor relations → acquisition and mPOWER deployment disclosures]

The logic is straightforward: customers buy outcomes — availability, latency class, committed throughput — not orbits. An operator that can arbitrage its own multi-orbit portfolio against each workload defends margin better than one selling a single altitude. The open question for 2026–27 is whether multi-orbit incumbents can integrate fast enough to matter before LEO-native operators simply add the enterprise service layers themselves.

The hardware is cooperating with the strategy: terminal vendors now ship electronically steered flat panels that track LEO constellations and point at GEO or MEO assets from the same aperture, collapsing what used to be three antenna installations into one. Once the terminal is orbit-agnostic, the last physical argument for single-orbit contracts goes with it.

Frequently Asked Questions

Which orbit is best for satellite internet: LEO, MEO or GEO?

For latency-sensitive broadband — consumer, enterprise WAN, maritime, aviation — LEO wins on its 25–60 ms real-world latency. GEO remains cost-effective for one-way distribution and thin-route coverage where 600 ms is tolerable. MEO’s O3b occupies the committed-capacity enterprise middle at roughly 130–150 ms.

Why is GEO latency around 600 ms regardless of technology?

Distance. A round trip to 35,786 km covers at least 71,572 km, which costs roughly 480 ms at the speed of light before any network processing. No modulation, protocol or hardware improvement removes propagation delay — only a lower orbit does.

Is MEO still commercially relevant in 2026?

Yes, in two franchises. Navigation constellations — GPS, Galileo, GLONASS, BeiDou — are MEO by physics and are not moving. And SES’s O3b mPOWER serves cruise, energy, carrier and government customers who value committed throughput at ~150 ms, a segment its operator reports as growing.

What does a multi-orbit strategy mean in an enterprise contract?

One provider, multiple orbital assets behind a single SLA: for example GEO or MEO committed capacity for baseline load with LEO overlay for latency-sensitive traffic. Buyers get outcome-based service tiers; the operator gets to arbitrage its own portfolio. Contract language should still specify per-path performance floors.

How do satellite lifetimes and capex differ across the three orbits?

GEO: 15–20 year assets, several hundred million dollars each, project-finance economics. MEO: 10–12 year hardened spacecraft in small fleets. LEO: 5–7 year satellites built on production lines, meaning capex is continuous by design — investors should model replacement cycles, not one-time build-outs.