Starshield Restrictions Disrupt Ukrainian Drone Operations, Spark Diplomatic Row
Ukrainian military operations faced significant disruption after sudden speed restrictions were imposed on **SpaceX's Starshield** satellite service. The move severely impacted drone missions along the front lines, leading to urgent talks with **SpaceX** and a public blame game between **Elon Musk**, Ukrainian officials, and the U.S. government.
# Starshield Speed Limits Cripple Ukrainian Drone Capabilities
**Starshield**, the military-grade variant of **SpaceX's Starlink** internet service, has been a critical lifeline for Ukrainian forces, providing on-the-move connectivity for vehicles and drones. However, unannounced restrictions on Tuesday disrupted this vital service, forcing the cancellation of combat missions and complicating essential drone operations, logistics, and reconnaissance.
"Starshield connectivity while in motion has now been restored and remains operational," a Ukrainian Defense Ministry source confirmed on Thursday, speaking anonymously. This restoration followed a period where terminals struggled to maintain connections at higher speeds, with some reports indicating issues at speeds as low as 110-120 kilometers per hour.
While connectivity has reportedly improved at speeds up to 160 km/h, the formal speed limit remains in place. The underlying cause of these restrictions is still unclear, prompting ongoing discussions between Ukrainian officials, **SpaceX**, and its partners.
## Musk Points to Washington, D.C.
**Elon Musk**, CEO of **SpaceX**, responded to former Ukrainian Defense Minister **Mykhailo Fedorov's** call to lift the speed limits entirely. Musk stated on **X** (formerly Twitter) 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."
Musk differentiated **Starshield** from the commercial **Starlink** service, emphasizing that the latter is intended for civilian or defensive purposes, not offensive military operations. These comments appeared to shift responsibility for the restrictions towards Washington. However, officials in President **Donald Trump's** administration have reportedly denied involvement, stating the U.S. government does not control **SpaceX** and did not order the restrictions. Washington has indicated plans to contact the company to ascertain the cause of the disruptions.
## Battlefield Consequences: Drone Missions Disrupted
The immediate impact of these restrictions was felt directly on the battlefield. Ukraine's **7th Air Assault Corps** reported communication problems in the Huliaipole sector, particularly affecting drones reliant on satellite connectivity for navigation and control.
Drones experienced connection losses lasting 10 to 20 seconds, even at speeds below the formal threshold. While drones continued to fly, these interruptions made them harder to control and increased their vulnerability to Russian attacks by forcing them to slow down. Medium-range strike drones, which require high speeds during takeoff, were particularly affected, with some missions being canceled due to unstable communications.
**Serhii Beskrestnov**, a Ukrainian military technology expert and presidential adviser, warned that the restrictions also threatened Ukraine's ability to intercept Russian drones, specifically high-speed, jet-powered **Shahed** drones. He stated, "Our defense forces received no advance warning of the restriction, which caused several missions to fail. Clearly, this move cannot be a coincidence and is linked to the current political situation."
## Zelensky Blames Trump Amid Worsening Relations
The **Starlink** disruption comes amidst deteriorating relations between Kyiv and Washington. In an interview with **Piers Morgan**, Ukrainian President **Volodymyr Zelensky** expressed feeling personally betrayed by **Trump** over the restrictions, accusing Washington of abandoning a crucial partner. Zelensky alleged that both **SpaceX** and the United States were responsible, claiming the disruption would cost Ukrainian lives.
"I am sure they knew what they did, absolutely," Zelensky stated, predicting further casualties. Meanwhile, the **Kremlin** stated it had no official information regarding the restrictions, with spokesperson **Dmitry Peskov** reiterating Moscow's preference for such technologies not to be used for military purposes.
## Starlink's Critical Role and Past Tensions
**Starlink** has been instrumental in Ukraine's military communications since Russia's full-scale invasion in 2022, when **Musk** activated the service following an appeal from **Fedorov**. **SpaceX** provided thousands of terminals, helping Ukraine restore communications damaged by Russian attacks.
However, **Musk's** relationship with Kyiv has been complex. He has previously voiced concerns about the costs of providing the service and the risks of its use in offensive military operations, even suggesting "itβs time for Zelensky to go" in a separate statement. Despite this, in March 2025, **Musk** pledged never to disconnect Ukraine from **Starlink**, acknowledging the military's dependence on the technology.
Earlier this year, **SpaceX** also took steps to prevent unauthorized Russian use of **Starlink** after Ukrainian officials reported that Russian forces were installing terminals on attack drones. Ukraine also introduced a verification system allowing only registered **Starlink** devices to operate in Ukrainian-controlled territory.
## Suspected Sabotage of Starlink Infrastructure in Europe
The latest restrictions coincide with suspected sabotage incidents targeting **Starlink**-related infrastructure supporting Ukraine in Europe. In September, a fire damaged electrical equipment at a **Starlink** ground station in Poland, with authorities investigating possible sabotage linked to Russian intelligence services.
More recently, two masked men deliberately set fire to 11 of 17 **Starlink** antennas at a facility near Sofia, Bulgaria. These antennas were reportedly used by Ukraine and other customers. While there is no publicly confirmed evidence linking these two incidents or establishing Russian involvement in the Bulgarian attack, the timing adds another layer of concern to the ongoing challenges surrounding **Starlink**'s deployment and security.