Europe Finalizes Its Own Satellite Network. What IRIS² Actually Changes.

What Just Got Approved

Is Europe actually building its own satellite internet, or is this another announcement that quietly stalls in committee?

IRIS² stands for Infrastructure for Resilience, Interconnectivity, and Security by Satellite. The European Union has now moved this past the planning phase into an actual concession contract, handing operational control to a consortium called SpaceRISE. That consortium is built around three established satellite operators: SES out of Luxembourg, Eutelsat out of France, and Hispasat out of Spain. These are not startups betting on unproven hardware. They already run geostationary and medium-orbit fleets serving broadcast, government, and connectivity customers today.

The reported price tag sits around 10.6 billion euros, split between public EU funding, contributions from member states, and private capital from the consortium partners. The constellation is meant to combine satellites in low Earth orbit with assets in medium Earth orbit, a hybrid approach that differs from the single-shell design most commercial networks use. Public reporting has pointed to service starting around 2030, with the network intended to run through at least 2033 under the current agreement.

The stated purpose is straightforward on paper: secure connectivity for European governments and institutions, plus broadband access for underserved areas across the continent and partner regions. Whether that timeline holds is a separate question, and one worth watching closely given how satellite programs tend to slip.

Why 'Sovereign' Is the Point

Every European government agency, telecom, and defense contractor currently routes some portion of its satellite connectivity through providers headquartered outside the continent. That works fine until it doesn't. A licensing dispute, a change in foreign export policy, a company prioritizing its home market during a crisis — any of these can interrupt service for customers who have no seat at the table when those decisions get made.

This is the same logic that drives any business to diversify vendors for a critical function. You do not run your entire operation on a single supplier if that supplier answers to someone else's priorities. Cloud companies split workloads across regions for this exact reason. Airlines maintain relationships with multiple fuel suppliers. The word sovereign gets attached to IRIS² because governments are involved, but the underlying decision is closer to a procurement one than a political one: control your own infrastructure or accept the terms of whoever controls it for you.

SpaceRISE gives the EU an operator it can direct, audit, and hold to contract terms written under its own regulatory framework. That matters for government communications, for emergency response coordination, for military logistics that cannot depend on a system another country could throttle or deny.

Resilience is the actual product here. Independence just happens to be the mechanism.

The Technical Tradeoffs

Most commercial constellations pick one shell and stay there. Starlink runs low Earth orbit almost exclusively, thousands of small satellites a few hundred miles up, because that altitude keeps latency low and lets you replace hardware cheaply as it degrades. IRIS² does not do that. It stacks LEO satellites with a layer in medium Earth orbit, roughly ten times higher, and asks the two shells to work together.

The reason to bother with this is coverage math. LEO satellites move fast and cover a narrow strip of ground at any given moment, so you need a lot of them to guarantee constant service anywhere on the continent. MEO satellites sit higher and slower, each one covering far more ground, which fills gaps the LEO layer cannot reach continuously without even more hardware. Combine the two and you get lower latency where LEO is overhead and steadier backup coverage where it isn't.

The cost of that design shows up in deployment difficulty. Two shells mean two sets of ground infrastructure, two sets of orbital mechanics to manage, and software that has to hand off connections between layers without dropping government or military traffic mid-transfer. SES already operates MEO satellites through its O3b system, which is likely why the consortium is willing to attempt this instead of picking the simpler, single-shell route everyone else took.

What to Watch Next

2030 is a target, not a date on a calendar you can count on. Satellite programs slip constantly, and a hybrid two-shell design gives this one more places to slip than most. So the honest question is not whether IRIS² launches, but which checkpoints tell you it's actually on schedule versus quietly drifting the way these projects tend to.

The first real signal is manufacturing contracts getting locked in with actual satellite builders, not just SpaceRISE announcing partnerships. Hardware orders placed on paper mean nothing until production lines are running.

The second is a first launch, even a partial one. A handful of LEO satellites going up on schedule tells you the consortium can execute, not just plan. Watch whether that first launch happens anywhere near the timeline SES, Eutelsat, and Hispasat commit to publicly over the next year or two.

The third is whether the MEO integration gets demonstrated before full deployment. SES has O3b experience, but stitching two orbital shells together for government-grade traffic handoff is a different problem than running MEO alone. If that integration testing gets delayed or quietly dropped from public updates, that is the tell.

Funding disbursement schedules matter too. A 10.6 billion euro program split across public and private sources will show stress in payment delays before it shows up anywhere else.