Why Calling Starlink Indispensable in Ukraine Misses the Real Threat

Why Calling Starlink Indispensable in Ukraine Misses the Real Threat

Read enough breaking-news dispatches about the war in Ukraine and you will see the same sentence recycled until the ink wears thin. Starlink is indispensable. Europe cannot replace it anytime soon. End of story.

That is lazy consensus. Worse, it is dangerous.

Calling a single satellite constellation indispensable in modern warfare is a gift to every adversary with an electronic warfare pod, a software vulnerability, or a political lever. The real story is not that Kyiv relies heavily on low Earth orbit (LEO) satellite communications right now, nor that Brussels lacks a drop-in twin on a shelf today. The real story is that treating any single commercial network as irreplaceable confuses tactical convenience with strategic survival—and blinds defense planners to the architecture that actually endures under fire.

I have watched defense contractors and telecom operators spend tens of millions chasing shiny hardware while ignoring link resilience, spectrum agility, and ground-station fragility. When a signal drops in the mud outside Kharkiv or Zaporizhzhia, nobody cares about glossy brochure claims. People care whether packets move without getting geolocated or jammed into oblivion.

The Lazy Consensus Around "Irreplaceable" Satcom

The standard headline frames the issue as a binary race: can European operators—such as Eutelsat OneWeb or SES—match SpaceX's scale overnight? Framed that way, the answer is obviously no. SpaceX operates thousands of satellites in low Earth orbit, backed by rapid launch cadence, high-volume user terminals, and deep integration with battlefield workflows from artillery spotting to drone relays.

No single rival matches that exact combination at scale right now. Admitting that reality is basic honesty, not defeatism.

Where the lazy consensus goes off the rails is the leap from "hard to replace quickly" to "impossible to work around." Military communications have never survived on a single pipe. From field telephone wire to high-frequency (HF) radio, troposcatter links, tactical mesh radios, and fiber optics, resilient command-and-control networks rely on graceful degradation, not single-point perfection.

To be clear on the engineering terms, low Earth orbit (LEO) typically spans altitudes from roughly 500 to 2,000 kilometers, offering low round-trip latency compared to geostationary orbit (GEO) satellites sitting around 35,786 kilometers above the equator. Lower latency matters for real-time telemetry, unmanned aerial vehicle control loops, and tactical coordination. Yet lower altitude also means satellites move rapidly across the sky, requiring constant handoffs, phased-array beam steering, and tightly managed radio frequency (RF) spectrum.

When commentators treat Starlink as a magic shield rather than one layer in a contested RF environment, they miss two critical truths:

  • Concentration creates a bullseye. Any system that becomes the sole backbone of tactical connectivity turns into the highest-value target for electronic warfare (EW), cyber pressure, and legal or commercial friction.
  • Replacement does not mean cloning. A viable alternative does not need to replicate every consumer-grade feature of a commercial broadband terminal. It needs to pass high-priority command, targeting, and situational-awareness traffic when primary links degrade.

You Are Asking the Wrong Question About Europe and Kyiv

The usual debate asks whether the European Union can build a "Starlink killer" or substitute the entire network on short notice. That question sets up a straw man and guarantees a gloomy answer.

Building a massive LEO constellation from scratch takes years of satellite manufacturing, launch slots, ground infrastructure, and regulatory coordination. Even existing multi-orbit operators—combining LEO and medium or geostationary assets—face capacity limits, terminal availability hurdles, and differences in battlefield integration.

A sharper question is this: How do you make a force anti-fragile when commercial space assets are contested, throttled, or unavailable?

No. Not one-for-one. Anyone promising a turnkey swap in a few weeks is selling fairy tales.

Realistically, near-term substitution looks like heterogeneous redundancy. That means stitching together multiple transport paths: commercial LEO capacity where available, GEO and medium Earth orbit links for specific throughput or geographic coverage, hardened tactical radios for short-range line-of-sight or mesh hops, and terrestrial lines where frontlines stabilize. A command post does not need 200 megabits per second to pass coordinates or status updates; it needs a path that gets through when high-bandwidth links get hammered.

"Does Reliance on One Private Constellation Hand Over Strategic Leverage?"

Yes—if you fail to build alternatives. Any dependency on a single commercial vendor carries commercial, contractual, and geopolitical exposure. Even without malice, a single company faces hardware defects, software regressions, constellation management challenges, and competing global demands.

Blaming a vendor for existing is pointless. Building zero fallback options is malpractice.

"Why Doesn't Ukraine Just Switch Everything to Older or Non-LEO Systems?"

Because physics and latency are unforgiving. Traditional GEO links introduce noticeable signal delay due to distance, and many legacy military satcom systems lack the sheer bandwidth and agile, low-cost user terminals that made commercial LEO terminals so widespread at the tactical edge.

Switching "everything" to older systems would cripple bandwidth-hungry workflows overnight. Keeping commercial LEO while aggressively bolting on diverse backups is the pragmatic path—not romantic nostalgia for clunky gear.

What Contested Space Actually Looks Like on the Ground

Modern warfare turns the electromagnetic spectrum into a street fight. Every transmitter is a potential beacon. Every dish is a signature.

Imagine a scenario where an armored reconnaissance unit operates near a contested treeline with active electronic jamming. The crew relies on a compact satellite terminal to upload drone feeds and receive fire-mission updates. If jamming degrades that specific frequency band or forces power spikes that increase detection risk, the unit faces a stark choice: push through a degraded link, shift to an alternative frequency or backup radio path, or move and re-establish contact.

In that environment, resilience is measured in continuity of mission, not peak speedtest numbers. A network that drops from fast video streaming to reliable low-rate data and voice beats a network that looks great on paper and goes dead under targeted interference.

Ground infrastructure is another blind spot in popular coverage. Satellites in orbit get all the romantic attention, yet space links rely on gateways, routing nodes, power generation, and fiber backhaul on Earth. Disruptions to power, cooling, or terrestrial transit can choke connectivity just as effectively as orbital or RF issues.

Heavyweights in space and defense—from orbital dynamics pioneers like Tsiolkovsky and Von Braun on the theoretical and rocketry side to modern defense analysts studying space resilience and multi-domain command—have long emphasized that architecture beats heroics. A single brilliant asset cannot carry an entire campaign indefinitely without backup pathways and disciplined spectrum management.

The Uncomfortable Trade-Offs of My Own Argument

Let's put cards on the table. Pushing for multi-path resilience and reduced single-vendor reliance is not free, and pretending otherwise would make me just as sloppy as the pundits I am criticizing.

First, complexity rises. Managing multiple satcom providers, different terminal types, varied encryption and routing policies, and fallback radios increases training burden and logistics friction. Conscripts and junior officers do not want five manuals when artillery starts falling.

Second, cost and procurement speed can suffer. Fragmenting orders across multiple systems can reduce unit-cost economies of scale and slow down standardization if bureaucracies over-complicate integration.

Third, performance can dip during transitions. Failing over from a high-throughput LEO link to a narrower backup channel means slower transfers and tighter bandwidth discipline. Commanders have to accept lower data rates in exchange for survival.

Those trade-offs are real. Ignoring them leads to bloated, fragile Frankenstein networks. Facing them head-on forces discipline.

How to Build Real Resilience Instead of Chasing Headlines

If you run defense procurement, telecom engineering, or enterprise continuity planning, stop obsessing over declaring a single "winner" and start engineering for failure.

  1. Audit for single points of failure across the full chain. Map every link from sensor or handset to satellite, gateway, core network, and power source. If cutting one cable, jamming one band, or losing one vendor darkens an entire sector, fix the topology first.
  2. Design for graceful fallback, not identical speed. Define minimum viable communications for every unit or site. Know which traffic is mission-critical (command, navigation/timing checks, essential telemetry) and which traffic is nice-to-have (heavy file transfers, non-essential video).
  3. Invest in spectrum agility and low-signature discipline. Train operators on directional masking, power control, rapid relocation, and multi-band options so adversaries cannot easily pattern-of-life or saturate a single channel.
  4. Treat commercial space as a force multiplier, not a sovereign crutch. Use commercial LEO and multi-orbit capacity aggressively where it excels, while funding sovereign or allied resilient paths, tactical mesh alternatives, and hardened ground support so no single lever controls survival.

Headlines love clean absolutes: indispensable or obsolete, unstoppable or doomed. Real-world engineering lives in the messy middle—where redundant paths, disciplined operators, and honest risk math keep the signal alive when the noise gets loud.

Build the backup before the signal drops.

LB

Logan Barnes

Logan Barnes is known for uncovering stories others miss, combining investigative skills with a knack for accessible, compelling writing.