Reports through October 20, 2026, describe speed-based limits on satellite connectivity used by Ukrainian forces. The restrictions disrupted some drone operations, but public accounts do not establish a single, verified chain of responsibility—or confirm that the previous service settings were fully restored.
1
6
What the restrictions did
The first reported connection losses began overnight on October 13–14. Reports commonly put the limit at about 160 km/h (100 mph): terminals in motion reportedly lost connectivity above that speed. Some accounts describe lower thresholds on certain equipment, so 160 km/h should be treated as a widely reported figure, not a confirmed cutoff for every terminal.
2
4
51
This was a speed-linked connection restriction, not simply a report of slower downloads. Ukrainian officials said the disruption affected military missions, and President Volodymyr Zelensky said the limits constrained drones used to intercept Russian attack drones and deliver supplies to frontline troops.
6
34
Starshield is not the same as commercial Starlink
Starlink is SpaceX’s commercial satellite-internet network. Starshield is the military-grade service associated with it; NPR describes it as a military version shared with Ukraine by the U.S. Defense Department.
18
The distinction matters because early coverage sometimes used “Starlink” as shorthand for the affected connectivity. But reporting also distinguished the military service from commercial Starlink. Secretary of State Marco Rubio said he understood commercial Starlink to be running again, while describing Ukraine as seeking Starshield access. That account does not, by itself, settle which service or terminals were affected in every reported incident.
10
47
Who ordered the limits? Reports conflict
The Wall Street Journal reported on October 20 that Elon Musk ordered and authorized the slowdown of a military-grade service used by Ukraine, citing U.S. officials and people familiar with the matter.
1 Reuters had earlier reported, citing two U.S. officials and a Western official briefed on the issue, that the instruction to slow Starshield came from inside the White House.
17 The Telegraph separately reported that Musk proposed slowing the service to President Donald Trump.
57
Those accounts do not amount to a publicly documented authorization chain. Trump denied that he ordered the restrictions, while Musk said Starshield is controlled by the U.S. government and that speed or usage limits are decided by the U.S. military and ultimately the president.
21
56 Rubio also denied that the White House ordered the slowdown.
39
The accounts may refer to different steps—proposing a change, authorizing it, communicating an order, or technically applying a restriction—but the available reporting does not resolve who was responsible for each step. Reuters and the Journal reported different accounts, and public statements from Trump, Musk, and Rubio did not settle the dispute.
1
17
21
39
56
Partial restoration did not settle the issue
Ukrainian and British officials reported at least partial restoration by October 15. But on October 17, Zelensky said restrictions remained and were still affecting military use.
2
6 On October 20, he appealed to Rubio for full access to Starlink and Starshield.
8 Reports of partial restoration, therefore, should not be read as confirmation that the previous operating limits were reinstated.
The episode also prompted calls for scrutiny. A bipartisan group of senators sought an investigation into why and how the satellite service was disrupted; senators also raised concerns about reported effects on intelligence-sharing and threat-warning capabilities.
19
20
The refinery dispute is context, not proof of cause
Reuters reported that the limits came amid pressure from Trump’s administration for Ukraine to stop attacks on Russian refineries. That timing is relevant to the political dispute, but it does not prove that the refinery issue caused the restrictions.
17
The reporting makes Ukraine’s reliance on SpaceX connectivity clear, while leaving important questions open: exactly which terminals faced which limits, who authorized the change, and whether the previous settings were restored. The safest conclusion is that a real, speed-dependent disruption was reported, its operational effects were serious enough to prompt official scrutiny, and responsibility remained contested as of October 20.
1
6
20