Subscribe
Share
Share
Embed
Chapters
00:00 Today's headlines
00:41 Amazon's satellite network in Army test
01:19 Reflect Orbital bought two launches
02:49 Artemis III rocket: tanking test ahead
03:50 Spain's PAZ 2 funding timing changed
05:09 SpaceX accused of limiting Starlink
08:05 Who controls Starshield and its limits
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.
Who can change the speed of a satellite link used by Ukrainian forces — the company that operates the network, or the government that owns its military version? And when a connection helps guide drones, who carries the risk if it stops working? Before that, in the headlines: the U.S. Army tests Amazon’s satellite network, Reflect Orbital buys two launches, Artemis III hardware moves toward a pad test, and Spain shifts €65.8 million in satellite funding. Welcome back to Space Stakes, your daily brief on the business of space. It’s Thursday, October 15, 2026. Let’s get into it.
A battlefield test for Amazon’s satellite network: Aviation Week posted on X that the U.S. Army recently stress-tested Amazon’s nascent proliferated communications network — a growing group of satellites designed to provide high-speed connectivity to soldiers in the field. Aviation Week said the company announced the test on Oct. 13. That’s a test, not proof of an operational service, but it puts a concrete government use case in view. SpaceNews posted on X, in a headline, “Amazon Leo demonstrates satellite internet for U.S. Army.” The useful question now is what the Army learned from the demonstration and whether it leads to a defined service or contract.
Two dedicated launches, one unusual business idea: Reflect Orbital has bought two launches from India’s Skyroot Aerospace for mirror satellites intended to direct sunlight to selected places on Earth, Payload reports. One launch is on Vikram-1, which debuted in July and can carry ~350kg to low Earth orbit, the region closer to Earth where many satellites operate. The other is on the upgraded Vikram-1U, expected to fly its first mission in Q1 2027 and capable of carrying ~550kg to low Earth orbit. Payload says the launch costs and mission dates weren’t disclosed. The hardware is being purchased; the sunlight service is still a plan. Reflect’s larger concept is a constellation of ~50,000 mirrors, with proposed uses including extending solar-farm generation after sunset and lighting search-and-rescue operations or nighttime concerts. A single approved first mirror satellite, Eärendil-1, is a step toward that idea, not evidence that the full service is operating. Skyroot Aerospace posted on X: “Welcome aboard, @reflectorbital. 🚀 Two dedicated launches on our Vikram rockets will take their future spacecraft to orbit. Reflect Orbital builds mirrors that orbit Earth and reflect sunlight to chosen spots on the ground. Solar farms can generate power for longer, and rescue teams can find people in the dark. This is a milestone for India’s private space sector.” My read: two bought launches make the plan more tangible, while the customer proposition still has to work beyond a launch announcement.
NASA’s Artemis III rocket is taking shape, but the next milestone is a rehearsal, not a launch. NASASpaceFlight.com reports that both solid rocket boosters are fully stacked and all four RS-25 engines are installed on the core stage. NASA is preparing to mate the stage and boosters into a short stack, which will go to Launch Pad 39B for a tanking test — a practice run for loading propellant and working through launch procedures. The test is expected in the coming months. The Artemis III crew is also due to conduct its first full launch-day rehearsal at the pad, ahead of the mission’s targeted no-earlier-than June 2027 date. That phrase matters: it’s a target, with no earlier launch promised. There’s real hardware progress here, and the rehearsal is a practical step for the crew. Artemis III will remain in low Earth orbit and demonstrate docking and other operations with commercial lunar modules from SpaceX and Blue Origin. Those tasks are intended to reduce risks ahead of the first crewed lunar landing attempt on Artemis IV. The stack is advancing; the mission still has work beyond the rocket itself.
Spain has moved the timing of satellite-program funding, while keeping it within an existing loan. European Spaceflight reports that the government approved an early release of €65.8 million under Hisdesat’s €1 billion loan for the PAZ 2 radar-satellite program. The adjustment raises funding scheduled for 2026 from €179.8 million to €245.6 million and reduces the 2029 allocation by the same amount. The 2027 allocation of €182.9 million and the 2028 allocation of €213 million remain unchanged; the 2029 allocation falls to €206.3 million. The remaining €88 million is to be distributed over three years from 2030 to 2032. European Spaceflight is the sole outlet in this episode’s coverage of this funding change, and we haven’t independently confirmed it. The program is planned to deliver two synthetic aperture radar satellites, which create images using radar rather than visible light, to replace and expand Spain’s existing PAZ spacecraft. The satellites are expected to be operational by 2031. Airbus Defence and Space was selected as prime contractor in July 2025. The funding schedule has changed; by itself, that does not tell us whether the program is on schedule.
Here’s the main story: control of Ukraine’s satellite link is part of the battlefield. Via Satellite reports that a Ukrainian defense adviser accused SpaceX of limiting access to Starlink as Ukraine faced increased attacks from Russia. Elon Musk disputed the claim’s framing, saying limits on Starshield are set by the U.S. government. To follow the dispute, you need one distinction: Starlink is SpaceX’s commercial satellite service; Starshield is the military version that Musk says is owned and operated by the U.S. government.
Serhii Beskrestnov, who advises Ukraine’s Ministry of Defence on defense technology, said in a statement on Telegram on Wednesday that SpaceX had put a speed limit on terminals while in motion, applying to Starshield for speeds over 100 mph. He said, “Our defense forces were not given notice of this limit, and this has resulted in the disruption of a number of missions.” He added, “It is clear that this action cannot be a coincidence and is related to the current political situation.” That last sentence is Beskrestnov’s interpretation; the cause is disputed, and the episode’s reporting does not establish who initiated the restriction.
Why does speed matter? Ukraine uses Starlink in interceptors that defend against Russian Shahed jets, Beskrestnov said. He also described the consequence in stark terms: “In fact, by their actions, the partners are depriving us of one of the few chances to protect the country from Shahed jets.” NBC News reported additional instances of Starlink connectivity problems in Ukraine that disrupted drone control.
Musk’s statement, as reported by Via Satellite, drew a line between the two services. He said Starshield is owned and operated by the U.S. government, and that “Any limits on speed or usage are decided by the U.S. military and ultimately POTUS,” referring to President Trump. Musk did not confirm or deny whether restrictions on Starshield service exist. He said earlier this year that Starshield is owned by the U.S. government and “not under SpaceX control.” Those are distinct claims: ownership and control of Starshield, and the question of whether a speed limit was imposed and by whom.
Ukraine’s president, Volodymyr Zelensky, said on “Piers Morgan Uncensored” that Ukraine was asking for service to be switched on, and that he hoped the problem was a mistake or technical issue. “People will die, of course, if attacks will continue and if Starlink will not work,” Zelensky said. Via Satellite also reports that Russia launched ballistic missiles at Ukraine this week and that Zelensky said Ukraine had not received a warning from its partners, which President Trump disputed, according to CNN. The account does not establish that those events caused the connectivity restriction.
There is another network in the picture, but its role is not yet clear. Eutelsat told Via Satellite it continues to provide connectivity in Ukraine through its low Earth orbit and geostationary orbit networks, and said it is committed to resilient connectivity. The company did not elaborate on whether its OneWeb network could fill in if Starlink were turned off. That is the practical question beneath the ownership argument: what service is available to Ukrainian forces when a particular link is limited?
The control question matters because a satellite connection can be commercial infrastructure and a military dependency at the same time. Ukraine’s forces use Starlink in drone operations, while Musk says Starshield’s limits are decided by the U.S. military and ultimately the president. Those statements put the issue in sharp relief, but they don’t resolve this particular episode: who set the reported limit, what precise change was made, and what service is available to replace it?
Beskrestnov says Ukraine received no notice and that missions were disrupted. Musk says the U.S. government controls Starshield. Zelensky says Ukraine is asking for service to be switched on and hopes the problem is a mistake or technical issue. Those voices are describing different parts of the problem, and none of the statements in Via Satellite’s account confirms the exact decision path. The distinction between Starlink and Starshield is important, but it does not make the operational question disappear. If military users rely on a service, responsibility for changes needs to be legible to the people planning missions and to the governments paying for the capability.
Via Satellite also quotes Marc C. Lange, identified as a European defense adviser, from a separate story about Europe’s dependence on U.S. space technology for defense. Lange said, Ukraine’s deep strike campaign is running on American intelligence data and Starlink terminals. The moment one or both of these assets are not available to Ukraine anymore, that campaign ends. That is his assessment of the campaign’s dependence, not confirmation of what happened to the terminals in this episode. It does underline why the question reaches beyond a service setting: if an ally’s operations depend on a privately operated network, the terms of access and the chain of authority become part of the military capability.
And what does the alternative look like? Eutelsat says it continues to provide service through its low Earth orbit and geostationary orbit networks, but did not say whether OneWeb can substitute for Starlink if service is turned off. That leaves a real gap in the public picture. A second network matters only if it can deliver the needed connection for the actual mission; a company’s commitment to resilient connectivity does not answer that operational question.
My read is that this is a control-and-accountability story, with the Starlink-Starshield distinction at its center. Musk’s statement points to government authority over Starshield. Beskrestnov’s account describes disruption and a lack of notice. Those points can both be true without telling us who ordered the limit or what prompted it. I’d want a clear account of the decision, the service terms for military users, and what happens when a change affects active operations. The taxpayer question is equally concrete: what capability does a government customer receive, on whose authority can it be changed, and what alternative is actually available?
SpaceX has built a consequential communications network, and that achievement deserves recognition. The same importance raises the standard for clarity when military operations rely on it. That is my view, and it applies to any provider carrying a government customer’s mission. Does the request to restore service settle the dispute? No — the account describes Ukraine asking for service to be switched on, while the underlying decision and the precise limits remain unresolved.
Time for the Hype Check. My substance rating is 6 out of 10: the public statements establish a serious control dispute around a military-dependent link, but they don’t establish who ordered the reported restriction or its exact scope. The next useful evidence is a clear account of the decision and the service available to Ukrainian forces. When you see the next headline about a satellite network in a war zone, read for who controls the service and who can change it — the brand on the spacecraft doesn’t answer either question.
If this episode helped you make sense of the line between a commercial network and a military service, follow Space Stakes wherever you listen. 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 Quickly Quantum: a daily quantum computing briefing you don't need a physics degree to follow. The breakthroughs, the funding rounds, and how much substance is really under each claim. Find it wherever you get your podcasts.