When Amazon Crashed, "Decentralized" Blockchain went Down With it
Description
This story was originally published on HackerNoon at: https://hackernoon.com/when-amazon-crashed-decentralized-blockchain-went-down-with-it.
AWS outage exposed crypto's centralization crisis: 37% of Ethereum nodes went dark. Decentralized solutions race to fix blockchain's Achilles heel.
Check more stories related to web3 at: https://hackernoon.com/c/web3.
You can also check exclusive content about #blockchain-infrastructure, #decentralization, #crypto-centralization, #rpc-providers, #ethereum, #web3-infrastructure, #aws-outage, #aws-in-web3, and more.
This story was written by: @johnwrites. Learn more about this writer by checking @johnwrites's about page,
and for more stories, please visit hackernoon.com.
The October 2025 AWS outage revealed blockchain's dirty secret: despite claims of decentralization, 37% of Ethereum nodes and 70% of RPC traffic rely on centralized providers like AWS, Infura, and Alchemy. When AWS crashed for 14-16 hours, users couldn't access blockchains even though protocols kept running. The "bootstrap trap" forces new chains into expensive centralized services, creating censorship risks and innovation bottlenecks. Projects like Lava Network, Pocket Network, and Ankr are racing to build merit-based, decentralized infrastructure before the next outage strikes.
United States
