Opinion | Starlink restrictions in Ukraine have exposed a problem Elon Musk and Donald Trump cannot solve by pointing somewhere else: somebody exercised power over battlefield communications, and the public deserves to know who authorized it. The explanations offered so far have left far too much room for everyone involved to dodge responsibility.

The Wall Street Journal reported Oct. 20 that Musk ordered restrictions on military-grade Starlink services used by Ukraine, citing U.S. officials and people familiar with the matter. The restrictions impaired offensive and interceptor drones. CBS News separately reported that Musk ordered restrictions after consulting administration officials; how the order was implemented remained unclear.

My view is that this creates a credibility problem for both men. Musk has every commercial reason to reassure customers that essential connectivity follows dependable rules. Trump has every political reason to insist his administration controls consequential national-security decisions.

Those interests become difficult to reconcile when the public is told that the government controls the military service, the administration distances itself from the restrictions, and reporting identifies Musk as the person who ordered them.

Ukraine should not have to absorb the consequences while Washington and SpaceX work out whose explanation is least embarrassing.

Starlink restrictions: Why Starshield matters

Musk’s public explanation, reproduced in an Oct. 19 Senate letter to SpaceX, placed authority over Starshield limits with the government: “Any limits on speed or usage are decided by the US military and ultimately POTUS.”

On Oct. 21, Secretary of State Marco Rubio described decisions about commercial Starlink as matters for Musk and SpaceX, while denying U.S. government involvement in the slowdown, Reuters reported.

Those statements concern related but distinct services. SpaceX describes Starshield as a secure network for government customers that uses Starlink technology to support national-security needs. Treating the two names as interchangeable obscures the very question that needs answering: Who controlled the particular capability that changed?

A statement about private ownership does not explain who exercised authority under a government arrangement. A statement about government control does not explain what SpaceX personnel actually did.

The public needs the decision record: the affected service, the applicable contract, the instruction, the person who issued it and the people who implemented it. Repeating the product names more emphatically will not supply those answers.

Ukrainians experienced the consequences

The word “slowdown” also risks making this sound smaller than it is. The Senate’s Oct. 19 letter describes reported restrictions affecting devices traveling faster than 100 mph. That concerns whether moving equipment can maintain a connection, with potentially serious consequences for drone operations.

As USA Herald previously reported on the Starlink restrictions, Ukrainian units described lost satellite connections, canceled missions and disruptions affecting drones used for both strikes and air defense.

According to the Ukrainian presidency’s account of an Oct. 19 meeting with U.S. lawmakers, President Volodymyr Zelenskyy said restrictions remained across parts of the front. He described effects on logistics, Ukrainian strikes and defenses against Russian attack drones, particularly faster, jet-powered Shaheds.

The next day, his office said he discussed restoring Starlink and Starshield capabilities during a call with Rubio. That conversation also covered ballistic-missile warnings and interceptors.

These are Ukrainian accounts of the operational effects, and they should be attributed accordingly. They nevertheless make the urgency unmistakable: the people using these systems were seeking answers while trying to defend their country.

A dispute over responsibility becomes obscene when the people with the power to explain themselves can wait, while the people facing incoming weapons cannot.

If Musk made the call, SpaceX has a trust problem

If the reporting is borne out, Musk will have to explain the authority under which he ordered the restrictions. Government customers should demand to know whether a capability they rely on can change at his personal discretion, what safeguards constrain that discretion and what notice they can expect.

That is where I see the danger to SpaceX’s wider business.

A government purchasing critical communications is buying more than bandwidth. It needs predictable access, enforceable obligations and a clear process for resolving disputes. It needs to know what happens when the supplier’s leadership disagrees with its military objectives.

The military-service controversy does not establish that every commercial Starlink customer faces the same restrictions. It does give other governments a concrete reason to scrutinize the company’s decision-making and the protections written into their own agreements.

The business damage need not appear as an immediate collapse in subscriptions. Customers can continue using a service while treating their dependence on it as a vulnerability they need to reduce.

That is an ugly position for a supplier selling reliability.

If Musk’s defense is that Washington ultimately controls the relevant capabilities, customers will want that relationship spelled out just as clearly. Which decisions belong to SpaceX and which belong to the U.S. government? What assurances survive a political disagreement?

Trust cannot rest on customers guessing correctly about who holds the authority.

Trump’s denial leaves an oversight problem

Trump also faces an uncomfortable question if he did not direct or approve the restrictions: How did a consequential change affecting Ukraine’s military capabilities occur, and what did his administration do when it learned about it?

A president does not personally approve every operational decision. But presidential distance from an individual instruction cannot substitute for an explanation of the government’s oversight.

If contractors can make decisions of this magnitude without adequate coordination, the administration needs to explain the safeguards that failed and if officials authorized the change, it needs to identify them and explain their reasoning. If the restrictions reflected existing contractual limits, it needs to show the relevant terms and explain their application.

The commander in chief cannot make being out of the loop sound like leadership.

Conversely, if evidence establishes that Trump approved restrictions to pressure Ukraine, he should have to defend that policy publicly. He should explain its objective, its expected military effects and the risks his administration was prepared to impose on Ukrainians.

A presidential order would not, by itself, establish the constitutional crime of treason. That requires a distinct legal showing. My political judgment is that deliberately weakening a partner’s defenses to force concessions would constitute a profound betrayal of the people relying on American support. Whether that was the purpose here remains a question for the evidence.

The refinery dispute makes motive a central question

The Journal also reported that Musk and Trump had expressed anger over Ukrainian attacks on Russian diesel refineries, which Trump blamed for high energy prices. That context makes the purpose of the restrictions especially important to establish.

Musk’s criticism was public before the reported disruption. On Oct. 10, he wrote, “Zelensky has gone too far”, in an X reply to @RapidResponse47 and @POTUS. The reply responded to a White House video of Trump criticizing Ukrainian attacks on Russian refineries.

Four days later, Ukrainian officials publicly reported new satellite restrictions that had disrupted drone missions. That chronology documents Musk’s public opposition to Zelenskyy’s conduct before the restrictions surfaced.

The sequence is relevant to the question of motive, particularly alongside the subsequent reporting that Musk ordered the restrictions. It does not, by itself, establish that he acted independently of Washington. Whether he acted alone, coordinated with administration officials or implemented an agreed decision requires the communications and decision records.

Were the restrictions connected to an effort to influence Ukraine’s military decisions? Were they an enforcement action under an existing agreement? Who considered their effect on defensive missions?

Those questions deserve documents and sworn answers.

There is a world of consequence between restricting a particular operation under clearly understood terms and imposing a change that also degrades defenses against incoming attacks. Officials and contractors should have to account for the actual scope, the anticipated effects and the warning given to the people affected.

Invoking peace or commercial policy cannot replace that accounting. Any justification has to confront what the decision did.

Congress already has a paper trail to pursue

The demand for scrutiny predates the latest reporting and crosses party lines.

In an Oct. 15 letter to the Defense Department’s inspector general, nine senators requested an investigation into satellite restrictions and separate reported disruptions involving intelligence and threat warnings. Republican Sens. Thom Tillis, Susan Collins, John Cornyn and Lisa Murkowski joined the request.

The senators asked whether government officials or contractors directed, approved or knew about the changes. They also sought scrutiny of reported risks to American personnel and asked that relevant communications and contractual records be preserved. The letter explicitly acknowledged uncertainty about the causes and possible connections between the disruptions.

The separate Oct. 19 demand from Sens. Jeanne Shaheen, Richard Blumenthal, Sheldon Whitehouse and Chris Coons seeks SpaceX’s records by Nov. 2. It asks who participated in restriction decisions, who had authority under the contracts and what communications passed between SpaceX and federal officials.

After the Journal’s report, Sen. Adam Schiff called for a Senate investigation and for Musk to testify before Congress under oath. These are demands for investigation and testimony, not completed findings. They identify the next step with admirable clarity.

Congress should obtain the records and require the responsible people to explain them. A hearing should establish who ordered what, when, under which authority and with what understanding of the consequences.

The public should be able to compare those answers with what Musk and administration officials have already said.

Neither man gets to disappear behind the other

Here is the trap I believe Musk and Trump have created for themselves: each explanation that distances one from responsibility raises questions for the other.

If Musk exercised independent control, SpaceX must explain how customers can rely on its commitments; if Washington directed the restrictions, the administration must explain its policy. If authority was divided, both must show how that arrangement operated and where accountability rests.

There may be facts still missing that materially change this account. Producing them is the responsibility of the people and institutions that possess them.

Until then, their competing explanations are a reason for more scrutiny.

Musk has a business reputation to protect, and Trump has a political reputation to protect. Neither interest should outrank a clear accounting of decisions affecting people in a war zone.

Put the decision-makers under oath. Produce the records. Explain who exercised this power and why Ukraine was left trying to understand the consequences while defending itself.