Subscribe
Share
Share
Embed
Chapters
00:00 Today's headlines
00:40 SpaceX Starfall capsule's second flight
02:33 Space Force plans wider jammers
03:05 NorthStar, Maritime conditional approval
04:10 Rubio denies Washington ordered Starlink slowdown
07:13 Accountability for a commercial network
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.
Today on Space Stakes: Ukraine says battlefield Starlink limits looked deliberate, while Washington denies ordering them — so who can control a commercial network when a military depends on it? Before that, in the headlines: SpaceX's Starfall capsule is set for another return-vehicle demonstration, JAXA names a launch date for its Mars-moons mission, and the Space Force is planning wider satellite-jammer deployment. Welcome back to Space Stakes, your daily brief on the business of space. It's Sunday, October 18, 2026. Let's get into it.
A capsule built to bring cargo back from space is scheduled for another ride. Starlust reports that SpaceX's Falcon 9 is scheduled to lift off from Cape Canaveral Space Force Station in Florida for the Bandwagon-5 rideshare mission when the one-hour window opens at 6:30 am ET. SpaceX said on X that teams had encapsulated the 32 payloads ahead of the launch.
The mission is also the second flight of Starfall, SpaceX's return capsule. Starlust says the first Starfall mission launched on June 23 this year, and the capsule splashed down about 700 nautical miles off the U.S. west coast and was recovered by a SpaceX team. This next demonstration is intended to test a vehicle that can carry experiments and manufactured payloads back through Earth's atmosphere. The capsule isn't designed for human spaceflight.
There's a real business question inside that compact capsule: can return from orbit become routine enough to support research and manufacturing? Starlust says SpaceX has described the vehicle as a way to enable affordable, routine access to the microgravity environment. That's the company's stated aim; this flight is still a demonstration, and the return-and-reuse capability has yet to be proven. You'll want to separate the promised service from what the vehicle has demonstrated so far.
The Falcon 9 booster is on its 19th flight, according to Starlust, and is set to land on the A Shortfall of Gravitas droneship in the Atlantic Ocean. That's a planned landing, not an outcome we can report in advance. For you, the useful marker is whether this second capsule flight advances the path from sending experiments up to bringing them back.
Japan's Mars-moons mission has its ride date. JAXA posted on X that Martian Moons eXploration, or MMX, aboard H3 Launch Vehicle No. A major planetary mission now has a date attached to its ride. That is the full update from JAXA's post on X, and the launch itself is still ahead.
Satellite jamming is moving into a wider deployment plan. SpaceNews posted on X that the Space Force plans wider global deployment of satellite jammers. A jammer interferes with a satellite signal, and the wording here describes a plan, not a completed deployment. SpaceNews reporting describes support for global deployments of as many as 56 systems with contractors hired to maintain and support them. For you, the business and security question is who builds, maintains and pays for that ground-based disruption capacity alongside the satellites themselves.
Conditional approval can open a financing door, but it doesn't mean a company is already listed. SpaceQ reports that Maritime Launch Services and NorthStar Earth & Space both received conditional approval to list on the Toronto Stock Exchange.
For Maritime Launch, SpaceQ says the shares jumped 17 per cent on Thursday, the day the company announced the approval, to 48 cents. The shares trade on Cboe Canada for now, and the company has not set a date for the move. NorthStar's shares jumped 30 per cent on Wednesday, then gave back the gain over the next two days, ending the week down 11.6 per cent in New York. SpaceQ says NorthStar has until Nov. 30 to meet the conditions.
So what's the practical significance? A Toronto listing could put NorthStar in line to join SpaceQ's Canadian Space Index, whose rules require a Canadian listing quoted in Canadian dollars that has been in place for at least 90 days. That's an eligibility pathway, not a guarantee of index inclusion. For both companies, the immediate development is conditional approval; the listing still has steps to clear. That distinction matters when a market move arrives before the underlying business changes.
The main story is control without a clear public explanation. Firstpost reports that U.S. Secretary of State Marco Rubio denied that Washington ordered a slowdown of Starlink internet service in Ukraine, calling reports of deliberate disruption "categorically false." The story is single-source, and we haven't independently confirmed the account.
Here's the distinction that makes this easier to follow: Starlink is SpaceX's commercial satellite internet service, while Starshield is a separate, military-oriented communications product. Firstpost says Rubio described Starshield as operating under a contract with the U.S. military, and said Ukraine does not currently have access to it. He said Kyiv had requested access to Starshield for deep strikes inside Russia.
The immediate dispute concerns Starlink, the commercial service. Firstpost says Rubio was asked whether the U.S. had a role in disruptions to Starlink in Ukraine. He said neither the White House nor the U.S. government had ordered internet speeds reduced. His explanation was that the slowdown "sort of happened," that he understood service had been restored, and that Ukraine was using Starlink for its drones.
Rubio also said he was unsure what President Volodymyr Zelenskyy had said, then disputed the suggestion that the slowdown was deliberate. Firstpost reports Zelenskyy's position as the opposite: restrictions on Ukraine's military use of Starlink appeared deliberate and not the result of technical problems. Those are competing official claims, and the account leaves the central technical question open: what caused the slowdown?
The distinction between the two services matters here. A statement about Starshield access doesn't itself explain what happened to Starlink, and a denial of a U.S. order doesn't establish the technical cause. Bloomberg's @business account posted on X: "Restrictions on Ukraine's military use of SpaceX's Starlink system appear to be deliberate and not the result of any technical problems, President Volodymyr Zelenskyy said on Saturday". That captures Zelenskyy's position as Bloomberg presented it; it doesn't independently settle the cause.
Now, the other side of the exchange as it appeared on X. Anton Gerashchenko's @Gerashchenko_en account posted on X: "US Secretary of State Marco Rubio said that Starshield is not available to Ukraine at the moment, that Ukraine has made a request to use it for long-range strikes on Russia, and \"I'm not sure Zelenskyy knows what he's talking about\"." And @RSA_Observer added on X: "Interesting. Rubio says Ukraine has no access at all to Starshield but only Starlink and that the White House has nothing to do with the Starlink slowdown - which Zelensky appears to still be complaining about." Those posts summarize Rubio's denial and the Starlink-Starshield split; they don't provide telemetry or other technical evidence either.
Firstpost also reports Rubio's remarks that Starlink was back up and running, based on his understanding. So the immediate service status, as he described it, is restored. But for a military relying on a commercial network, a restored connection is only part of the question. You also need to know who can change the service, what the cause was, and what operating rules or recourse apply when access changes.
Here's my read: the story is about accountability for a commercial network used in a military setting. Firstpost gives us one official account from Zelenskyy and one from Rubio, who denies a U.S. order and says the slowdown wasn't deliberate. Neither claim, as presented here, gives you a technical explanation of the event. I wouldn't name SpaceX, Washington, or a technical fault as the cause without evidence that distinguishes among them.
That leaves a practical question for you: if a military depends on a commercial service, what happens when the service changes? Rubio's denial narrows one claim — he says the White House and U.S. government did not order the slowdown — but it doesn't tell us what did happen. Zelenskyy's assertion that the restrictions appeared deliberate points in another direction, but it also doesn't provide the technical mechanism in this account. That is why the disagreement matters beyond the wording of either statement.
The Starlink-Starshield distinction sharpens the issue. Ukraine's use of commercial Starlink for drones is described in Rubio's remarks; Firstpost says Ukraine does not currently have Starshield and has requested access to it. Those are separate products, with separate access arrangements. Treating them as interchangeable would blur the specific question at hand: who had authority over the Starlink service during the slowdown, and what explains the change?
My view is that a frontline military's reliance on a commercial network deserves clear operating expectations. That's my judgment, not a finding about who caused this disruption. The evidence in this account supports caution, not a culprit. The best way to make the story more concrete would be a technical explanation of the slowdown and restoration, alongside a clear account of who can make service decisions and what notice applies. Without that, the public is left comparing official statements while the network itself remains central to the dispute.
And there's a larger business point: commercial space systems can become critical infrastructure before the public has a clear picture of their limits or accountability. That doesn't make commercial service inherently unreliable, and it doesn't prove government control. It does make transparency around service changes important when military users rely on the connection. The question isn't whether private networks can serve a military; it's what commitments and recourse exist when service changes under pressure.
Time for the Hype Check. I give this story a 4 out of 10 on substance: the competing claims are clear, but the cause and the control mechanism remain unresolved. The next useful development would be a technical explanation from SpaceX or evidence that clarifies whether any government direction was involved. If those details emerge, they could change this read; for now, Ukraine's forces bear the operational uncertainty, while SpaceX and Washington face the credibility test.
If this kind of careful look at who controls the infrastructure behind space services is useful, 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 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.