Share article

Bitcoin$62,502.09 sells itself as a network that cannot be shut down. Cambridge researchers just put a hard number on the part traders and operators tend to ignore: the internet is physical, and the chokepoints are countable. Their modeling suggests a coordinated hit on key subsea cables and a handful of routing providers could isolate up to 95% of Bitcoin$62,502.09's public clearnet routing capacity, effectively stranding most nodes from each other even if miners keep hashing.[1]
That is not a price chart setup, but it is a narrative that matters. When markets get stressed, connectivity becomes liquidity. The key "level" to watch here is not Bitcoin$62,502.09 support or resistance, it is infrastructure concentration, especially where nodes sit and how they route.

Enjoy articles without ads?

Register for free and get unlimited access to all articles.

What the Cambridge team actually studied

The work comes from the Cambridge Centre for Alternative Finance, with researchers Wenbin Wu and Alexander Neumueller presenting what they describe as the first longitudinal look at Bitcoin's "physical layer" resilience. The paper (hosted on arXiv) treats Bitcoin's peer-to-peer overlay as dependent on something far less decentralized: inter-country internet links and the Autonomous System Networks (ASNs) that move traffic.

Instead of hand-waving about "the internet will route around damage," the researchers simulate failure using a cascade model. The idea is straightforward: sever enough critical links and the remaining paths get overloaded or disappear, producing fragmentation where nodes cannot maintain connections to the wider network.

A big takeaway is that random damage is not the scary case. The scary case is targeted damage.

Random outages: surprisingly resilient, until they are not

If subsea cable failures happen randomly, the model says Bitcoin's public node network is mostly fine. The researchers estimate that between 72% and 92% of inter-country submarine cables would need to be destroyed before the network experiences "significant fragmentation," defined as more than 10% of nodes disconnecting.
That is a high bar, and it matches real-world intuition: cables break, ships drag anchors, repairs happen, and traffic reroutes. Markets rarely price in "random cable cuts" because the base rate is manageable and the internet has redundancy.[2]

So if you are looking for the invalidation of the doom thesis, it is this: accidental failures do not appear sufficient to meaningfully fracture Bitcoin's public node connectivity under the assumptions of the model.

Targeted cuts: the threshold drops hard

The paper's sharper warning is about coordinated attacks that pick targets based on network centrality. When the model prioritizes "high-betweenness" cables (links that sit on a large share of shortest paths), the failure threshold reportedly drops from 72% to around 20%. Translation: you do not need to break most of the ocean, you need to break the right parts of it.[3]

The researchers flag 11 critical Europe to North America cables as especially important. That corridor matters because Europe and North America host a large share of public infrastructure, exchanges, cloud regions, and routing hubs. If you can meaningfully degrade transatlantic connectivity, you can create regional partitions that are not just slow, but structurally separated.
For Bitcoin, a partitioned network is not instantly "dead," but it can get weird fast: delayed block propagation, diverging mempools, higher orphan risk, and a messy user experience for any service that assumes consistent global visibility.

The real choke point is not the ocean, it is who hosts the nodes

The most headline-grabbing number is not about cables at all. The model also looks at the ASNs that host and route Bitcoin nodes. According to the study summary, a targeted takedown of the top five ASNs hosting Bitcoin nodes:

  • Hetzner
  • OVH
  • Comcast
  • Amazon
  • Google Cloud

could wipe out roughly 95% of the network's clearnet routing capacity.

Even if you argue about definitions (capacity vs count, public vs private nodes), the direction is hard to ignore: Bitcoin nodes cluster where bandwidth is cheap, provisioning is easy, and uptime is sold as a product. That is great for convenience, and bad for adversarial resilience.

This is where the "decentralization" marketing meets the reality of modern ops. A lot of Bitcoin's public face sits in a small number of data centers, clouds, and ISPs. Those entities do not need to coordinate to become a single point of failure. Concentration does that for them.

The TOR paradox: privacy helps, but it can move the fragility

Bitcoin has been adapting. One major shift is the rise of Tor as a transport layer for nodes. The researchers highlight a dramatic change: from "a few dozen" Tor-enabled Bitcoin nodes in 2014 to about 64% of the network by 2025.
That sounds bullish for censorship resistance, and it often is. But it also sets up what the source calls a "TOR paradox." Routing through Tor can reduce reliance on conventional clearnet paths and make targeted censorship harder, but it also introduces dependencies on the Tor network's own health, performance, and potential chokepoints.

From a risk perspective, the key question is not "Tor good or bad," it is where the bottleneck moves. If clearnet concentration is replaced by Tor concentration, you still have a systemic fragility, just with a different label.

Why traders and operators should care (even if the chain keeps running)

This research is not saying Bitcoin can be "turned off" by cutting a few cables. Mining would continue wherever power and connectivity exist. Some nodes would remain reachable. Satellite relays and alternative links exist in niche forms. Also, the study focuses on public nodes, not every private node inside institutions.
But market impact does not require full shutdown. It requires uncertainty.

A serious connectivity event could lead to:

  • Exchange instability: degraded connectivity between matching engines, wallets, and nodes can trigger withdrawal pauses or deposit delays.
  • Confirmation confusion: users in one region may see different propagation timing than another, which becomes a support nightmare.
  • Volatility: traders will price the operational risk fast, especially if social feeds fill with "Bitcoin split" narratives, even when consensus is intact.
  • MEV and latency edges: propagation delays create opportunities for sophisticated actors while retail gets rekt on timing.
The clean framing is this: the protocol may be decentralized, but coordination risk still shows up in price.

Mitigation is possible, but it is not free

If this paper gets traction, expect the practical response to focus on reducing concentration:

  • More geographic diversity for public nodes, especially outside the Europe and North America backbone.
  • Multi-homing and diverse upstream providers so a node is not captive to one ASN.
  • More non-cloud hosting and community-run infrastructure, even if it is harder to maintain.
  • Better peer selection and routing hygiene at the software layer to avoid everyone clustering around the same "easy" endpoints.
None of that is glamorous. It is ops work, and ops work costs money. The upside is resilience. The downside is convenience.[4]

Watchlist takeaways

  • Concentration is the tell: keep an eye on where public nodes are hosted and whether cloud and ISP dominance is rising or falling.
  • Transatlantic infrastructure is a hotspot: the study highlights 11 Europe to North America cables as especially critical.
  • The big number to remember is 95%: the model suggests the top five ASNs could represent most clearnet routing capacity for public nodes.
  • Tor adoption is a double-edged hedge: 64% by 2025 signals adaptation, but also shifts dependency to different infrastructure.
Bitcoin does not need perfect decentralization to work, it needs enough decentralization when things get adversarial. Cambridge's message is simple: the weak link is not the code, it is the pipes.