Starlink in Ukraine: a denial does not settle who is in charge
Donald Trump's statement on Starlink access in Ukraine rules out immediate responsibility. But it does not explain how control over private satellite services is distributed.
A denial answers only one question
Donald Trump has stated that neither he nor Elon Musk is responsible for the recent loss of Starlink access in Ukraine. The statement is politically relevant because it touches on the debate about a country at war depending on private satellite infrastructure. But it does not answer the central operational question: who decides, under which rules, when which services are available?
The terms themselves have to be kept apart. Starlink is SpaceX's commercial satellite network. Starshield denotes an offering geared to government and security-related applications. Public reports on restrictions, contracts and speed limits do not always refer to the same technical or contractual level. Anyone who conflates the two may draw premature conclusions about the availability of one from a statement about the other.
Private capacity, public consequences
Satellite communication in a war is not simply a consumer service. It can enable the exchange of situational information, the coordination of relief supplies and the connection of remote areas. Precisely because the infrastructure is privately operated, corporate decisions, government contracts, export controls and military requirements overlap. A political denial can rule out a direct instruction; it does not automatically explain technical safeguards, contract terms or decisions by authorities and companies.
This is not a marginal problem of Ukraine. The war shows in concentrated form how heavily critical digital infrastructure can depend today on a few private providers. With cloud services, submarine cables, satellites or platforms the question is similar: which services count as commercial, which as critical – and who bears responsibility when they are restricted?
Control operates on several levels
The availability of a satellite service can be limited on several levels: through hardware, coverage, technical configuration, terms of use or regulatory requirements. Security reasons come on top. A provider may, for instance, want to prevent a service from being used for certain military purposes; a state can impose conditions; a customer may have purchased only certain capacities. Without robust information about these levels, no clear responsibility can be derived from the observed disruption.
That is why it is journalistically cleaner to treat a denial as what it is: a statement about responsibility, not proof of a complete technical explanation. Ukraine and its partners have a legitimate interest in transparency about availability, deadlines and emergency channels. Providers, in turn, cannot disclose every security architecture publicly. The tension between these interests is real.
What Switzerland can learn from this
Switzerland is not a party to the war, but it depends on reliable communication networks, precise navigation and data links. In civil protection, in research and in the economy the importance of space-based services is growing. The public debate should therefore not revolve around individual billionaires alone. It should clarify which redundancies, procurement rules and responsibilities are needed when private infrastructure becomes part of resilience.
The same applies to international rule-making. Space infrastructure is cross-border, and so are its operators and customers. Clear contracts, oversight of critical services and open communication channels in crises are less spectacular than a political statement. But they are what decides reliability.
