Trump denies cutting Ukraine’s Starlink access as Zelensky details the food, water and drone failures it caused

Full analysis

What happened Why it matters How each country tells it Where accounts conflict Room for disagreement Our assessment Sources and evidence

What happened

On the morning of October 14, the Ukrainian Armed Forces command reported that drones fitted with Starshield terminals—the military version of SpaceX’s Starlink—began losing their satellite link whenever speed passed 160 kilometers per hour, wrecking several operations. Onet Wiadomości, which gives the most granular account, reports that the following day the threshold at which signal dropped fell to 60–80 km/h, causing what it calls an even more serious problem for Ukrainian forces. After about a day the permitted speed rose again, though President Zelensky said Friday that it had not returned to previous levels.

At the EU summit in Brussels, Zelensky gave the failure a human cost. Glavcom reports that he said the restrictions “disconnected logistics and disconnected civilian protection,” calling the episode “very unpleasant.” Soldiers on the front can stay in position for weeks or months under constant Russian drone observation, he told reporters, and Starlink-equipped drones must fly fast to deliver food and drinking water; when the link drops at speed, the supplies do not arrive. The Belarusian state channel ONT, relaying BelTA’s report of The Guardian, records him saying the limits “have not been lifted fully,” that speeds are recovering gradually but have not reached previous levels, and that he called the episode “a very dangerous and unpleasant surprise.” Onet notes that former defense minister Mykhailo Fedorov wrote on X on October 15 that the connection worked stably at 160 km/h and thanked SpaceX owner Elon Musk. Musk immediately refused credit: “any limits on speed or usage are decided by the US military and ultimately POTUS.”

Washington’s version sits beside that. President Trump told reporters Friday that “I didn’t do that. No, we didn’t do that at all… I don’t even think it was slowed down,” and “I heard about it from the news, the media.” The New York Post reports that Reuters said Thursday the White House ordered the slowdown, citing two US officials and a Western official, and a congressional source confirmed that account to the Post. The Telegraph, carried by The New Republic and the Post, reported that Musk pitched the slowdown and Trump approved; an unnamed source told The Telegraph, as relayed by The New Republic, that after a “night of carnage” in Kyiv Musk feared European consumer backlash and “tweeted out that he was innocent,” but “the reality is that they were both in it.” Against this, an unnamed administration official told the Post that the White House gave no such instruction and called it “Pentagon freelancing.” The Pentagon has not commented.

Why it matters

The event compresses the war’s dependence into a single dial. Onet’s technical account describes Starlink terminals on infantry, headquarters, relay drones, ground logistics platforms and interceptor drones. A cap at 160 km/h sharply hampers attacks on moving targets; at 60–80 km/h “the whole system of drone control at the front suffers.” Because command and communication are “directly dependent” on satellite links, Onet concludes Ukraine has no replacement outside Washington’s control: OneWeb is bankrupt, IRIS² is unfinished, and Chinese constellations could reach Russia’s military before European equivalents reach Ukraine. Zelensky supplied the front-line measure—food and water not arriving under Russian observation.

The outlets read the same facts through their own stakes. The New York Post presents a president denying any role while anonymous officials trade blame. The New Republic uses The Telegraph’s sources to call the denial false and treats Zelensky as Trump’s scapegoat before the midterms. Glavcom asks what the cutoff cost the front line. Onet treats it as a warning about a US-controlled switch on NATO’s eastern flank. ONT angles toward Zelensky’s dependency, carrying Musk’s argument that Starlink is a commercial service and should not serve offensive operations. What none disputes is that the switch exists and sits in Washington.

How each country tells it

• 🇺🇸
  New York Post · United States · original reporting

  Carries Trump’s flat denial at face value while relaying Reuters’ account that the White House ordered the slowdown and The Telegraph’s report that Musk proposed it.
• 🇺🇸
  The New Republic · United States · opinion

  Asserts from The Telegraph’s four anonymous sources that both Musk and Trump were in on the shutoff, framing Trump’s denial as false and Zelensky as a scapegoat.
• 🇺🇦
  Glavcom · Ukraine · original reporting

  Reports Zelensky’s Brussels briefing on what the slowdown actually did on the ground: it cut logistics and civilian protection, with Starlink-equipped drones unable to deliver food and water to front-line units.
• 🇵🇱
  Onet Wiadomości · Poland · original reporting

  An analytical piece treating the episode as the Pentagon and Washington holding Ukraine’s warfighting future in their hands, with technical detail on how the speed limits degraded drone relays, interception and command.
• 🇧🇾
  ONT · Belarus · carries BelTA

  Relays Zelensky’s admission, via BelTA citing The Guardian, that the restrictions are not fully lifted, framing him as a dependent party and carrying Musk’s line that Starlink should not serve offensive operations.

Where accounts conflict

Two disputes cannot both be true. On the order itself: The Telegraph’s four anonymous sources, as relayed by The New Republic and the New York Post, say Musk proposed the slowdown and Trump approved it. The New York Post separately relays Reuters’ two US officials and a Western official saying the White House ordered it. But an unnamed administration official quoted by the Post denies any White House instruction, calling it “Pentagon freelancing,” and Trump says he “didn’t do that.” Musk’s statement that limits are decided by the military and ultimately POTUS is compatible with every version except the Pentagon-only one. The Pentagon has not spoken.

On the underlying fact: Trump told reporters he did not think the service was slowed down at all and that it was “probably functioning,” while the Ukrainian Armed Forces command, Zelensky, his adviser Beskrestnov and former minister Fedorov all describe a speed cut that interrupted operations and has not fully lifted. Those versions could only be reconciled if the Ukrainian accounts are wrong; none of them is sourced to Washington.

Room for disagreement

The strongest case that this was a one-off scare rather than sustained leverage comes from the detail in Onet itself: Washington “does not set itself the goal of immediately disorganizing the command of the Ukrainian Armed Forces.” Under that reading, the October 14–15 throttle was a warning shot or bureaucratic action, not a new standing policy. Trump’s denial and the unnamed official’s “Pentagon freelancing” explanation fit the partial restoration: Fedorov wrote on October 15 that the link was stable at 160 km/h, and Zelensky said restrictions were not fully lifted but speeds were recovering. Ukraine is also acting as a party that can adapt: Zelensky said at his Brussels press conference that Kyiv is working with France on additional communications capacity, and Onet notes the Russian army built mesh networks to replace its own lost Starlink access. If that adaptation succeeds, future throttles become slower headaches rather than events that cut food and water to the front.