Chapters
00:00 Today's headlines
00:47 FCC authority for Globalstar C-3 system
02:18 Four operators explore joint bid for MSS
03:39 Amazon plans more than €16 billion in Germany
04:35 EraDrive won $13M Era-Node award
06:00 Cosmos 2612 maneuvers around ICEYE-X36
09:17 Unconfirmed interference near ICEYE-X36
The money, missions, and power shaping space. Space Stakes is a daily briefing on the business of the new space race — launches, contracts, constellations, and the capital behind them. Every episode cuts through the industry's hype: signed contracts vs. paper constellations, funded orders vs. "up to" ceilings, launch dates vs. track records. Who pays, who profits, and who actually delivers — told so both aerospace insiders and curious newcomers finish feeling it was made for them. Space Stakes is an AI-voiced podcast, created and built by a real human, Brian Lampert. Nothing on this show is financial advice.
Also from Brian Lampert: Quickly Quantum and Concrete Compute.
A Russian government-owned satellite maneuvered toward commercial radar satellite ICEYE-X36, coming as close as 500 meters, according to LeoLabs, as reported by Breaking Defense. That’s a close approach with stakes beyond two spacecraft: ICEYE imagery has been widely believed to support Ukraine, though the specific satellite’s role has not been publicly confirmed. What does an uncoordinated approach mean when a commercial spacecraft may be involved? We’ll look at what the tracking shows, what the officials and experts say, and where the uncertainty remains. Welcome back to Space Stakes, your daily brief on the business of space. It's Tuesday, October 20, 2026. Let's get into it.
Globalstar has FCC authority to operate its third-generation C-3 satellite constellation in the United States, Via Satellite reports. The system is designed for direct-to-device service — satellite connectivity to ordinary smartphones — using mobile satellite services, or MSS, spectrum. Globalstar announced the approval Monday. Its planned system includes 48 low-Earth-orbit satellites, six on-orbit spares and 90 ground station antennas around the world. MDA Space is building the satellites, and Globalstar filed for the constellation in February of 2025 after Apple invested to fund it.
The distinction matters: FCC authorization permits operations; it doesn’t mean those satellites are already in orbit or that the service is operating. Globalstar CEO Paul Jacobs called the approval “a critical step forward for continuing to enhance the capabilities of our Low-Earth Orbit satellite constellations,” and said it would support next-generation services with increased capacity, improved performance and greater flexibility.
There’s also a corporate deal underway. Globalstar is going through a deal to be acquired by Amazon, which plans to operate both C-3 and a new Amazon direct-to-device constellation of up to 5,105 satellites. The plans place Globalstar’s system inside a much larger connectivity strategy, but the authorization itself is the concrete milestone today. For you, the practical promise is a phone connecting by satellite; the next step is turning permission and plans into a working service.
In the same European MSS spectrum contest, four mobile operators are exploring a joint bid, Via Satellite reports. Deutsche Telekom, Orange, Telefónica and Vodafone announced a letter of intent to consider seeking spectrum for direct-to-device service. It’s a formal confirmation that they’re working together, not a firm plan, and the satellite partner is still to be selected.
The European Commission is deciding which companies will be authorized to operate in the 2 GHz MSS spectrum, with plans to reserve a portion for European entities. The four operators say they want “responsible European governance” and open access for mobile network operators to offer satellite connectivity to their customers. They say the satellite portion would come from a partner, rather than an operator-funded constellation.
Ookla lead industry analyst Luke Kehoe said SpaceX’s push into the U.S. mobile market has put operators in a defensive position. He said the European operators want to avoid becoming effectively mobile virtual network operators for satellite coverage, selling someone else’s service on someone else’s terms. That is the commercial tension: mobile companies want a role in satellite service, while the constellation may belong to a separate partner.
Kehoe also cautioned that spectrum rights and ground infrastructure only go so far when a separate partner controls the constellation. The letter leaves the crucial partner choice open, so this is a bid strategy taking shape, not a sovereign satellite network already built.
Away from spectrum maneuvering, aboutamazon.com reported that Amazon plans to invest more than €16 billion in Germany in 2027. The company says the investment spans data centers and artificial intelligence infrastructure, satellite connectivity through Amazon Leo, logistics projects and Prime Video content.
Amazon says €4.8 billion of the planned investment will go toward expanding the AWS Europe (Frankfurt) Region in 2027. That cloud spending is part of a broader package, rather than a figure for Amazon Leo alone.
The satellite piece sits alongside infrastructure with a clearer immediate business purpose: Amazon says it is expanding cloud capacity and logistics, while also including high-speed satellite internet in the announcement. For space, the key is that this is a planned investment across several businesses, not a separately stated Amazon Leo budget. The announcement gives the service a place in the company’s Germany plans; it doesn’t give a standalone price tag for that part.
And on government procurement, Payload reports that EraDrive won a $13M Department of Defense award under which the Space Force will buy an undisclosed number of Era-Node autonomy modules. Era-Node is a vision-based module intended to let satellites carry out autonomous operations; the award is described as direct procurement funding through the Accelerate the Procurement and Fielding of Innovative Technologies program.
Lawrence Robertson, the Air Force’s lead for space experiments, told Payload that working with the APFIT office and NASA Ames got EraDrive selected and on contract within the same fiscal year. The award is meant to move new capabilities into procurement, rather than fund research and development like SBIR and STTR awards.
There’s a meaningful distinction between the module’s development and its flight record. Payload says EraDrive has yet to fly the fully integrated Era-Node module in orbit, while nearly all of its components and software have flight heritage. Over the past two years, the company has flown at least seven experiments of its Era-Core autonomous software aboard NASA’s Starling satellites. Those experiments demonstrated identifying and tracking moving targets and cueing other satellites to adjust their position.
I like the specific procurement mechanism here, but the operational proof still has to come from the integrated module in orbit. The award is a step toward buying capability, with its quantity undisclosed.
That's the rest of the rundown. Now, the story that deserves the long look. This is about how close approaches in orbit become a security question when the spacecraft being approached is commercial. Breaking Defense reports that Russia’s Cosmos 2612 maneuvered around ICEYE-X36 between October 15 and 19. A rendezvous and proximity operation, or RPO, means one spacecraft deliberately moves close to another.
LeoLabs said Cosmos 2612 “conducted a deliberate series of maneuvers toward ICEYE-X36,” shifting between positions ahead of and behind the commercial satellite. Breaking Defense says LeoLabs put the closest approach at 500 meters. That figure is the reported LeoLabs estimate; the central point in this account is a sequence of maneuvers, not a single pass.
Adam Marsh, LeoLabs’ vice president for technical solutions, told Breaking Defense this was a first-of-its-kind RPO. “This is the most advanced and potentially dangerous uncooperative RPO we’ve observed,” he said. Uncooperative means the spacecraft operators aren’t coordinating the close approach. That raises the stakes because the maneuvering spacecraft’s intentions can’t be settled simply by pointing to a planned joint operation.
Victoria Samson, chief director of Space Security and Stability for Secure World Foundation, said the new element was an uncoordinated close approach involving a commercial satellite. She told Breaking Defense: "What is new is that I don’t think that there has ever been an uncoordinated RPO that was close. Also, in these earlier cases, the satellite that was being approached was a USG satellite; obviously in this case, it was a commercial satellite."
LeoLabs’ analysis described a string of actions: Cosmos 2612 departed on a controlled trajectory, matched ICEYE-X36’s orbital plane, closed from long range, adjusted speed and altitude, repositioned ahead of and behind the target, remained nearby instead of making a simple flyby, and made repeated small maneuvers. The orbital plane is the path a satellite follows around Earth; matching it can let one spacecraft move alongside another. The sequence matters because it suggests controlled positioning around a specific spacecraft, rather than a one-time crossing.
Breaking Defense also reports that space watcher Marco Langbroek said in a blog post that Cosmos 2612 began the mission on September 30 and undertook maneuvers he described as “clearly designed” to catch up to ICEYE-X36. That is Langbroek’s characterization; the tracking account from LeoLabs independently describes maneuvering around the satellite.
The possible connection to Ukraine is important, but it has to stay qualified. ICEYE first announced an agreement with Ukraine in 2022 to provide synthetic aperture radar imagery through a dedicated satellite, but has never publicly identified which specific satellite was provided. Samson said ICEYE-X36 may be collecting data used by Ukraine, although that has not been publicly confirmed. SAR, or synthetic aperture radar, can produce images using radar rather than relying on visible light. Clayton Swope, deputy director of the Aerospace Security Project at the Center for Strategic and International Studies, wrote that Cosmos 2612 should be viewed as a likely threat given that ICEYE “supports Ukraine” in its effort to repel Russia’s 2022 invasion.
But the key uncertainty isn’t whether LeoLabs observed a deliberate sequence; it’s what that sequence means for risk and response. Swope wrote: Given Russia’s history of testing on-orbit weapons, policymakers should assume Cosmos 2612 could take an action that threatens the commercial satellite. But the risk extends beyond just one satellite. A Russian counterspace activity in the vicinity of Western satellites should be assessed within the context of aggressive Russian gray zone activities targeting U.S. and European interests.
That is a call for policymakers to treat the approach as a potential threat, not evidence that an attack happened. The distinction matters: a capability to inspect, shadow or potentially interfere with another spacecraft is not the same as proof of interference. LeoLabs’ analysis says the observed tactics could be used for those purposes; the report doesn’t say Cosmos 2612 actually interfered with ICEYE-X36.
There’s a second complication in the spacecraft’s national and commercial status. ICEYE-X36 is operated by ICEYE US and was launched from the United States in 2024, Breaking Defense reports. Samson said that makes it a U.S. satellite, or at least one for which the United States is the launching state. Yet the specific link between ICEYE-X36 and imagery provided to Ukraine remains unconfirmed. Those are separate questions: who has responsibility connected to the satellite, and what information it may be collecting.
Samson also asked why the U.S. government had been silent on the matter. That is a pointed question from an expert in space security; it isn’t evidence that the government has taken no action. The reporting gives no on-the-record government account of coordination, purpose or risk. For you, the public uncertainty means the tracking data can establish the closeness and pattern of movement, while the political response and the mission’s specific connection to Ukraine remain unsettled.
I think the strongest conclusion is narrower than the most alarming one: repeated, controlled maneuvering near another spacecraft is a serious security signal even when we can’t establish intent or confirm what ICEYE-X36 was doing for Ukraine. I’m confident about the importance of that distinction, and less certain about what response is warranted without an account from the operators or government. If an official explanation or clearer evidence of interference emerges, that would materially change the assessment.
I also think the commercial status is the consequential change in the story. Samson’s point is that previous close approaches she discussed involved U.S. government satellites; this case involves a commercial spacecraft. That means the question reaches beyond military hardware and into the safety and operating environment of companies providing services with potential national-security value. We shouldn’t convert that into a claim that a collision or attack occurred. We should take seriously that a commercial satellite can become part of a geopolitical contest without its role being publicly established.
Time for the Hype Check. My substance score is 7 out of 10: the tracked maneuvers and named experts make this a substantial warning, while the strongest limit is that intent, interference and ICEYE-X36’s specific use remain unconfirmed. The stake is a close approach to a commercial satellite, and the evidence leaves the risk visible but the response unresolved; if these maneuvers continue, commercial operators and the governments responsible for protecting their interests bear the immediate pressure.
Follow Space Stakes wherever you listen, and join us as we track what governments, operators and companies actually do with these risks. This has been Space Stakes, an AI-voiced podcast, created and built by a real human using today's cutting-edge technology. Nothing you heard on this show is financial advice. I'm Brian Lampert, and I'll catch you all tomorrow — take care!
Watching on YouTube? Hit subscribe, and tomorrow's briefing will be waiting for you. I also host Concrete Compute: a daily briefing on the AI buildout. The datacenters, the megawatts, and who actually pays for them. Find it wherever you get your podcasts.