New data from Cambridge's Centre for Alternative Finance shows Ethereum's decentralization narrative has a cloud computing problem. The CCAF found that 31% of global Ethereum beacon node activity is based in the United States, with infrastructure heavily clustered on three cloud providers: Amazon Web Services (AWS), Hetzner, and OVH.
The CCAF dashboard explicitly emphasizes the need for greater geographic distribution to improve network security and resilience. Cloud providers experience outages, and when a large portion of Ethereum’s validator set depends on the same underlying infrastructure, a routine cloud outage becomes a potential network stability event.
Ethereum currently boasts more than 880,000 validators, a number that has grown substantially since the network’s transition to proof-of-stake during the Merge in September 2022. In earlier analyses from 2022, AWS alone was found to host over 50% of Ethereum nodes. The reliance on three major cloud providers, AWS, Hetzner, and OVH, means that over two-thirds of total node share has at times been concentrated among just those platforms.
The network’s security model assumes a distributed validator set. The growth to over 880,000 validators post-Merge reflects genuine adoption of the staking model, but the concentration creates tail risks. Price stability could be affected if a major provider disruption or regulatory action suddenly took a significant percentage of validators offline.
The CCAF dashboard underscores the need for broader geographic distribution to bolster security and resilience. Cloud outages can translate into network stability events when a large portion of validators relies on the same underlying infrastructure. For investors, the takeaway is that while the staking model has gained traction, concentration risk remains a factor that could influence network stability and, in turn, price dynamics if disruption or regulatory actions impact a sizable share of validators.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.
