World / War — The Trump Musk Starlink Ukraine restrictions fight took a direct turn on Wednesday: President Donald Trump personally called Elon Musk and asked him to lift the limits on Ukraine's military-grade Starlink service, U.S. officials told the Wall Street Journal — and by Thursday the system was, in the words of officials on both sides, working more normally.

President Donald Trump called Elon Musk on Wednesday and asked him to lift restrictions on the military-grade version of Starlink that Ukraine's forces rely on, the Wall Street Journal reported on Thursday, citing U.S. officials — and Reuters confirmed the account the same day. The call is the first reported instance of the president personally intervening to reverse a slowdown that, for eight days, had capped the speed at which Ukrainian hardware could stay connected to SpaceX's satellite network at around 100 miles per hour (160 kph), a limit Ukrainian officials said left some of their offensive drones and air-defense interceptors powerless against Russian attacks.

Track it live: Ukraine war map — live conflict tracker

Elon Musk speaking at a Trump cabinet meeting — Trump Musk Starlink Ukraine restrictions
Elon Musk speaks during President Donald Trump's first cabinet meeting of his second term, in the Cabinet Room of the White House on February 26, 2025. On Wednesday, Trump called Musk directly and asked him to lift the Starlink restrictions on Ukraine, U.S. officials told the Wall Street Journal. Photo: The White House (Molly Riley) via Wikimedia Commons (public domain)

The clearest sign the call landed came from the battlefield side of the connection. The system was working more normally on Thursday, shortly after the Trump–Musk conversation, according to U.S. and Ukrainian officials cited by the Journal. Some Ukrainian officials were careful not to declare the episode over: the system had not been restored to full functionality, they said, but it was working at higher speeds than under the cap. That partial-restoration picture matters, because earlier on Thursday President Volodymyr Zelenskyy had said publicly that Starlink speed had not been restored for Ukraine at all, and that he hoped for talks with U.S. Secretary of State Marco Rubio in the coming days. Between Zelenskyy's statement and the Journal's reporting, in other words, sits a service in the middle of being switched back on — faster than the cap, not yet what it was, and verified so far by officials' descriptions rather than by any public statement from SpaceX itself.

What Trump asked for — and what he said frustrated him

Trump told Musk he was frustrated that the system's speeds remained capped at around 100 mph, officials told the Journal. Trump has also told aides and allies this week that he wanted to reverse the slowdown of Starlink, which Ukraine's forces use to defend themselves along the front line. The conversation followed the Journal's report earlier this week revealing that Musk himself had ordered the slowdown — reporting that landed in the middle of a public dispute about who was responsible. SpaceX and the White House have offered differing accounts of whether the world's richest man acted alone or at the administration's behest, and the White House referred the Journal, for this latest story, to Trump's recent denials that he had asked Musk to throttle Starlink's speeds or that he knew who issued the order. Trump told reporters on Monday that he did not know who was responsible for the slowdown, "but I would like to find out." The two men had also spoken about Ukraine and Starlink on the day the slowdown became public, the Journal previously reported.

What no party has done, as of Thursday, is comment on the record about the call itself. Musk, SpaceX and Ukraine's embassy in Washington did not immediately respond to the Journal's requests for comment. That silence leaves the shape of the reversal — a presidential request, made by phone, to a private company, about a battlefield system — resting on the accounts of unnamed U.S. officials, corroborated by the observable change Ukrainian officials described in the service itself.

Starlink satellites passing overhead at night — Trump Musk Starlink Ukraine restrictions
Starlink satellites pass overhead near Carson National Forest, New Mexico, photographed soon after launch. SpaceX's constellation of more than 11,000 low-Earth-orbit satellites carries Ukraine's battlefield communications and drone links. Photo: M. Lewinsky / NOIRLab via Wikimedia Commons (CC BY 4.0)

Eight days of throttle: how the crisis built

The slowdown began on October 14, when a speed limit appeared on the military-grade service — the Starshield tier built on Starlink's network, which adds encryption and, crucially, allows equipment to travel at far higher speeds than a commercial Starlink account. Ukraine's weapons are exactly the kind of equipment that needs that headroom: attack drones, interceptors and uncrewed boats that must move fast to intercept Russian drones, strike logistics and stall the invasion force. Kyiv said it received no warning. Serhii Beskrestnov, a senior adviser to Zelenskyy, said at the time that the action "cannot be a coincidence" and connected it to the political moment — a suspicion the White House has not addressed. Our earlier coverage traced the first days of the disruption and Kyiv's account of missions failing against the cap: SpaceX's Starlink speed limit and the drone missions it disrupted.

The administration's public line, in the days that followed, was that the whole matter sat outside its hands. Rubio said on Wednesday — the same day as the Trump–Musk call — that decisions regarding Ukraine's access to Starlink were up to its parent company SpaceX and its CEO Musk, not the White House. Days earlier, departing for a trip abroad, Rubio had said no one in the United States had ordered the slowdown, that it was not deliberate, and that his understanding was that the service had been restored — an assertion that drew criticism from lawmakers in both parties and that Zelenskyy kept contradicting in public. Defense Secretary Pete Hegseth likewise portrayed the cutoff as a commercial matter, pointing to terms of service that SpaceX had the option to enforce. Trump, for his part, denied ordering any restriction — the denial at the center of our report on the president's response — while other reporting, contested by the administration, described a White House role in the original limit: the sources-based account of the Starshield order. The Journal's Tuesday reporting then moved the attribution again, concluding that Musk ordered the slowdown and had discussed the decision with Trump — a sequence the White House's denials and SpaceX's silence have left formally unresolved.

The 100 mph problem, in one piece of arithmetic

The reason a speed cap on a satellite link can decide air battles is brutally simple, and a Senate Democratic aide laid it out during the congressional delegation's October 13–16 visit to Kyiv, which coincided with the slowdown: Russia is now fielding jet-powered versions of the Shahed attack drone that fly at 280 miles per hour (450 kph) or faster, and defending against them requires faster defensive drones. "It's a basic maths problem. If you have a 280-mph object coming towards you, you are not going to be able to counter it with something that goes 100 mph," the aide said, noting Kyiv lost a lot of air assets the first night of the slowdown. Michael Kofman, an expert on the war at the Carnegie Endowment for International Peace, made the same point from the other direction on Thursday: "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 suggest the system is now working more regularly — independent, expert confirmation that the post-call improvement Ukrainian officials described is visible at unit level, not just in statements.

Shahed 136 drone on display — the Russian attack drones Ukraine's interceptors must outrun
A Shahed 136 on display at an IRGC Aerospace Force exhibition in Kermanshah. Russia's jet-powered successors to this design fly at 280 mph or faster — the speed Ukraine's Starlink-linked interceptors were capped far below. Photo: via Wikimedia Commons (CC BY 4.0)

Why this matters

Start with what the call itself proves, whichever account of October 14 turns out to be true. For a week, the official position of the United States government was that a private company had made a private decision that Washington could not direct — Rubio said so explicitly, twice. Then the president picked up the phone, asked the company's owner to reverse it, and within roughly a day the service was measurably improving. That sequence does not prove the administration ordered the original slowdown; Trump's request is equally consistent with a president fixing a problem he says he did not create, in a week when the story was damaging him politically ahead of the midterm elections. But it does retire the claim that the White House was a bystander. A system this central to an ally's air defense now demonstrably moves when the president calls — which means its settings are, in practice, a matter of U.S. policy whether or not they are one in law.

That is the structural story underneath the week's drama, and it cuts in two directions at once. Ukraine's dependence on Starlink was always a known vulnerability: a constellation of more than 11,000 satellites, run by one company, owned by one man, carrying the communications and drone links of an army at war. The October episode showed the vulnerability is not hypothetical or technical — it is discretionary. A speed value in a terms-of-service table, changed without warning on October 14, degraded Ukraine's ability to intercept drones aimed at its cities; a phone call on October 22 began changing it back. Kyiv's supporters in Congress have already converted that lesson into an oversight question: bipartisan lawmakers, including Republican Senators Thom Tillis, Lisa Murkowski and John Cornyn alongside Democratic colleagues, have called on the Pentagon's Inspector General to investigate whether the Pentagon or its contractors had a role in the restrictions, and the IG's office has said it is preparing a response. The question those lawmakers are really asking — who can lawfully throttle a battlefield system the U.S. government helps procure, and with what notice — survives this week's reversal regardless of how the investigation answers it.

The politics run alongside. The slowdown arrived during a stretch in which Trump has eased economic pressure on Russia, criticized Zelenskyy, and pushed Kyiv toward negotiations — a pivot that has alarmed Ukraine and several European allies and drawn bipartisan pushback in Congress. Against that backdrop, Kyiv read October 14 as pressure, not accident; the administration read it as a commercial event it had nothing to do with. Trump's call to Musk can be read by the first camp as a quiet climbdown once the military cost became undeniable, and by the second as a president correcting a contractor's mistake the moment he confirmed it was real. Both readings agree on the fact that matters most to Ukraine: the pressure, if it was pressure, has been called off by the only person whose call the system's owner was certain to take.

What happens next

Four tests will show whether Wednesday's call closed the episode or merely paused it. First, full restoration: Zelenskyy said Thursday the speed had not been restored, and Ukrainian officials described a service improved but not whole. Whether the last increment returns — and whether Kyiv confirms it in the same public terms it used to complain — is the cleanest verification available, cleaner than any statement from Washington. Second, the promised Rubio channel: Zelenskyy said he hopes to speak with the secretary of state in the coming days, and what Rubio tells him about guarantees, notice periods and who decides will signal whether the administration intends to formalize any of this. Third, the Inspector General track: lawmakers have asked, the IG is preparing a response, and a real investigation would put the October 14 decision — Musk's, the White House's, or both — into a documentary record for the first time. Fourth, SpaceX itself: neither Musk nor his company has explained the slowdown, its purpose, or its reversal on the record. Until they do, the most consequential settings in Ukraine's air-defense network remain the ones nobody has publicly admitted to choosing.

There is a final, quieter measure. Ukraine told the world for eight days that the cap was costing it air assets against drones flying at 280 mph. The drones did not pause while Washington and SpaceX sorted out whose decision the cap had been. If the restoration now underway holds, the episode will be remembered as the week a phone call between a president and a billionaire functioned as an air-defense decision — and as the clearest demonstration yet that in this war, some of the most important switches are not in Kyiv, or even in the Pentagon, but in a private network's control room, one call away from the Oval Office.

Related coverage: SpaceX imposes Starlink speed limit in Ukraine, disrupting drone missions · Trump denies ordering the Starlink–Starshield limit · White House ordered Starshield limit, sources say

Sources: Reuters, The Wall Street Journal, Reuters via The Business Standard.