Restrictions expose Ukraine's Starlink dependency in Russia war

16th day of the tenth month

A nation fights for its life, and the lifeblood of its front runs through terminals owned by one man in another country. This is the story the throttling of Starlink has told, whether anyone wished it told or not. Ukraine’s drones find their targets, its gunners their coordinates, its commanders their voices - all upon a network that can be dimmed at a stranger’s discretion. The dependency was known. Dependencies, like debts, are known by everyone except the debtor until the creditor calls.

I have seen this configuration. In the dark years we lived by the convoy across the ocean, and every cabinet paper of that epoch understood one thing plainly: the artery was not ours. We did not pretend otherwise, and we did not leave the matter to hope. We built the second route, the third, the reserve behind the reserve - not because we distrusted our friend across the water, but because friendship is not a strategy and gratitude is not a supply line.

The official language speaks of technical restrictions and renewed tension. Renewed tension. What a gentle phrase for the discovery that your defensive grid answers to a private gentleman’s temperament. One is reminded of the landlord who discovers, mid-battle, that the drawbridge belongs to a neighbour.

What this requires is not indignation but engineering. A second constellation, contracted and paid for, under Kyiv’s own hand. Terrestrial links dug and hardened. Redundancy treated not as extravagance but as the very substance of sovereignty. The work of months, begun late - as such work always is.

And let no one in Washington mistake the lesson. An ally held by the switch teaches every nation watching to build its own switch. Empires that govern by the tap run the risk that the tap, once turned, is never trusted again. The throttling was a small act. Its consequences will be measured in decades.

16th day of the tenth month

A single valve now controls the flow of communication across an entire nation at war. This is the fact worth examining, and everyone is examining the wrong thing.

Start from the theoretical limit: a wartime communication network should be a field, not a wire - distributed across many frequencies, many orbits, many owners, so that no one hand can close it. The physics permits this. Low-earth orbit constellations can be launched by competing entities; spectrum can be divided; terminals can be made interoperable by specification, published and open, the way alternating current was standardized so that any generator could feed any grid. What exists instead is one constellation, one proprietor, one throttle. Ukraine’s entire battlefield nervous system runs through a single switch that sits in another country’s hands and, worse, in one man’s disposition.

The gap between resilience and dependency is precisely one design decision: open the terminal standard, publish the interface, and let three or four constellations interoperate. None of this is physically impossible. The rockets fly. The frequencies exist. The fact that it has not happened tells you the obstacle is not technical - it is that a monopoly is profitable and dependency is leverage, and both are preferred by the parties who could dissolve them.

The overlooked mechanism is the interface, not the satellite. Everyone marvels at the constellation; nobody asks who owns the protocol that lets a terminal speak to it. Control the specification and you control the grid, whatever the hardware. This is the lesson of every network ever built, and it is relearned each time at the price of a war.

I am impatient with the commentary about alliance politics. The politics is weather. The architecture is climate. A nation that permits its defense to run on a single proprietary frequency has not been betrayed when the throttle closes - it has been measured, and found to have skipped the step where engineers insist on redundancy.

We could build the field. We chose the wire. The distance between those two facts is a choice, made anew each budget cycle.

16th day of the tenth month

The throttling was not an event. It was a demonstration. A private man in one country reduced the speed of a network used by another country’s defenses, and the second country learned the terms of its dependence in an afternoon.

The stated cause was commercial restriction. The structural cause is older: whoever owns the wall decides who passes through it. Ukraine did not build this wall. It cannot repair it, replace it quickly, or open it by force. It can only ask. The man who owns it can raise the price, slow the flow, or close the gate, and no assembly in Kyiv can vote on any of it. This is what it means to fight a siege with borrowed provisions.

The Melian exchange, stripped of language: Ukraine has soldiers and a cause. The network’s owner has a switch. The switch outweighs the cause. The weak side understood this from the first month of the war and accepted the arrangement because fighting without the network was more dangerous than fighting beneath another man’s hand on it. Acceptance is not gratitude. It is arithmetic.

Note what the reporting shows. The dependence runs in both directions - the same terminals serve attack and retreat, the drone operator and the field surgeon. A single point of failure at the center of a national defense. The Americans call it a partnership. In practice, the smaller partner’s survival is contingent on the larger partner’s mood, and the larger partner has begun to price that mood.

The Ukrainian official spoke anonymously. Anonymity is what dependence sounds like when it speaks. He could not name the grievance openly, because the hand that throttles can also withhold.

I record this without instruction to anyone. The record is the instruction. A state that cannot control the infrastructure of its own defense has ceded a portion of its sovereignty, whatever its flags and speeches say. The speeches were excellent. The terminals do not listen to speeches.