SpaceX restricted the operation of the Starlink satellite communication terminals used by the Ukrainian military on the night of October 13–14, UA.News reported. [E10]
Military-grade Starlink service used by Ukraine was placed under a new restriction, Reuters reported. [E2]
"While moving at speeds above 160 km/h, the connection began to disappear," UNN reported. [E7]
Serhiy Beskrestnov, an adviser to Ukrainian President Volodymyr Zelenskyy on military technology, wrote on Telegram: "Our defence forces did not receive a warning about this limitation and this led to the disruption of several missions," Euronews and TVP World reported. [E1][E5] The Jerusalem Post reported that he added: "It is clear that this action is not coincidental and is related to the current political situation." [E6] UA.News, citing Serhiy Sternenko, an activist, volunteer, and former advisor to the Minister of Defense, reported several important missions were disrupted. [E11]
A source in the 7th Rapid Reaction Corps confirmed disruptions to Starlink operations, Reuters reported. [E3][E4]
Ordinary satellite communications terminals are currently working, UNN reported. [E9]
UNN reported Sternenko saying it is likely that SpaceX took such measures at the request of the Trump administration. [E8]
Ukrainian President Volodymyr Zelenskyy said on 4 October that Ukraine is working on a satellite system of its own, something similar to SpaceX's Starlink, Interfax-Ukraine reported. He argued Kyiv should be free to turn Starlink on Russian military targets, warning that China and other states will share comparable satellite technology with Moscow within months. [E12]
The desk's reading. There is a 68% probability that no named official source or named news outlet reports, by 16:00 UTC on 15 October 2026, that SpaceX has removed or disabled the in-motion speed restriction on military-grade Starlink terminals used by Ukrainian forces. The 68% is the no-named-report call. A path on which SpaceX quietly restores in-motion service and no named report arrives still settles yes; this paper is not separately pricing whether the cap physically remains. The start is the overnight restriction already in force, with no SpaceX duration published and no published reversal. UNN's cutoff while moving, and ordinary terminals still working, move the no-named-report call up: those facts describe a product speed gate on the military-grade service, not a network shutdown, and a product rule is less likely to draw a same-day restore notice than a glitch. Beskrestnov's no-warning missions, the 7th Rapid Reaction Corps confirmation, and his line that the action is not coincidental move it up, as an intentional setting is less likely to be walked back in a named notice before the deadline. The absence of a SpaceX statement moves it down: a company still debugging a misconfiguration can still post a restore. Sternenko's unverified Trump-administration request does not move the number. The competing reading is that overnight connectivity loss was a glitch or a short anti-abuse trip, and that SpaceX will post that military in-motion service is restored before the deadline. A SpaceX or Ukrainian official notice that the speed restriction is removed would move the call down. Silence by the deadline settles yes.
The next test. A named official source or named news outlet reports, by 16:00 UTC on 15 October 2026, that SpaceX has removed or disabled the in-motion speed restriction on military-grade Starlink terminals used by Ukrainian forces. That report overturns the reading. No such report by that deadline settles yes.