Starlink Built a Satellite Mesh. The Routing Authority Is Still Terrestrial.
by Nick Clark | Published March 27, 2026
Starlink deployed thousands of low-earth orbit satellites connected by inter-satellite laser links, creating a mesh network that spans the planet. Traffic can hop between satellites without touching the ground. But routing authority, session management, handover policy, and traffic prioritization remain governed by terrestrial ground stations. The mesh routes packets. It does not carry its own governance. That requires protocol-level semantics where authority travels with the content.
Starlink's constellation is a remarkable engineering achievement. Inter-satellite laser links enable traffic to traverse the orbital mesh at the speed of light in vacuum, potentially faster than terrestrial fiber for long-distance routes. The gap described here is not a failure of SpaceX's engineering. It is a structural property of how routing authority relates to the physical mesh.
The mesh forwards. The ground governs.
When a Starlink satellite receives a packet, it forwards it along the mesh toward its destination. The routing decisions that determine which path the packet takes, which satellite handles the next hop, and how handovers work as satellites move relative to ground terminals are computed and distributed by the ground segment.
Ground stations upload routing tables, manage satellite ephemeris data, coordinate frequency assignments, and handle session state for user terminals. The satellites execute these instructions. They do not independently govern routing policy.
This means the mesh has a structural dependency on terrestrial infrastructure for every governance decision. Which traffic gets priority, how congestion is managed, how handovers are sequenced, which orbital planes carry which traffic classes: all of this originates on the ground.
Why this matters for satellite networking
A satellite constellation where routing governance depends on ground contact faces specific structural constraints. Ground station coverage is not uniform. Over oceans, polar regions, and adversary-controlled territory, ground contact may be intermittent or unavailable. During these periods, satellites must operate on cached routing tables that may not reflect current conditions.
Regulatory environments vary by jurisdiction. A satellite transiting from one country's airspace to another may need to comply with different traffic policies. If those policies are managed terrestrially, the governance update depends on ground station availability in the relevant jurisdiction.
Military and emergency use cases require routing that persists through ground infrastructure disruption. If the authority to route is terrestrial, losing ground stations means losing routing governance, even if the orbital mesh remains physically intact.
What memory-native protocol semantics address
A memory-native protocol embeds routing policy, trust scope, mutation permission, and propagation rules into the content itself. Each packet or session carries the authority for its own routing rather than depending on externally held state.
In a satellite mesh operating on memory-native semantics, each satellite would hold locally governed routing policy validated through scoped consensus with its orbital neighbors. Routing decisions would be made by the mesh itself based on the authority carried by each packet and the policy held by each node.
Handovers between satellites would be governed by the trust relationships between nodes, not by ground-computed tables. Congestion management would be handled through local policy that adapts to observed conditions. Regulatory compliance would be encoded in the routing authority carried by the traffic, not imposed by jurisdiction-specific ground stations.
The ground segment would not disappear. It would shift from governing routing to providing initial policy configuration and long-term planning. The operational routing authority would live in the mesh itself.
The remaining gap
Starlink built the physical mesh. The remaining gap is in the protocol layer: whether the routing authority can live in the mesh itself rather than being uploaded from the ground. That transition requires protocol semantics where governance travels with the content rather than being held by the infrastructure.
