Trump Called Musk, Got Ukraine's Starshield Uncapped

For ten days, nobody would admit who throttled the internet connection Ukraine's drones fly on. Elon Musk said the military and the president decide. The president said he didn't know. The Pentagon said it changed nothing. Then, on Wednesday, Donald Trump picked up the phone, called Musk — and, mostly, it came back.

That's the short version of the strangest episode of the war's tech war. The longer version involves a speed limit lower than a camper van on a Texas highway, a feud over Russian diesel, and a week of denials so botched that nine United States senators are now demanding the Pentagon's watchdog name the person who ordered it.

Photo: a stack of 60 Starlink satellites atop a Falcon 9 before entering orbit. Starshield, the military-grade network built on Starlink technology, is what Ukraine's forces lost reliable access to this month. Photo: Official SpaceX Photos, via Wikimedia Commons (CC0).

Update, Oct. 23: Trump says it's "back" — Zelensky says it isn't

The story moved again on Thursday. Trump, asked outside the White House whether he had personally called Musk, declined to confirm the call — "I don't want to comment on it, you know, whether I called or whether somebody else called — doesn't make any difference," he said — then landed the claim that matters: "I guess the bottom line, he put it back." Zelensky, at his own press conference the same day, contradicted him: the speed "has not been restored to 400 [km/h; 250mph] yet," though "we are working on it." (Both remarks via the Hindustan Times' Oct. 23 Reuters-based report.) The finger-pointing meanwhile went three-way: one Ukrainian official told Axios that "SpaceX as a company tells us it is a technical problem. But our contacts in the company say it is coming from the White House. When we ask the White House, they say it is Elon." And the Washington–Kyiv relationship kept fraying at the edges — AFP reports Trump has been calling for Zelensky's replacement after the Ukrainian leader criticised the US deal allowing more Russian diesel onto global markets. The cap may be lifting; the political fight underneath it is not.

The Trump-Musk call that lifted Ukraine's Starshield cap

The Wall Street Journal reported on Thursday that Trump personally called Musk on Wednesday and asked him to lift the speed restrictions on Starshield, the military-grade satellite network Ukrainian forces use for frontline communications and drone operations. Trump had told aides and allies repeatedly this week that he wanted the restrictions reversed, and on the call he vented his frustration that speeds were still capped at around 100 miles per hour.

The outreach was first reported by the Journal, citing US officials, and confirmed to the New York Post by a White House official. What happened next is not in dispute: by Thursday, US and Ukrainian officials said the system was operating more normally than before, at higher speeds than under the cap. Some Ukrainian officials, however, said full functionality had not been restored.

Trump, asked about the call on Thursday afternoon at the White House, did the political two-step — he declined to confirm the conversation had even happened, then summed up the outcome in six words. "The bottom line: he put it back," he told reporters.

Volodymyr Zelensky, speaking at a press conference on the same day, sounded like a man negotiating with his own country's lifeline. The speed of the military's satellite connection, he said, "has not been restored to 400 [km/h; 250mph] yet." Then the part that matters: "We are working on it. I am waiting to hear from US Secretary of State [Marco] Rubio. He promised to get back to me with information within 48 hours or so."

Three days earlier, Trump had told reporters he didn't know who was responsible for the slowdown — "but I would like to find out." He apparently found out the number to dial.

What the Cap Actually Did to Ukraine's Drones

The mechanics of the restriction were cruelly simple. Starting on October 14, without warning, Starshield terminals began losing their connection whenever they moved faster than about 160 kilometres per hour — 100 mph, the speed limit on a motorway. In practice, Ukrainian units found the links held only below about 130 km/h, roughly 81 mph. Drones that routinely fly faster than that simply went dark.

That list is most of Ukraine's drone fleet: offensive drones used for strikes on Russian logistics and command posts, mid-range attack drones, and the interceptor drones Kyiv is racing to scale up against Russia's own jet-powered attack drones. The Associated Press reported on October 16 that Ukrainian defence-technology adviser Serhii Beskrestnov said Starshield terminals could lose connectivity above 160 kph, and that Ukraine was in what he called active negotiations with the Pentagon, SpaceX and the US government to get the limit lifted. His own words were sharper than the technicalities: "this is not only a technical issue and not only a business issue, but also a political one."

The military significance is why the cap was more than a contract dispute. Michael Kofman, a military analyst at the Carnegie Endowment for International Peace, told the Wall Street Journal that "removal of the throttle limit will do much to enable Ukraine's strike capabilities at operational depths and its current effort to scale up deployment of jet-powered interceptors." Kofman added that he had heard from Ukrainian military units that early tests suggested the system was now working more regularly — early, careful, but real.

It's worth remembering how deep this dependency runs. As we wrote when Europe admitted it can't free Ukraine from Musk's Starlink, there is no replacement network ready. Starshield handles battlefield communications and the targeting chain; the civilian Starlink network runs everything else. When one man controls both, a software setting becomes a weapon.

"It Wasn't Me": A Week of Shoddy Denials

The paper trail of who did it reads like a group project where everyone deleted the shared folder. On October 14, hours after the slowdown became public, Musk posted on X that "Starshield systems are owned and controlled by the US government" and that "any limits on speed or usage are decided by the US military and ultimately POTUS" — pointing the finger squarely at the White House.

Trump, for his part, had denied requesting any curbs the previous Friday, adding: "It wasn't me. And I don't think it was Elon." Defence Secretary Pete Hegseth said on Tuesday that the Pentagon had issued no instructions: "We haven't pulled anything back," adding that "Starlink has the option to make decisions concerning its terms of service" and that "we haven't made any directives or anything like that." Secretary of State Marco Rubio, speaking on Wednesday during his trip to India, went further: "The president has nothing to do with the decisions that are made by Starlink and Starshield and by Mr. Musk. That's a private company; the president doesn't run that company and can't direct that company to do anything... I'm telling you, there was no foreknowledge."

Then the Journal's reporting landed: it was Musk who ordered the cap, citing US officials and people familiar with the matter. Some of those officials told the paper Musk acted alone; one person said Musk spoke with Trump and other senior officials before imposing it. Reuters had earlier reported the order came from inside the White House. The Telegraph said Musk approached Trump with the idea. Three outlets, three chains of command, zero agreement.

Zelensky, meanwhile, stopped being diplomatic. On NBC's Meet the Press on Sunday, he said: "It was blocked for some period of time. And then it was deblocked by the American side. We are very thankful for this... It was a message from the American government to limit the speed. And technically, SpaceX did it." Administration sources have floated — with no evidence provided — a theory that Ukraine's problems came from using consumer Starlink terminals for some applications instead of Starshield. Nobody has produced a shred of proof for that, and Kyiv isn't buying it.

Refineries, Diesel and the Midterms: The Motive

None of this happened in a vacuum. Both Musk and Trump were furious at Ukraine for striking Russian diesel refineries — and the timing was not subtle. Trump blames those strikes for high fuel prices ahead of the November 3 midterm elections. On October 10, he told Zelensky he should "better damn well stop" hitting refineries; Musk replied on X that "Zelensky has gone too far," according to reporting of the exchange. Four days later, Ukrainian drone operators began losing full access to Starshield.

The pressure campaign went further than rhetoric. The administration struck a deal with Moscow to allow Russian diesel onto global markets and waived some sanctions on Russia — moves Ukraine and its European allies condemned. One US official told Axios that Zelensky "is misreading the room. By continuing to hit refineries, he is eroding the goodwill that he has built with Trump over the last six months." Most energy analysts, it should be said, argue the Iran conflict has done far more to drive fuel prices than any refinery fire in Russia — but midterms don't wait for analysts.

None of that proves a quid pro quo, and it would be shoddy journalism to assert one without evidence. But the sequence — fury over refineries, then the cap; a phone call from Trump, then the uncapping — is the kind of coincidence that makes senators reach for subpoena-shaped stationery. Poland already warned Musk to stop playing politics with Starlink; this month showed exactly what that warning was about.

Photo: Elon Musk at the Pentagon in March 2025. The Pentagon's Inspector General is now preparing a response to a bipartisan Senate demand to investigate whether the Defence Department or SpaceX ordered Ukraine's Starshield speed cap. Photo: U.S. Air Force Senior Airman Madelyn Keech, Department of Defence, via Wikimedia Commons (public domain).

Starshield cap: Congress wants the Pentagon watchdog to name names

We checked the paper trail ourselves — the bipartisan demand to the Pentagon's watchdog, the Democrats' separate records request to SpaceX, and the watchdog's promised reply all landed within days of the cap. This investigation isn't hypothetical; it's already moving.

Nine senators from both parties have written to the Defence Department's Inspector General, Platte Moring, demanding an investigation into whether the Pentagon or its contractors ordered, directed or knew in advance about the restrictions. The letter was led by Senator Jeanne Shaheen, the ranking Democrat on the Senate Foreign Relations Committee, and Republican Senator Thom Tillis, and signed by Dick Durbin, Susan Collins, Jack Reed, John Cornyn, Chris Coons, Lisa Murkowski and Richard Blumenthal. It asks what the senators most want answered: who decided, and whose contracts were broken.

The letter's most striking passage concerns American personnel. "We are particularly alarmed by incidents in which US diplomatic, military, and security personnel were unable to reach designated bunkers during Russian air raids," the lawmakers wrote, and asked the Inspector General to establish whether Pentagon or contractor decisions contributed to those circumstances.

Separately, on October 19, four Democratic senators — Blumenthal, Sheldon Whitehouse, Shaheen and Coons — sent their own records request to SpaceX's legal vice president, Christopher Cardaci. It demands a complete timeline of restrictions between October 10 and 15, the names of everyone who approved, implemented or had advance notice of them, all communications between SpaceX and federal officials, the contracts showing whether SpaceX or the US government controls access, and whether Germany — which funds some of Ukraine's Starlink access — was notified. They want answers by November 2. The Pentagon's Office of the Inspector General, for its part, said it is in the process of preparing a response.

The Switch Still Has One Owner

Here's the uncomfortable truth neither Musk nor Trump can post away: a private citizen switched a war's nervous system off and on in the same week. Europe noticed, and said so out loud. Commission spokesman Thomas Regnier called the reports "deeply concerning" at a Brussels briefing on Wednesday, urged SpaceX to restore full service urgently, and admitted the obvious: the war has shown how important space capabilities are to Europe's security, and Europe needs to build its own. Talks on Ukraine joining the EU's GOVSATCOM pool are underway; the IRIS² constellation won't be fully operational until 2029. That's a long time to wait for redundancy.

This is also not the first time. In 2022, Musk refused to extend Starlink coverage to Crimea ahead of a planned Ukrainian naval-drone attack, citing escalation fears, and briefly threatened to stop funding Starlink in Ukraine altogether before reversing. Each episode ends the same way: Musk exercises the power, everyone acts shocked, nothing structural changes. JD Vance has said he understands Musk's reluctance to intervene in the war — a remarkable sentence to sit with, given that reluctance now extends to flipping a switch mid-battle.

So here is the reporter's judgment, stated plainly: the question was never really who ordered the cap — the denials, the contradictions and the belated phone call all point to a system where nobody is clearly in charge, which is the whole problem. Whether Musk can keep being the switch — and whether Washington can keep pretending it's surprised every time he flips it — will decide not just Ukraine's war, but how the next decade of warfare gets fought.

As Europe's own admission made clear, there is no Plan B yet. Until there is, every phone call between a president and a billionaire is a national security event.

What is Starshield and how is it different from Starlink?

Starlink is SpaceX's commercial satellite internet network. Starshield is its military-grade sibling, built on the same satellite technology but designed for government and defence customers, with different service terms — including, until this month, no speed-based connection limits for Ukrainian forces. The Pentagon is a Starshield customer; Ukraine's frontline units are the end users.

What exactly was capped on Starshield in Ukraine?

Not data speed, but motion speed. Terminals lost their connection when moving faster than about 160 km/h (100 mph); in practice, links often held only below ~130 km/h. That threshold sits below the operating speed of most Ukrainian attack and interceptor drones, which is why the cap was so destructive.

Did Trump order the Starshield slowdown?

Unresolved. The Wall Street Journal reports Musk ordered it himself; Reuters reported the order came from inside the White House; The Telegraph said Musk brought Trump the idea. Trump, Hegseth and Rubio all deny any government directive. The one fact everyone agrees on: Trump called Musk on October 21 and asked for it reversed.

Is Ukraine's Starshield fully back to normal now?

Not quite. US and Ukrainian officials say it's operating more normally and at higher speeds than under the cap, but Zelensky says speeds have "not been restored to 400 [km/h] yet" — the pre-cap ceiling — and some Ukrainian officials say full functionality hasn't returned.

Who is investigating the Starshield slowdown?

A bipartisan group of nine senators has asked the Pentagon's Inspector General to investigate whether the Defence Department or its contractors ordered or knew about the restrictions. Four Democratic senators separately demanded SpaceX's internal records by November 2. The Inspector General's office says it's preparing a response.

Update, Oct. 24: Congress opened not one but four probes

The uncapping did not end the story — it moved it to Capitol Hill. On October 23, House Foreign Affairs Committee Democrats led by ranking member Gregory Meeks and Senator Peter Welch, with four bicameral colleagues, demanded a clear explanation from Elon Musk about why Starshield access was ‘suddenly shut off for Ukrainian forces’ (House Foreign Affairs Committee Democrats). Their letter quotes Musk's own assertion that limits are ‘decided by the U.S. military and ultimately POTUS’ — and sets it against public reporting that Musk personally brought the suggestion to slow Ukrainian communications to President Trump. The Wall Street Journal reported on October 22 that Trump called Musk to restore the system; the lawmakers note the restrictions remain in place anyway.

A second letter, led by California Democrats Sam Liccardo, Ro Khanna and Jimmy Panetta and first reported by CNBC, went further: it asks White House chief of staff Susie Wiles for an immediate, government-wide investigation into who ordered the restrictions, whether federal contracts were breached, and whether other Musk-affiliated federal agreements carry the same risk — with an initial briefing due within 14 days. Senator Richard Blumenthal separately opened his own inquiry on October 22, writing to Defense Secretary Pete Hegseth that the move ‘raises serious questions about who controls critical capabilities the U.S. government has spent billions of dollars to procure’ (Kyiv Independent). Meeks and Welch gave Musk until October 31 to answer. Senator Adam Schiff called for a full Senate investigation and Musk's testimony under oath; Senator Chris Coons said Musk should not be able to influence the war ‘with the push of a button’ — and Poland warned Musk about playing politics with Starlink weeks before Washington caught up.

Sources

The Wall Street Journal (original reporting on Musk's order and the Trump–Musk call, October 20 and 22, 2026); Reuters (White House account reporting); the Associated Press (October 16 reporting on Serhii Beskrestnov and Ukrainian testing); Agence France-Presse (wire coverage of the Journal's reporting); the New York Post (White House confirmation of the call and Trump's Thursday remarks); NBC News, Meet the Press (Zelensky interview, October 18); Axios (US official on the refinery dispute); European Commission midday briefing, Brussels (Thomas Regnier, October 21); Carnegie Endowment for International Peace (Michael Kofman's assessment).

Published October 23, 2026 · By Daniel Rao

Daniel Rao covers AI, defence tech and frontier science for TechPulse USA. He has spent the last year chronicling the collision between autonomous software and the institutions it keeps surprising.