Trump: Musk Restored Starshield; Kyiv: Speed Cap Still On
Donald Trump declared the problem solved. Kyiv, checking the front line on Friday morning, says it isn't.
A day after the US president told reporters that Elon Musk had restored Ukraine's Starshield access — "the bottom line, he put it back" — Ukrainian officials spent the morning documenting the opposite: connectivity still dropping at 161 kilometres per hour, no confirmation of any change, and interceptor drones still going dark at the worst possible moments. Someone, somewhere, is wrong about what happened between Thursday's announcement and Friday's battlefield. And the gap between those two stories is now wider than any speed limit SpaceX ever imposed.
Photo: A SpaceX Starlink user terminal (illustrative). Ukraine's military says speed restrictions on Starlink/Starshield connections remain in place as of Friday morning. Credit: Steve Jurvetson / Wikimedia Commons, CC BY 2.0.
Update, Oct. 23 (evening): the 200 km/h false dawn — and Trump's Friday denial
Friday-evening reporting hardened the "not restored" side. The Wall Street Journal reported that some Ukrainian units briefly flew drones at 200 km/h on Thursday — a false dawn: by late Thursday and overnight, most of the military was again losing connections above 161 km/h, and Zelensky's spokesman Dmytro Lytvyn wrote on X late Thursday: "We see the same limit... nothing has changed." Beskrestnov's Friday Telegram assessment (quoted in our FAQ below) attributes the isolated faster cases to the SpaceX algorithm rather than any lifting. Trump, speaking Friday, denied ordering the restrictions — "It wasn't me and I don't think it was Elon" (single-source report via Nigeria Magazine; hedged as such). And Zelensky, in Friday-afternoon remarks carried by CNN, confirmed the speed limits "are still there" — while warning that already-agreed US Patriot interceptors "are still not coming," a shortage that makes the drone-interception problem worse.
Thursday's victory lap, Friday's flat denial
Rewind twenty-four hours. The Wall Street Journal had reported that Trump personally called Musk to ask him to lift restrictions on Starshield — the military-grade version of Starlink that carries Ukraine's battlefield communications. Asked about the call at the White House on Thursday, Trump did that thing he does: neither confirmed nor denied it, waved the question away, and landed a punchy bottom line instead.
"Whether I called or whether somebody else called, doesn't make any difference, I guess," he told reporters. "The bottom line – he put it back."
He added, for good measure: "I don't want to comment one way or the other, but my relationship with Elon is a very good one."
It was the classic Trump tech-remedy formula: name the billionaire, claim the fix, move on. The trouble is that the people on the receiving end of the service check the receipts. By Friday morning in Kyiv, they were checking — and the receipts said otherwise.
A source in Ukraine's Defence Ministry told CNN there was "currently no confirmation that the restrictions have been lifted" and that "instances of signal loss are still being observed" for any military equipment travelling above 100 miles per hour (161 kph). A separate MoD source told the Kyiv Post, in almost identical language: "As of this morning, cases of connectivity loss at speeds of 161 kph are still being observed."
Then came the sharpest rebuttal, from a man whose job is to monitor exactly this. Serhiy "Flash" Beskrestnov, an adviser to President Volodymyr Zelensky on defence technologies, wrote on Facebook on Friday morning: "At this time, we are not observing any lifting of restrictions on Starlink. There are isolated cases where Starlink may operate slightly faster than the restrictions allow, but this is likely due to the SpaceX algorithm or specific usage conditions, rather than a lifting of the restrictions."
We read the Friday-morning dispatches from CNN, the Kyiv Post and Interfax-Ukraine back to back this afternoon, and all three land on the identical line: no confirmation, still dropping at 161 kph.
161 kph: the number that grounds Ukraine's drone fleet
To understand why a single number matters so much, picture the kill chain it breaks. The restrictions — which, according to Interfax-Ukraine's Defence Ministry sources, hit without warning on the night of October 14 — cut the link whenever a terminal moves faster than an equipment-dependent threshold, somewhere between 72 and 161 kph. That doesn't sound crippling until you remember what Ukraine's Starlink-equipped hardware actually does at speed.
Ukraine's interceptor drones, the ones sent up to knock down Russian jet-powered Shahed attack drones, fly fast because their targets fly fast — above 400 kph. Zelensky spelled out the arithmetic to CNN's Christiane Amanpour in an interview published Thursday: "When an Iranian drone goes with a speed of 450 or 500 kph [280 to 311 mph], and you limit [the speed] one night to 70 or even 100, you cannot intercept anything. And this is terrible."
One Ukrainian Armed Forces officer put it more bluntly to CNN: "There are definitely speed limits; nothing has changed yet, at least from what I can see here. It makes coordination difficult; sometimes there are interruptions. The connection drops out for 10 to 15 seconds." Ten to fifteen seconds is an eternity when the thing you're steering is chasing a jet drone. "We lost a lot of assets, much more than usual," the officer added, saying the restrictions had hit reconnaissance drones and Starlink-equipped systems too.
It is worth stating what is verified and what is analysis. Verified: the caps began the night of October 14; the thresholds ran 72–161 kph depending on equipment; interceptor drones, strike UAVs, logistics, reconnaissance and communications retransmission were all complicated; the Defence Ministry held consultations with the United States, SpaceX and NATO partners, and says it has verified backup communication channels. Analysis: whatever caused the restrictions, their battlefield cost is measured in drones Ukraine can no longer steer and strikes it can no longer stop.
Thursday night was grim evidence of the stakes. Russia launched 176 attack drones overnight, according to the Ukrainian Air Force. At least nine civilians were killed and 76 injured across the country, per CNN's tally of local officials' reports. Russia's deputy energy minister said strikes on energy infrastructure in six regions left more than 500,000 people without power on Friday. Against that backdrop, Kyiv Post reported that a third source told CNN the available speeds were "clearly not enough to intercept jet-powered drones" — as of Thursday afternoon, the very day Trump declared the service restored.
The hot-potato chain of blame
Here is where this story stops being a technical glitch and becomes a political farce. Nobody — not the White House, not the Pentagon, not SpaceX — will say who actually ordered the restrictions. They will, however, happily point at each other.
Start with Musk. When the speed caps became public, the SpaceX chief posted that "any limits on speed or usage" of Starshield "are decided by the US military and ultimately POTUS." Neat. Clean. Somebody else's problem — specifically, the president's.
But Defence Secretary Pete Hegseth said on October 20 that the Pentagon had not directed any changes to Starshield. And Trump himself said last week that he had not either. So the military says it didn't do it, the president says he didn't do it, and Musk says only the military and the president could have done it. Somewhere in that triangle, nine days of restrictions materialised out of thin air.
Photo: US President Donald Trump told reporters on Thursday that Elon Musk had restored Ukraine's Starshield access. Ukrainian officials say the restrictions remain. Official 2025 White House portrait, public domain.
Secretary of State Marco Rubio has added a third flavour of evasion, maintaining that Starlink is a commercial product whose operating decisions are made by SpaceX — while conceding that Ukraine's request for broader Starshield access remains under discussion. Meanwhile Zelensky, asked point-blank who ordered the restrictions, told reporters he genuinely doesn't know whether the decision came from SpaceX or from US government institutions. "Technically, I think SpaceX can do it," he said. "But whether the decision comes from them or from some institutions, I don't know."
A senior European official, speaking to the Associated Press on condition of anonymity, confirmed Thursday that the cap was still set at about 100 mph (160 kph) — and that Ukraine has received no clear official explanation of who ordered the restrictions or why. Nine days in, with interceptor missions being lost, Kyiv still doesn't have a name, a signature, or a reason. That is not a communications mix-up. That is an accountability vacuum, and it is colossally irresponsible for a system this critical to a war.
Our earlier reporting traced the arc of this saga as it unfolded — including the Wall Street Journal's account of Trump's call to Musk and the history of the speed caps in our report on Trump's intervention, and the longer-running question of whether Europe can ever free Ukraine from its dependence on Musk's constellation. This latest episode answers part of that question: dependence is not just a technical problem; it is a governance problem, and nobody is governing.
Congress enters the picture
The vacuum has not gone unnoticed on Capitol Hill. Democratic Senator Richard Blumenthal has announced a new inquiry into how the technologies were slowed down for Ukraine's defence systems — the kind of move that converts a news cycle into a paper trail. Subpoenas, hearings and sworn testimony have a way of finding the name nobody will volunteer.
Blumenthal's announcement lands in a Washington already jittery about the episode. The restrictions surfaced shortly after Trump publicly criticised Ukraine and urged it to stop striking Russian oil refineries, and relations have frayed further since, with Trump calling for Zelensky to be replaced after the Ukrainian president criticised a US deal easing some sanctions to let more Russian diesel into global markets. None of that proves causation — we are not asserting a link the reporting doesn't establish — but it is the political weather in which a satellite system got throttled without explanation.
Ukraine's acting charge d'affaires in Washington, Denys Senik, has said Kyiv is still awaiting an official response from the Pentagon and SpaceX on the full restoration of Starshield services. Ukraine, in other words, is waiting for an answer from the US side, and there is no response yet — even as the US president tells reporters the matter is resolved.
Our read: announcements don't intercept Shaheds
Here is the reporter-position part, stated plainly. When the President of the United States announces that a military communications system has been restored, and the army actually using that system reports — the very next morning, with monitoring data — that nothing has changed, one of two things is true. Either Kyiv's Defence Ministry, its presidential adviser, a senior European official and multiple frontline officers are all independently wrong, or the announcement was premature at best and shoddy at worst.
Look at the asymmetry. Trump's evidence for the fix is a sentence at a press gaggle: "he put it back." Kyiv's evidence for the non-fix is a week of recorded connection losses at specific speeds, corroborated by named officials and an anonymous officer describing 10-to-15-second dropouts in real time. In journalism, you trust the people with the instruments, not the people with the podium.
There is also the partial-truth possibility worth taking seriously. Ukrainian volunteer Serhiy Sternenko reported on X on Friday that some Ukrainian units did see the service restored for flights above the previous limits — but, he stressed, "this applies by no means to all missions. Some of them were disrupted because in certain cases the restrictions remain in effect." That uneven picture matches Beskrestnov's note about occasional above-limit operation being an algorithm quirk rather than a lifted restriction. A fix that works for some units, some of the time, is not a fix — it is a coin flip with interceptor drones.
The botched part of this whole affair is not the technology. It is the governance: a system that can ground a country's air defence can be throttled by an unnamed hand, for unnamed reasons, and restored — or not — by a presidential one-liner. Blumenthal's inquiry is the first serious attempt to get a name on paper. Until that happens, "he put it back" is a claim, not a fact. And Kyiv will keep checking the front line, because Kyiv has no choice.
For context on how we got here, see also Poland's warning to Musk about playing politics with Starlink — an early sign that European capitals saw exactly this kind of leverage problem coming.
Frequently asked questions
What is Starshield, and how is it different from Starlink?
Starshield is SpaceX's military-grade version of its Starlink satellite internet service, operated under US government contracts. Ukraine uses it for battlefield communications, mid-range strikes on Russian-occupied territory and its interceptor-drone operations. It uses the parallel civilian Starlink system for non-military purposes. Both networks are reportedly affected by the speed restrictions.
What exactly is the speed restriction?
Terminals lose their satellite connection when moving above a speed threshold. According to Ukraine's Defence Ministry sources, the thresholds began on the night of October 14 and ranged from roughly 72 to 161 kph (about 45–100 mph) depending on the equipment. The 161 kph figure is the one Kyiv keeps recording losses at as of Friday morning.
Did Trump actually call Elon Musk about this?
The Wall Street Journal reported he did, and a person familiar with the matter separately confirmed to CNN that Trump asked Musk in a phone call "in recent days" to restore full access. Trump himself has declined to confirm or deny the call, telling reporters: "Whether I called or whether somebody else called, doesn't make any difference, I guess."
Has the restriction been lifted or not?
According to every Ukrainian and European source that has checked this week — no, or at best partially and unevenly. Trump's claim that Musk restored the service on October 22 is contradicted by Ukraine's Defence Ministry (no confirmation, losses still observed at 161 kph Friday morning), presidential adviser Serhiy Beskrestnov (no lifting recorded), a senior European official (cap still ~160 kph Thursday), and frontline officers (dropouts of 10–15 seconds ongoing). Some units reported improvements, but not all.
What happens next?
Three tracks: Zelensky said Secretary of State Marco Rubio promised to return with information within "48 plus hours"; Senator Blumenthal has launched a congressional inquiry into how the slowdown happened; and Ukraine's Defence Ministry continues monitoring the networks while relying on verified backup communication channels. The name of whoever ordered the restrictions remains unknown.
Sources
Reporting for this article drew on CNN's Friday-morning coverage from Kyiv and Washington, the Kyiv Post's Defence Ministry sourcing, Interfax-Ukraine's ministry reporting, Ukrainska Pravda, the Associated Press (via DT Next), LIGA.net, Euromaidan Press and Mezha, alongside the Wall Street Journal's original reporting on Trump's call to Musk. Quotes are attributed to the outlets that first published them.
By Daniel Rao
Daniel Rao covers US tech and AI policy for TechPulse USA, with a focus on the collision between Silicon Valley and Washington — and what it means for the rest of the world.
Comments
Post a Comment