Vendor lineage
SpaceX - low orbit, and what it does to the latency floor
The constraint that could not be engineered away was engineered around, by moving the satellites.
SpaceX operates a low-Earth-orbit satellite constellation, and its relevance to this timeline is a single number. Where geostationary orbit sits around 36,000 kilometres up, low orbit is a few hundred - which collapses the round-trip latency from roughly half a second to a range that ordinary protocols and interactive applications can work with.
The trade is not free and it is the reason nobody did this earlier. A satellite at that altitude is only overhead for minutes, so continuous coverage needs thousands of them, constant handover between them, and a launch economics that makes replacing the constellation routine rather than catastrophic.
Read beside the Hughes entry it makes a general point about limits: the geostationary latency floor was never a technology problem to be solved by better modems. It was a consequence of a choice of orbit, and it moved only when the choice did.
The orbit is the technical story. The one that belongs beside the Huawei and Atos entries is what happened when the constellation became a battlefield network. After the February 2022 invasion SpaceX shipped terminals to Ukraine, at first free of charge and with no military contract, and they became the communications layer for a great deal of the war.
In September 2022, according to the biography of the company's chief executive, Ukraine sent six explosive-laden drone submarines toward the Russian fleet at Sevastopol, guided by Starlink. The book's first account said coverage had been switched off within a hundred kilometres of the Crimean coast; the executive replied that the regions had never been activated and nothing had been deactivated, and the biographer then clarified that Ukraine had believed coverage reached Crimea when it did not, had asked for it to be enabled, and had been refused. The drones lost connectivity and washed ashore. The executive's stated reason was that agreeing would have made the company complicit in a major act of war, and that the service's terms prohibit offensive military use.
Which of the two verbs is right - disabled or declined to enable - was argued over for a week and should be recorded as contested, because it is. What is not contested is the part that matters to this catalogue: on one night, whether a stretch of coastline had connectivity during an allied state's military operation was decided by one private individual, on the basis of a conversation with a foreign ambassador and a company's terms of service. No treaty governed it and no legislature was consulted. A vendor's terms of service were, for that night, the law of a battlefield.
The remedy is the instructive part, and it is the same remedy the Atos entry records from a different direction. The US military subsequently contracted for the service on its own terms, and the company began building a separate constellation for the government that would be owned and controlled by it. The customer that cannot accept a supplier's discretion buys the supplier's discretion. Three senators asked the Defense Secretary to explain what had happened; the questions they asked were the ones that apply to every supplier, and the answer was the same as everywhere else: it depends on who owns the switch.
- SpaceX - American spaceflight company (Wikipedia)
- Founding year: 2002
- CBS News, September 2023: an excerpt from Walter Isaacson's biography describes Ukraine attempting a September 2022 attack on the Russian fleet at Sevastopol with six explosive-laden drone submarines guided by Starlink, and Musk telling engineers to turn off coverage within 100 kilometres of the Crimean coast; Musk responded that the regions in question had never been activated and SpaceX had deactivated nothing, and that agreeing to the request would have made SpaceX explicitly complicit in a major act of war
- Senators Shaheen, Warren and Duckworth's letter to the Defense Secretary, September 2023, recording Isaacson's clarification that the Ukrainians thought coverage was enabled to Crimea when it was not and that Musk declined to enable it, and Musk's statement that Starlink's terms of service prohibit offensive military use as a civilian system, and that Starshield, built for the US government, would be owned and controlled by it
- PBS: Musk was not on a military contract when he refused the request, having provided terminals to Ukraine free after the February 2022 invasion; in the months after, the US military funded and formally contracted with Starlink for continued support
- CNN on the biography: Musk replied that he would not turn coverage on for Crimea because Ukraine was going too far and inviting strategic defeat; officials relying on the charity of a private company for battlefield communications also faced a standoff over who would pay for the terminals