Elon Musk ordered Starlink speed cap for Ukraine military operations

On 20 October, a report by the Wall Street Journal, amplified by Gizmodo, claimed that Elon Musk had instructed SpaceX to throttle the speed of the military‑grade version of its satellite network that Ukrainian forces use to coordinate drones and battlefield communications. The slowdown, which began on 14 October, reduced bandwidth for Ukrainian hardware, rendering some drones ineffective and sparking a backlash in Kyiv and confusion in Washington.

Starlink, the commercial satellite‑internet service run by SpaceX, expanded into a military‑grade product called Starshield. The latter is controlled by the U.S. Government and is intended for U.S. Forces, but Ukraine had been using Starlink for battlefield communications and drone operations since the onset of the Russian invasion.

Media additions

WSJ Claims Elon Musk Ordered the Throttling of Starlink Tech for Ukraine

According to the Wall Street Journal, cited by Yahoo News Singapore and NewsCord, Musk had “capped the speeds at which Ukrainian hardware could stay connected to the satellite‑based network.” He later posted on X that “any limits on speed or usage are decided by the U.S. Military and ultimately POTUS,” a statement echoed in a separate Straits Times article.

In the days that followed, Ukrainian President Volodymyr Zelenskyy publicly complained that the slowdown “we were unable to intercept a certain number of jet‑powered ‘shaheds’” and that the service “was very painful and frustrating.” He expressed that Ukrainian forces could “die if the unrestrictive service wasn’t restored.” These remarks were reported by The Tribune and echoed in a statement from former Ukrainian Defence Minister Mykhailo Fedorov, who thanked Musk for “restoring Starlink connectivity at speeds of up to 160 km/h.”

U.S. Officials, however, have consistently denied any order from Washington to throttle the service. Defence Secretary Pete Hegseth said the U.S. Military had not instructed SpaceX to make changes, adding that “any operational changes or adjustments… would fall within the satellite provider’s contractual terms.” The same denial was echoed by Secretary of State Marco Rubio, who noted that Starshield is a defense product “not available to Ukraine” and that the reported slowdown involved the commercial Starlink service, not the military‑grade system. These statements were captured by ABP Live and CNBC.

While the U.S. Denied responsibility, the Wall Street Journal report indicated that Musk had discussed the decision with multiple senior administration officials, including President Donald Trump, before imposing the speed cap. Trump, who had recently criticized Ukraine for attacking Russian diesel refineries, denied knowledge of the slowdown, saying he did not know who ordered it. He added that he would like to find out. These remarks were reported by Yahoo News Singapore and CNBC.

The controversy has sparked speculation about the extent of control the U.S. Government has over commercial satellite services used in wartime. Some analysts, such as Defence reporter Tyler Rogoway, have expressed reservations about the Wall Street Journal’s account, noting that SpaceX’s terms of service would seemingly prevent unilateral throttling. Rogoway’s concerns were highlighted in a Gizmodo piece.

Below is a concise timeline of the key events surrounding the slowdown:

• 14 Oct – Starlink speed cap imposed on Ukrainian hardware.
• 15 Oct – Reuters reports that the order came from the White House; Ukrainian forces experience reduced drone performance.
• 16 Oct – President Zelenskyy tweets about the loss of drone interception capability.
• 18 Oct – Musk posts on X that speed limits are decided by the U.S. Military and President.
• 20 Oct – Wall Street Journal publishes the full report; U.S. Officials publicly deny any directive.
• 21 Oct – The Tribune reports on the incident and notes ongoing restoration of speeds.

As Ukraine continues to rely on satellite connectivity to coordinate defence operations against Russian forces, the incident underscores the delicate balance between commercial technology providers and national security interests.