Report: Musk ordered Starlink slowdown in Ukraine, then blamed it on Trump

Publication: Ars Technica - All content

Author: Jon Brodkin

Source published: 21/10/2026, 18:35:38 UTC

Briefing created: 21/10/2026, 20:46:48 UTC

Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 21/10/2026, 20:43:24 UTC.

Briefings

A Wall Street Journal report states SpaceX CEO Elon Musk ordered a throttling of Starlink speeds for Ukraine, a decision that rendered offensive drones ineffective. Musk claimed all military Starlink decisions are made by the US military and President Trump, but the report indicates he made the final call after criticizing Ukraine's attacks on Russian refineries. Trump denied ordering the restrictions, though he may have discussed the matter with officials before the decision. The decision came after both Musk and Trump criticized Ukraine for attacking Russian diesel refineries.

Key points

Elon Musk made the final decision to throttle Starlink speeds for Ukraine, overriding claims that all military decisions are made by the US military and President Trump.
The throttling capped speeds rendering offensive drones and interceptor drones virtually useless, causing panic in Kyiv and confusion inside the Trump administration.

Context

A Wall Street Journal report details SpaceX CEO Elon Musk ordering Starlink throttling for Ukraine, sparking panic in Kyiv and confusion inside the Trump administration. The decision came after both Musk and Trump criticized Ukraine for attacking Russian diesel refineries.

Limitations

The report cites unnamed US officials and people familiar with the matter, and Trump denied ordering the restrictions. Evidence is limited to the WSJ article, which does not specify the exact date of the decision or confirm the timing of any prior discussions between Musk and Trump.

Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 21/10/2026, 20:46:48 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.

View archived briefing on IPFS
bafybeiagco2qitptom7l2phe4w5k5uoep5veopww4gjbhyjxitw5oseeoa