What happened
On 14 October 2026, Ukrainian officials said SpaceX had throttled military-grade Starshield terminals without warning. Serhii Beskrestnov, an adviser to President Zelensky on defence technology, said terminals moving faster than about 100 mph (160 km/h) were cut off. He said that disrupted missions and could weaken interceptor units that counter Russian Shahed drones. "Our defense forces received no warning," he said, according to the Denver Gazette's report. He tied the move to tension between Kyiv and Washington over an energy ceasefire, calling it "no coincidence". That link has not been independently established.
Elon Musk answered on X that "Starshield systems are owned and controlled by the US government". He added that any limits on speed or usage are decided by the US military and ultimately the president. Al Jazeera reported that the White House neither confirmed nor denied this. Service was partly restored later that day, but the speed cap remained in place. Zelensky called the restriction "a big mistake" that would cost lives. Poland's foreign minister, Radosław Sikorski, wrote to Musk: "As your European customers, we are watching you." Poland pays for Ukraine's Starlink subscriptions, Reuters reported.
We do not yet know who made the decision. Either answer is a problem for Ukraine.
The case for the restriction
There is a serious argument for speed limits. Starlink terminals fitted to fast-moving drones can be used by an adversary too. In February 2026 Ukraine's Ministry of Defence worked with SpaceX to build a whitelist of verified terminals after Russian drones were confirmed using Starlink links over Ukrainian cities. Terminals used by Russian forces were cut off. Whitelist updates were then processed once per day. The Ministry of Defence said the whitelist keeps verified terminals running while Russian terminals are blocked. The Ministry's own guidance, as reported at the time, also said authorised terminals could operate only in stationary mode or at low speeds in motion. Speed-based controls are therefore a known tool for limiting hostile use of the network. A government that owns a system has a legitimate interest in deciding how it is used, and Musk's statement about who controls Starshield may be accurate.
Why that does not answer the problem
The February whitelist was a transparent, negotiated rule. It was announced by Kyiv, built with a vendor, and given published verification channels for military units, civilians and companies. The October episode was the opposite: unannounced, unexplained, and landing on the same days as heavy Russian strikes on Kyiv. Zelensky said afterwards, according to Al Jazeera, "It was not a technical problem; it was the will." A restriction that may be reasonable in principle still fails as policy if the people operating under it learn about it when their drones drop out.
The larger point is that a connectivity layer carrying live military operations has no service-level commitments that Ukraine can enforce. Its terms are set by a private company, which says they come from a foreign military, which answers to a foreign president. Each party can point to another. In 2022 Musk ordered Starlink coverage shut off in parts of Ukraine during a counteroffensive, causing hours of disruption, as the Denver Gazette's report recalls. In 2025 he warned that the front line would collapse if Starlink were switched off. He later said he would never use it "as a bargaining chip". Three episodes in four years is a pattern, whatever the intent behind each one.
Scale makes it a structural dependency
The Kyiv Independent reported that Sikorski had previously cited about $50 million as the cost of providing half of Ukraine's 42,000 Starlink terminals. That figure comes from Sikorski, not from an audited source, and the outlet says it is unclear exactly what the later $50 million per year reference covers. Even as a rough guide, it shows two things. A substantial share of Ukraine's terminals is paid for by a NATO ally's treasury. And the service Poland funds is delivered on commercial terms that Warsaw cannot change. In August 2026 Sikorski threatened to rethink that payment when Poland was left out of Starlink's European roaming area. SpaceX reversed the exclusion within a day. That reversal shows how much these arrangements depend on leverage and public pressure rather than contract rights.
What proportionate policy looks like
This is not an argument for banning foreign satellite services or nationalising connectivity. Starlink is the reason Ukrainian communications survived the first weeks of the full-scale invasion, and an innovation-friendly policy should reward that. The goal is to make dependence tolerable while it lasts.
- Written terms for military use. Governments that fund subscriptions, including Poland and Ukraine, should require notice periods, a defined escalation path and a named responsible authority for any change to speed, geography or usage rules.
- Clarity on who decides. If the US government sets Starshield limits, it should say so on the record. If SpaceX does, Musk's account is wrong. Ambiguity benefits only the two parties who can each deny responsibility.
- Real alternatives. European and Ukrainian planners should keep funding multi-vendor capacity, including other low-earth-orbit constellations, mesh radio and fibre. Redundancy is cheaper than discovering the dependency mid-operation.
- Keep the security controls. Whitelisting and anti-misuse measures are legitimate. They are defensible when they are published and tested, and they are not when they appear as an overnight surprise.
Bottom line
A cap reported at 100 mph could be a defensible security measure, a bargaining move or a mistake. Which one it was cannot be settled from public information. What the episode does settle is that Ukraine's drone war runs on a service whose rules can change without notice and whose decision-maker cannot be identified with certainty. Better terms and more redundancy would address that without punishing the technology that has kept Ukraine connected.