Streetwise Professor

The evidence for SpaceX’s vital and unilateral role in (a) the Russian intercept of the ICEYE X36 satellite (which supports Ukrainian deep strikes into Russia) and (b) throttling the white-listed Starshield terminals Ukraine uses to defend against attacking Russian drone waves is massive, and nigh on indisputable.

When reports first broke that COSMOS 2612 had tracked and cut off ICEYE X36, R (aka @LibertyLynx) immediately suspected that the Russians did not have the tracking capability to pull that off on their own, suspected SpaceX involvement, and built an orbital model to test the theory. We then ran parallel models to cross-check the results, and the attached brief lays out the case in deep, and very technical, detail. It is based on the best and most complete publicly available information, including information produced by SpaceX, which is particularly damning

In brief, to recapitulate, on 16 October 2026 the Russian COSMOS 2612 sprinted from hundreds of kilometers away from ICEYE X36 and stopped on a dime within a few hundred meters of the US/NATO satellite. The likelihood that it could have done this on its own is near zero. Moreover, SpaceX was the only entity with the information and power to permit this intercept.

Maybe the brief will cause MEGO. But an animation (also created by R) that incorporates the information is an eye opener.

When I first viewed the video it reminded me of a football sweep play, with the Russian satellite in the role of a running back following the lead block of Starlink 35856, which pinned ICEYE X36 in place, allowing COSMOS 2612 to hit the hole right next to it.

Could have been a coincidence, right? Or the Russians just got lucky, eh?

Almost certainly not.

First, the Russians would not have had the information to guide COSMOS 2612 with that degree of accuracy, especially if ICEYE X36 had the ability to maneuver (more on that later because it is crucial). Russia has no space-based tracking assets, and relies on ground-based systems which are blind for 8-10 hours (due to the earth’s curvature). Further relying on COSMOS 2612’s onboard sensors limited range would have resulted in a miss of over 100km if ICEYE X36 had engaged in a brief avoidance burn.

But there was no burn. Why not? That is the central question here, the answer to which is particularly damning.

In response to an attempted approach in June, ICEYE X36 did engage in successful evasive maneuvers. Don’t believe me? How about ICEYE’s CEO, Rafał Modrzewski, who explicitly confirmed on the record to Reuters that ICEYE actively maneuvered its satellite to evade the Russian spacecraft, and that Russian maneuvers followed. Moreover, we have confirmed this in the data: independent reconstruction of all ~3,600 public Space-Track element sets explicitly verified X36’s maneuver on 25-26 June.

So why in June, but not in October? Because it couldn’t, that’s why. And why not? Because it was pinned. By whom, and how? By SpaceX, exploiting its unprecedented control in space, courtesy in large part to FCC regulations.

In brief, SpaceX issued a collision alert to ICEYE X36 for Starlink 35856, based on an assertion that ICEYE X36 would be within .401 kilometers of Starlink 35856. Under FCC Condition 16–negotiated with SpaceX lawyers–this collision alert obligated ICEYE X36 to eschew any maneuvers. In other words, the alert fixed it in place, thereby enabling the COSMOS 2612 to engage in a braking maneuver that put it right beside the American satellite.

Damning fact #1: SpaceX’s own documentation demonstrates that the collision alert was unwarranted and unnecessary, because in fact the distance to Starlink 35856 was 4.8 to 5.0 times greater than the claimed .401 km. Based on the correct distance, no alert was needed.

Damning fact #2. Starlink satellites are known for their autonomous collision avoidance abilities. If there was a genuine .401-meter collision risk, STARLINK-35856 could have—and normally would have—autonomously pulsed its thrusters to clear the corridor. Instead, SpaceX withheld that autonomous maneuver. By choosing not to move, they intentionally shifted the legal burden entirely onto ICEYE via FCC Condition 16. (Why should SpaceX insist that a vital US intelligence satellite yield right of way to one of its many satellites that primarily provide prosaic Internet connectivity?)

In brief, SpaceX engaged in acts of commission and omission without which the intercept would have been impossible.

To add to the disturbing implications, consider the following. The Russians would have known that it would have been futile to attempt an intercept if-as had been demonstrated in June-ICEYE X36 would be free to maneuver. The sprint and braking maneuvers were costly, and it would have been irrational to engage in them if the probability of success was nil. The only way the probability of success would have been sufficiently high to justify the cost would have been if the Russians were highly confident that ICEYE X36 would be pinned. And how could they have known that?

The plausibility of coincidence or luck vanishes when one considers the fact that the intercept was contemporaneous with the throttling of Ukraine’s Starshield terminals. These were whitelisted terminals, used to guide Ukrainian drone defenses. Once a Ukrainian drone exceeded the speed limit imposed by SpaceX, its connection was dropped, making it stupid. Note that Ukrainian drones operating within Russia were already limited to much lower speeds.

And by the way, when provided this information, Grok agreed that there was no coincidence here comrade, and assigned a less than .01 percent probability to this being a random coincidence.

Musk’s shifting stories also belie any innocent explanations. At first he said that the decision to throttle Ukrainian drones was a WH decision, because Starshield is operated by the US government. But that explanation exploded later when Hegseth and Rubio both stated that SpaceX had acted unilaterally pursuant to its Terms of Service with the US government. Musk later embraced the ToS story, claiming that they prevented Ukraine from using Starshield to kill anyone, and that Ukraine had violated this provision.

They just started doing that in October, Elon? Were you shocked! Shocked! to learn that Ukraine was using Starshield/Starlink for military purposes?

Interestingly, among the people whom Musk claimed he was protecting were “poor Russian conscripts.” Putting aside the fact that Russian troops are not conscripts (although they are often shanghaied into contract service), said Russian troops are killing Ukrainians. And further, by disabling the terminals, Musk increased the lethality of Russian strikes against Ukraine and Ukrainian civilians in particular.

Interesting to know Elon’s solution to this particular trolley problem.

The main point here is that SpaceX played a central role in compromising both Ukraine’s defensive and offensive capabilities at the precise same time. And in explaining the former, he engaged in a virulent rant against Zelenskyy. In that context, any innocent explanation of the intercept crumbles.

The implications of this go well beyond the events in Ukraine, as the brief discusses in detail. Unlike legacy defense contractors, including those involved with highly classified space and satellite operations, SpaceX operates on a “CO-CO” model: contractor owned, contractor operated. This contrasts with the legacy GO-GO model, in which the government buys, owns, and operates what the contractors produce.

The contractor-SpaceX here-provides services according to a contract: the “Terms of Service” that appear so notoriously in the foregoing. It is clear that these ToS provide tremendous discretion to SpaceX to make decisions that have grave national security implications. It is also clear that these it is willing to exercise these powers in ways that are inimical to US security interests.

And don’t think this is the only time. During the Iran War SpaceX invoked its ToS to prevent the use of Starlink to mount LUCAS drone strikes against Iran. Until, that is, the Pentagon agreed to pay a 4x greater fee to SpaceX. Which reminds me of the old Churchill line: Now we know what you are. We are just haggling over price.

This is all the more disturbing given the greatly expanded role of SpaceX, and Grok in particular, in every aspect of US military operations. It is sickly ironic that Hegseth and his tech chief Emil Michael declared Anthropic a national security risk for demanding that it retain a veto over the use of Claude given that they have supplanted it with a contractor who has used such a veto to the detriment of US security interests.

In the present instance, how bizarre is it that the US military would enter into a contract which allowed its counterparty to veto decisions to kill people? After all, the military’s job is, well, to kill people. The decision to do so is vested in Constitutionally established authorities operating subject to US law. It is not vested in Elon Musk, and it is incomprehensible that the US government has entered into contracts that grant him that authority.

This is a classic problem in transaction cost economics. SpaceX provides very specific assets (specific in the technical economic sense) to the United States government, and the Department of Defense in particular. The specificity of these assets gives SpaceX incredible power to hold up the government. Contracts should be crafted to limit this holdup power. Instead the Pentagon has enabled it.

GOGO is the default organizational response to holdup problems. Given the acute severity of the holdup problems posed by SpaceX, unless the government can find a way to write much better contracts with it, it should move back to that model.

But hot-from-the-presses news suggests that this is a vain hope, at least under the Hegseth Pentagon. The Defense Intelligence Agency just released “Challenges to Security in Space: Congestion, Competition, and Cooperation.” It relies on a Russian propaganda site (topwar.ru) and TASS (!) to hype Russian capabilities (namely its ground-based Krona surveillance complex).

The reliance of this document on a trash Russian military site renders it little better than the Steele Dossier, or the hack job on Russian election interference that the outgoing Obama administration cobbled together in January 2017.

Moreover, the timing is rather, shall we say, odd. Lo and behold, the day after Elon offered his fourth explanation for throttling Ukrainian drones, specifically that if he didn’t Russia would target Starlink satellites, the DIA drops a report citing topwar.ru to warn of Russian threats to American satellites. A coincidence, surely. If you believe that . . .

But there are indications that American dogs are fighting under the carpet–specifically the State Department and the Pentagon. Rubio was clearly displeased at the Ukraine drone throttling, and the fact that this was a Musk decision. The State Department was also infuriated by the intercept, taking a complaint to the UN. And Rubio just recently fired one of Musk’s operatives. So we must hold out hope that Rubio (whom Trump surely holds in greater esteem than Hegseth, and hopefully Musk) will be able to put a stop to this madness.

Yesterday’s post presented the evidence for and the implications of Elon Musk’s throttling of Ukraine’s Starlink/Starshield access. Since then, additional evidence makes this an established fact. Most notably, reporting in the WSJ that Trump (on bended knee?) asked Musk to release his grip (and WSJ reporting today that uneven Starshield restrictions are still persisting even after Trump’s call). When asked about it, the normally no-filter Trump declined to answer. Mark that down as confirmation.

But it gets better! Today’s brief, co-authored with @LibertyLynx (who originated, architected, and built the entire SGP4 orbital, FCC regulatory, and corporate forensic investigation from the ground up), demonstrates the near certainty that in addition to undermining Ukraine’s defensive capabilities (where the 130 to 160 km/h speed cap cut Ukrainian Unmanned Systems Forces validated target output by 23.0%), Musk/SpaceX compromised, or at least threatened to compromise, Ukraine’s offensive capability. Specifically, its capability to attack refineries and other targets within Russia.

The brief is extremely detailed and extensive, so here’s the TLDR version (though I do encourage reading it). Ukraine relies on Starlink/Starshield to control drones for operations at the front (and the logistical zone) and counter Russian aerial attacks. It does not use Starlink for reconnaissance and targeting of strikes deep inside Russia. For that it relies on Synthetic Aperture Radar (SAR) imagery from the ICEYE-X36 (NORAD 59103) satellite, operated by ICEYE US (the U.S. subsidiary of a Finnish company, operating under FCC license S3165).

Beginning on 15 October, within 48 hours of the Starshield throttle, a Russian inspector satellite, COSMOS 2612 (NORAD 68762), maneuvered to within less than a kilometer of X36 (closing to 0.76 km in the public catalog, and within a few hundred meters per optical trackers). And here’s the thing. Russia relies on ground-based radars that can only observe an orbiting satellite like X36 for narrow time windows (leaving 6 to 11 hour tracking gaps), and which do not allow it to track X36 continuously and with sufficient precision to arrange an intercept in which COSMOS 2612 compressed 364.3 hours of natural orbital drift into a 25.5-hour sprint (a 14.29x closure compression from 425 km away, cutting separation by 382.7 km relative to its pre-sprint orbit), braked, and then remained within a kilometer for more than 12 hours before moving away. (And across every Russian maneuver transition, the public Space-Track catalog lagged behind by 19.4 to 22.7 hours.)

Who can provide that real-time information? SpaceX. At the exact time COSMOS 2612 began its sprint (15 October at 04:15 UTC), X36 sat inside a 401-meter public collision alert with SpaceX’s STARLINK-35856 (NORAD 67013, where SpaceX’s private operator ephemeris diverged from public data by 15.37 to 30.13 km while carrying a 2.862 km 3D position uncertainty). Because X36 only has one trajectory, this overlapping Starlink alert pinned X36 in place—preventing it from executing a 0.5 km evasive altitude drop as it had in June (which generates 71 km/day of drift and exits a 3 km Russian braking box in 61 minutes), while requiring X36 under FCC Condition 16 to coordinate its trajectory with SpaceX. Under SpaceX’s Space Safety Terms of Service (Appendix A and Section 4(b)), committed maneuver trajectories uploaded to SpaceX are exposed to third-party sharing with a $500 liability cap (Section 10). Moreover, SpaceX tracks the 540 to 550 km orbital shell at 10 to 15 minute intervals using its 31,000 Stargaze cameras—and conveniently onboarded Chinese operators to its Space Safety platform on 6 and 16 October. Again, with its ground resources alone, Russia would have been flying COSMOS 2612 blind.

No other entity has all five of these capabilities. The intercept would not have been possible without these capabilities.

Nice little satellite you got here. A shame if anything happened to it. A threat that could only have been delivered with the help of SpaceX/Starlink/Musk. I further note that Russia has not delivered a similar threat to any Starlink asset while Tesla’s Q3 10-Q (filed 30 September) discloses $5.966 billion in rolling Chinese working-capital debt maturing between October 2026 and September 2027 and explicitly admits “presumed significant influence” over SpaceX through their shared CEO.

Goldfinger famously said: “Once is happenstance. Twice is coincidence. Three times is enemy action.” The simultaneous throttling of Ukraine’s defensive capability and compromising/threatening of its offensive capability, the first definitively attributed to SpaceX and the second solely within SpaceX’s capability, makes plain that Musk has acted against Ukraine and for Russia. Enemy action, indeed.

SpaceX’s culpability here is indisputable. The only open question is whether Musk acted on his own, or in connivance with the administration/Pentagon. And just as was the case with yesterday’s post, both alternatives are disturbing in their own way.

Trump’s, Rubio’s, and Hegseth’s claims that the administration had nothing to do with throttling Starlink may or may not be true. Trump’s asking Musk pretty please to turn it back on could be genuine, or it could be Kabuki. Again, neither alternative is good. If the President of the United States is reduced to a supplicant, and Musk has the unilateral authority (shielded by commercial Terms of Service) to make decisions with such vital national security implications, and perhaps to do so in cooperation with American enemies, we are in a very bad place. Especially given how embedded SpaceX currently is within the Pentagon as we head toward Round Two with Iran.

The on again, off again battle between Donald Trump and Volodymyr Zelensky is back on, and in a big way. The trigger for this most recent outbreak was news that somebody throttled Ukraine’s Starlink/Starshield link, limiting the speed of Ukraine’s fast drone interceptors which are essential to countering Russian jet-powered drones. As documented in the attached brief/strategy memo (prepared by @LibertyLynx) Russia responded by utilizing jet drones more extensively, and delivering more effective strikes on Ukraine. Against civilian targets in Ukraine, I might add.

It’s rather remarkable how rapidly Russia recognized and responded to Ukraine’s degraded capabilities.

As the document also describes in detail, this also has implications for US national security. Most notably, it works to the advantage of Russia in its forever war against Ukraine. But that’s not all. It forces Ukraine to substitute high end interceptors for low end ones, further depleting already nearly barren magazines–which creates a call on stocks from US allies and perhaps the US itself. Given the extravagant expenditure of weapons in the Iran War, our cupboard is increasingly bare, and we have nothing to spare.

Note that I said “somebody throttled” Starlink/Starshield. That phrasing was deliberate. Because we don’t know who did so. There are two possible answers, each deeply disturbing in its own way.

The first answer is that Trump made the call. Elon Musk says it was the USG, meaning Trump. Trump denies it. Rubio denies it.

Why would Trump do this? His animosity towards Zelensky is well known, and he has long been impatient with Zelensky’s resistance to a peace deal. With the midterms approaching, and fuel prices high, Trump is even more desperate for a deal. He may therefore believe that pressuring Zelensky will break the deadlock and allow him to announce peace in our time.

But handicapping Ukraine’s defenses will not achieve this outcome, especially not in Trump’s time frame. It is fantastical to imagine that such a deal could get done in the few days prior to the midterms, and even if a deal were to be done tomorrow its impact on energy prices would be (a) modest, and (b) delayed to well after the election. As much as Trump fulminates to the contrary, energy prices are driven first and foremost by the situation in the Gulf. The loss of Russian refined and crude supplies due to sanctions (which would presumably be lifted as part of a deal) and Ukrainian attacks is at most an aggravating factor.

It is also fantastical to think that Putin is just standing by waiting to do a deal, and that Zelensky is the only obstacle to one. Indeed, measures that weaken Ukraine’s defenses will only embolden Putin to continue to fight, figuring that he can gain more against a weakened Ukraine and perhaps even achieve his goal of conquering additional territory, and perhaps the entire country. Putin will deal only if he thinks defeat is inevitable. Giving him hope of something he can call victory will only prolong the war.

So if the rationale for kneecapping Ukraine is to facilitate an end to the war in days, followed forthwith by a sharp drop in energy prices, all in time to rescue the Republicans from an electoral rout, it is beyond delusional.

And it’s also politically stupid. This–and Trump emissary Witkoff’s obsequious behavior towards Putin, and Trump’s bizarre statements about how Russia isn’t doing anything bad in Ukraine–has generated tremendous political blowback, and has played into the narrative that Trump is Putin’s puppet. So if anything, it is politically counterproductive from the perspective of the midterms in particular.

But maybe the administration’s denials are in fact truthful, and Elon Musk is in fact responsible. Think about that for a minute.

Pete Hegseth (the primary author of the failed strategery in the Gulf) says that SpaceX throttled Starlink/Starshield because Ukraine violated “Terms of Service.” What? They didn’t read the fine print and just clicked “accept”? Or they just decided in early-October to do something different that violated the ToS? Or SpaceX changed the ToS? Or Ukraine refused to cease and desist from violating the ToS and SpaceX lost patience?

What changed in the last few weeks to trigger this intervention? The “ToS” excuse begs every question that matters.

For his part, J. D. Vance said it is totes understandable that Musk decided to intervene:

JD Vance on Starlink:

Elon Musk runs a private corporation, and I think it's completely understandable that he doesn't want to get in the middle of what is a war between two state actors without the United States government effectively directing him on what to do.

I don't think… pic.twitter.com/rm9dS65ElE

— Clash Report (@clashreport) October 22, 2026

So much wrong here. For one thing, SpaceX has been “in the middle of a war between two state actors” for several years now. Indeed, SpaceX has been instrumental in staving off Russia’s invasion, both by providing Starlink to Ukraine and denying it to Russia. What would explain a sudden reluctance on its part?

Moreover, the throttling of Starlink/Starshield has impaired Ukraine’s defensive capabilities, not its ability to strike Russian territory. Denying Ukraine truly defensive capability is particularly twisted, and has already cost civilian lives. Musk somehow thinks that Ukraine defending itself is unacceptable? And just decided this last month?

And how is it remotely OK for the United States to grant Musk a veto over the employment of Starlink/Starshield? Since 2023, Starshield has been under contract with the US government to provide Starlink services in Ukraine. The Pentagon was not willing to grant Anthropic the right to withhold services when it disagrees with how the Pentagon was using its AI (excuse me, SI): have they granted comparable rights to Musk? If so, why? If not, how is he getting away with exercising such power without contractual sanction?

Or maybe he’s not, and the administration is lying and it made the call.

Given how deeply embedded in the Pentagon SpaceX is now (at the expense of Anthropic, in particular), these events have disturbing implications that go far beyond Ukraine. Does the USG negotiate “terms of service” with SpaceX that give it the ability to throttle services to the Pentagon (e.g., throttling Grok) at its whim? Or can Musk exploit contract incompleteness to make unilateral decisions that impair US national security? Or is it difficult to enforce contractual terms against him because there is no alternative over a horizon of weeks or months? Under any of these possibilities, a mercurial, deeply untrustworthy, and highly conflicted individual has far too much power over American national security.

In earlier posts/briefs @libertylynx and I analyzed the holdup problems SpaceX/Grok/Musk poses. If it is indeed the case that the administration did not order the throttling, and Musk/SpaceX “understandably” did it on their own, we have been given a taste of how dangerous the holdup potential is.

There is no good alternative here. Either Trump and his administration made a decision based on delusional diplomatic, political, and military logic, or a deeply untrustworthy megalomaniac (other than the president) has the ability to make unilateral decisions that have dire consequences for American national security.