Bitcoin Survives 72% Cable Failures But 5 Providers Could Cripple It

A new Cambridge study just answered the question nobody had rigorously tested: What would it actually take to break Bitcoin’s network?

The answer is more complicated than Bitcoin maximalists want to admit—and more resilient than critics claim.

Researchers at the Cambridge Centre for Alternative Finance analyzed 11 years of Bitcoin network data against 68 verified submarine cable fault events. They ran 1,000 Monte Carlo simulations per scenario to test infrastructure resilience.

The findings:

Between 72% and 92% of the world’s inter-country submarine cables would need to fail simultaneously before Bitcoin experiences significant node disconnection.

Random cable failures barely register. Over 87% of real-world cable faults caused less than 5% node impact.

But here’s the catch:

A targeted attack on the top 5 hosting providers by node count—Hetzner, OVH, Comcast, Amazon, and Google Cloud—could cripple Bitcoin with just 5% routing capacity removal.

Does that validate Bitcoin’s resilience narrative, or is this overconfident given the targeted attack vulnerability?

It validates the resilience narrative.

But it also reveals the real threat: not random infrastructure failures, but coordinated attacks on specific chokepoints.

Let me explain why Bitcoin is far more resilient than people think—and why the hosting provider vulnerability is both a risk and an acceptable trade-off.

Random Failures Don’t Threaten Bitcoin (But Targeted Attacks Do)

The Cambridge study tracked 68 real-world submarine cable failures over 11 years.

The impact on Bitcoin? Almost nothing.

87% of those failures caused less than 5% node impact. The largest single event—when seabed disturbances off Côte d’Ivoire damaged 7-8 cables simultaneously in March 2024—knocked out 43% of regional nodes but affected only 0.03% of the global network (5-7 nodes).

The correlation between cable failures and Bitcoin’s price? -0.02. Basically zero.

Infrastructure disruptions are invisible against daily price volatility.

So random cable failures barely impact Bitcoin.

But targeted attacks are different.

While random failures require 72-92% of cables to fail before Bitcoin suffers disruption, a targeted attack on cables with the highest betweenness centrality (the chokepoints between continents) drops that threshold to 20%.

And targeting the top five hosting providers? Just 5% routing capacity removal achieves the same impact.

Which threat is more realistic?

The top 5 hosting providers is a more realistic threat.

Here’s why:

Random cable failures are acts of nature. Earthquakes. Anchor drags. Seabed disturbances. They’re unpredictable and scattered.

Targeted attacks are acts of state.

Coordinated regulatory shutdowns of hosting providers. Deliberate severing of critical cable routes. Government pressure on Amazon, Google Cloud, Hetzner, OVH, Comcast.

That’s the real threat.

Not a natural disaster that randomly damages 72% of submarine cables. But a coordinated state-level attack that targets the specific infrastructure Bitcoin depends on.

And that’s a fundamentally different adversary.

Random failures? Bitcoin survives easily.

Targeted state attacks on hosting providers? That’s a credible risk.

China’s Mining Ban Actually Helped Bitcoin’s Resilience (Paradox)

The study tracked how Bitcoin’s resilience evolved over time.

The findings are counterintuitive:

Bitcoin was most resilient in 2014-2017 when the network was geographically diverse. Critical failure threshold: 0.90-0.92.

Resilience declined sharply during 2018-2021 as the network grew rapidly but concentrated geographically. It hit its lowest point of 0.72 in 2021 during peak mining concentration in East Asia.

Then China banned mining in 2021. The network was forced to redistribute.

Resilience partially recovered to 0.88 in 2022, then settled at 0.78 in 2025.

Does that mean China banning mining actually helped Bitcoin’s long-term resilience?

It seems so.

Here’s the paradox:

When China hosted the majority of Bitcoin mining, the network was geographically concentrated. That created a single point of failure.

If China decided to shut down all mining operations (which they did), or if submarine cables connecting China to the rest of the world were severed (which could happen in a Taiwan conflict), Bitcoin’s hashrate would crater.

But China’s ban forced redistribution.

Miners migrated to North America, Europe, Central Asia. The network became more geographically diverse.

And geographic diversity equals resilience.

So China’s hostile action—banning mining—paradoxically strengthened Bitcoin’s infrastructure by eliminating the concentration risk.

That’s adaptive resilience in action.

Bitcoin doesn’t have a central authority that can proactively plan for infrastructure threats. But when a threat materializes (China ban), the network adapts.

Miners relocate. Nodes redistribute. The system self-organizes toward greater resilience.

That’s a feature, not a bug.

TOR Adoption Increased Resilience (But Created New Vulnerability)

Here’s the surprising finding:

64% of Bitcoin nodes now use TOR (The Onion Router), making their physical location unobservable.

The assumption has been that this inability to observe location might hide fragility. If TOR nodes are geographically concentrated, the network could be more vulnerable than it appears.

The Cambridge researchers tested this and found the opposite.

TOR relay infrastructure is heavily concentrated in Germany, France, and the Netherlands—countries with extensive submarine cable and land border connectivity.

An attacker trying to disrupt TOR relay capacity by cutting cables faces a compound problem: those countries are among the hardest to disconnect.

The four-layer model (accounting for TOR) consistently showed higher resilience than clearnet-only baseline, with TOR adding 0.02 to 0.10 to the critical failure threshold.

Does that surprise you?

Yes.

And it also tells me that if TOR is targeted, it could affect BTC infrastructure and probably pricing as well.

Here’s the nuance:

TOR adoption increases resilience against random cable failures because TOR relays are in highly connected countries.

But TOR creates a new vulnerability: concentration in specific jurisdictions.

If Germany, France, and the Netherlands coordinated to shut down TOR relay infrastructure—or if those countries’ internet connectivity was disrupted—64% of Bitcoin nodes would be affected.

That’s a different threat model than random cable failures. It’s a targeted regulatory attack on TOR infrastructure.

And while it’s unlikely (those countries are democracies with strong internet freedom norms), it’s more realistic than 72% of submarine cables randomly failing.

So TOR adoption is both a strength (increases resilience to random failures) and a vulnerability (creates concentration risk in specific jurisdictions).

Trade-offs, always trade-offs.

Adaptive Self-Organization: Strength or Weakness?

The study frames Bitcoin’s resilience evolution as “adaptive self-organization.”

TOR adoption surged after censorship events:

Iran’s internet shutdown in 2019
Myanmar coup in 2021
China mining ban in 2021

The Bitcoin community shifted toward censorship-resistant infrastructure without any central coordination.

Is that a strength (proves decentralization works), or a weakness (reactionary rather than proactive)?

It’s a strength.

Here’s why:

It actually shows that the network is self-governable. When a threat emerges, the community adapts—without waiting for a central authority to coordinate a response.

And technologies like DAOs could actually improve the infrastructure further.

Imagine a Bitcoin infrastructure DAO that:

Monitors geographic distribution of nodes and mining
Incentivizes node operators in underrepresented regions
Funds TOR relay infrastructure in strategic locations
Coordinates responses to infrastructure threats

That’s proactive resilience, not just reactive adaptation.

And it’s possible precisely because Bitcoin is decentralized. No central authority means no central point of failure. But it also means the community can coordinate voluntarily to strengthen infrastructure.

DAOs, governance tokens, quadratic funding—these mechanisms allow decentralized networks to act collectively without centralization.

That’s the future of adaptive resilience.

Not waiting for crises and reacting. But proactively building redundancy and geographic diversity through decentralized coordination.

The Hosting Provider Vulnerability: Acceptable Trade-Off?

Here’s the uncomfortable truth:

A targeted attack on just 5 hosting providers—Hetzner, OVH, Comcast, Amazon, and Google Cloud—could cripple Bitcoin by removing just 5% of routing capacity.

Does that undermine the decentralization narrative, or is it an acceptable trade-off given 72-92% resilience to random failures?

There had to be some sort of trade-off.

Here’s the reality:

Running Bitcoin nodes requires infrastructure. Servers. Bandwidth. Hosting providers.

Most node operators don’t run physical servers in their homes. They rent cloud infrastructure from hosting providers.

Why? Because it’s cheaper, more reliable, and easier to scale.

So yes, Bitcoin nodes are concentrated on a few major hosting providers. That creates a vulnerability.

But it’s an acceptable trade-off.

Here’s why:

Look at the providers we’re talking about: Amazon and Google.

These companies are going nowhere. They’re some of the most powerful corporations in the world.

If they were attacked, I wouldn’t be surprised if they had more power to fight back than the current countries currently in war.

Think about it:

Amazon Web Services hosts a massive portion of the internet. U.S. government agencies, Fortune 500 companies, critical infrastructure—all running on AWS.

An attack on AWS would affect far more than Bitcoin.

It would disrupt government services, financial systems, corporate operations. The economic and political consequences would be massive.

So while AWS is technically a single point of failure for Bitcoin, it’s also protected by the fact that disrupting AWS would be catastrophic for the entire economy.

Same logic applies to Google Cloud, Comcast, and other major providers.

They’re too big to fail. And too powerful to attack without massive collateral damage.

So yes, the hosting provider vulnerability exists. But it’s mitigated by the fact that those providers are systemically important and heavily defended.

Is that perfect decentralization? No.

Is it resilient enough? Yes.

What We’ve Observed: Infrastructure Resilience Doesn’t Equal Price Stability

The study concludes:

“With the Strait of Hormuz currently disrupted and Middle East war ongoing, the answer is probably nothing, unless someone is deliberately targeting specific cables and hosting providers.”

Does that match what we’ve observed with oil/BTC price dynamics?

No. This is unrelated to the oil story.

Here’s the key distinction:

Infrastructure resilience ≠ Price stability

We covered how when oil spiked to $100 due to geopolitical tensions, Bitcoin’s price dropped—not because mining costs rose (only 8-10% of hashrate is oil-sensitive), but because macro stress triggers risk-off behavior.

That’s a price dynamic, not an infrastructure failure.

Bitcoin’s network kept running. Nodes stayed online. Blocks kept getting mined.

But the price fell anyway.

Because Bitcoin’s network resilience doesn’t protect it from macroeconomic and psychological factors that drive price volatility.

Geopolitical shocks → risk-off sentiment → capital flees volatile assets → Bitcoin price drops.

None of that requires infrastructure failure.

So the Cambridge study validates that Bitcoin’s network can survive cable failures and regional conflicts. But it doesn’t validate that Bitcoin’s price is immune to those same events.

Two different questions. Two different answers.

Infrastructure: Resilient.

Price: Still volatile and correlated with macro risk sentiment.

Infrastructure resilience doesn’t guarantee market success.

What This Really Means

Cambridge study shows Bitcoin can survive 72-92% of submarine cables failing, but a targeted attack on 5 hosting providers could cripple it. This validates resilience while revealing the real threat: coordinated state attacks on specific chokepoints.

Here’s what we know:

Validates Bitcoin’s resilience narrative. 87% of 68 real-world cable failures caused less than 5% node impact. Random infrastructure failures invisible against price volatility. But targeted attacks on hosting providers (5% routing capacity) could cripple network—that’s the realistic threat.

Top 5 hosting providers is realistic threat, not random failures. Random = acts of nature (earthquakes, anchor drags). Targeted = acts of state (coordinated regulatory shutdowns, deliberate cable severing). Fundamentally different adversaries: Bitcoin survives one easily, vulnerable to the other.

China’s mining ban paradoxically helped resilience. Network most resilient in 2014-2017 (geographic diversity, 0.90-0.92), least resilient in 2021 (China concentration, 0.72). Ban forced redistribution, recovered to 0.78 in 2025. Hostile action strengthened infrastructure by eliminating concentration risk.

TOR adoption increased resilience but created new vulnerability. 64% of nodes use TOR. Relay infrastructure concentrated in Germany/France/Netherlands (extensive connectivity = harder to disrupt). Added 0.02-0.10 to critical failure threshold. But if TOR targeted, could affect BTC infrastructure and pricing—new concentration risk in specific jurisdictions.

Adaptive self-organization proves decentralization works. Bitcoin community shifted to censorship-resistant infrastructure without central coordination after Iran shutdown, Myanmar coup, China ban. Shows network is self-governable. DAOs could improve infrastructure further through proactive resilience (incentivize geographic diversity, fund TOR relays).

Hosting provider vulnerability is acceptable trade-off. 5 companies (Hetzner, OVH, Comcast, Amazon, Google) could cripple Bitcoin, but these are systemically important. Amazon/Google have more power to fight back than current warring nations. Disrupting AWS would affect government, finance, corporate ops—massive collateral damage protects Bitcoin indirectly.

Infrastructure resilience unrelated to oil/BTC price dynamics. Strait of Hormuz disrupted, but network keeps running. Price fell when oil spiked (risk-off behavior), not infrastructure failure. Network resilience doesn’t protect against macroeconomic/psychological factors driving price volatility.

Bitcoin could fail despite infrastructure resilience. Network surviving cable failures doesn’t guarantee market success. Infrastructure robust, but price still volatile and correlated with macro sentiment. Other cryptocurrencies with real utility could succeed even if Bitcoin struggles.

Cambridge study proves Bitcoin’s network is resilient to natural disasters and random failures. But price remains vulnerable to targeted attacks and macro stress.