Ukraine says a 100 mph operating limit has returned across the Starshield satellite service its forces use to intercept Russian drones.
SpaceX says that account is false and insists there has been no change.
That leaves a serious dispute hanging over one of the most important communications systems on the battlefield: Ukraine says it can measure the restriction in failed missions, while the company behind the network says it did not alter the service.
President Volodymyr Zelenskyy laid out Ukraine’s case after briefings from his defense minister and military commander.
Received briefings from Minister of Defense of Ukraine Yevhenii Khmara and Commander-in-Chief of the Armed Forces of Ukraine Mykhailo Drapatyi. Unfortunately, our units have been recording significant disruptions to Starshield’s operations over the territory of Ukraine for…
— Volodymyr Zelenskyy / Володимир Зеленський (@ZelenskyyUa) November 12, 2026
Zelenskyy said units had seen problems for several days along the entire front line and in Russian-occupied areas. He described the problem as a systematic limit at 161 kilometers per hour, or 100 mph, rather than a random technical failure.
Ukraine’s specific concern is not ordinary browsing speed. A moving terminal that loses service above that threshold can leave a fast interceptor drone without the connection it needs to reach an incoming Russian weapon.
Axios reported that a Ukrainian official described the disruption growing over three days: limited failures on day one, a much wider effect on day two and mission failures across the board by day three. Ukraine’s charge d’affaires in Washington said the system was cutting out when drones exceeded 100 mph and that Kyiv still had no explanation from SpaceX or the Pentagon.
The same report carried SpaceX’s direct answer: the allegation was false and there had been no change. It also noted that the bipartisan Congressional Ukraine Caucus was demanding a full accounting from both the Trump administration and SpaceX.
Those positions cannot simply be blended into a neat middle ground. Either the operating conditions changed, the Ukrainian military is measuring another technical problem that looks like the earlier cap, or the parties are describing different layers of a system divided between commercial infrastructure and government control.
That last possibility matters because Starlink and Starshield are related, but they are not the same product.
Starlink is SpaceX’s commercial internet service. Starshield is built for government and military customers, and Ukraine receives access through a U.S. government arrangement.
That uncertainty triggered immediate bipartisan pressure in Congress.
On behalf of the 105 Members of the Bipartisan Congressional Ukraine Caucus, we are demanding a full accounting from the Trump Administration and SpaceX on how and why this occurred and immediate action to restore full access to Starshield. pic.twitter.com/t3iFOoJFJh
— Congressional Ukraine Caucus (@UkraineCaucus) November 12, 2026
The caucus speaks for 105 House members and directed its demand at both the administration and SpaceX. Its statement raises the pressure for records and an explanation, but it does not establish who changed the service or whether the disruption began somewhere else in the system.
MarketScreener carried the Reuters report that Zelenskyy said the disruption covered the full front line and occupied territory and was making it harder to intercept jet-powered Russian drones. His government said it was working with the American side to determine what happened.
The wire service also placed the claim against the October episode, when Ukrainian officials reported an almost identical speed threshold. That earlier restriction was later reported lifted, making the return of the same number difficult to dismiss as a vague complaint even though the cause remains unproven.
Open sources cannot independently verify that a particular Russian strike got through because of the reported cap. They can verify that Ukraine made a detailed, measurable claim, that the same threshold appeared before and that SpaceX issued a categorical denial.
Senator Michael Bennet’s office documented the unresolved control problem before this latest report. Bennet and other lawmakers asked who ordered the October restrictions, whether SpaceX or the Pentagon implemented them and what safeguards exist to prevent a communications cutoff from hitting Ukraine without warning.
The senators also pressed for a clean explanation of the Starlink-Starshield boundary. That is more than a branding question: it determines whether a private company, a military contract manager or the White House can change operating rules that affect live combat missions.
The newest claims arrived while U.S. envoys were meeting Russian President Vladimir Putin, which immediately raised political suspicions. Timing is not proof, however, and no public evidence yet establishes who imposed a renewed limit—or whether the failure originates somewhere else in the system.
What is clear is that Starshield has become infrastructure with battlefield consequences. A 100 mph cutoff is not a minor service complaint when the equipment is mounted on aircraft trying to stop incoming drones.
SpaceX’s denial now demands a technical answer, not another round of competing slogans. Ukraine has supplied a threshold, a timeline and an operational effect; the Pentagon and SpaceX should be able to say what the network logs show.
Until that happens, the most important fact is the contradiction itself: Ukraine says the limit is back, and SpaceX says nothing changed.
Join the conversation!
Please share your thoughts about this article below. We value your opinions, and would love to see you add to the discussion!