A recent outage at Amazon Web Services (AWS) froze thousands of applications and reignited debate about web3’s reliance on centralized cloud providers.
The disruption exposed how deeply crypto platforms still depend on Web2 infrastructure for systems meant to operate without interruption.
How a Centralized Outage Crippled Decentralized Systems
On October 20, 2025, the AWS US-EAST-1 region went dark for nearly three hours due to a DNS bug in its DynamoDB service, freezing thousands of applications worldwide. The outage, which began around 07:55 UTC and was resolved by 09:35 UTC, stemmed from a latent software defect that created an empty DNS record, requiring manual intervention to fix.
The AWS outage triggered a chain reaction, disrupting major tech platforms like Lyft, Peloton, and Roblox. The crypto and web3 industry also experienced widespread disruption. Coinbase Advanced, a key trading platform, halted operations entirely, leaving users locked out of their accounts and unable to execute trades.
Base, Coinbase’s Ethereum Layer-2 blockchain, experienced severe slowdowns, with transaction throughput dropping dramatically as AWS-hosted infrastructure failed. Other ecosystems weren’t spared: Solana saw intermittent node failures, Ethereum’s decentralized apps (dApps) faced API disruptions, and Polygon reported partial outages in its scaling solutions.
This event called into question the fundamental promise of blockchains to create applications that can operate continuously without relying on any single server, company, or government. The failure revealed how single points of failure continue to compromise web3’s vision of unstoppable applications.
“The recent AWS outage is a reminder that web3’s promise of decentralization can’t rely on centralized backbones. Every outage like AWS’s shows the cost of centralization, not just in downtime but in trust,” said Evgeny Ponomarev, co-founder of Fluence.
Decentralized Compute Shows Promise Amid Technical Hurdles
Decentralized Physical Infrastructure Networks (DePIN) introduces a new model for provisioning compute resources. Instead of depending on centralized data centers, DePIN connects a global pool of independent providers through a peer-to-peer marketplace.
Each server contributes compute, storage, or GPU capacity that is verified on-chain for transparency. Control is distributed, not owned, and the system scales organically as new participants join.
This structure replaces massive, single-region data centers with a distribution across thousands of independent servers. If one fails, the workload can be seamlessly migrated to other servers or data centers.
This distributed model also drives a significant cost advantage. By tapping into idle global compute capacity, DePIN providers achieve greater efficiency, often reporting costs that are up to 85% lower compared with major hyperscalers. For instance, Fluence is one of several projects developing decentralized compute networks under the DePIN model.
The platform connects verified data-center providers that meet common compliance standards, allowing developers to run workloads across distributed CPU and GPU resources instead of relying solely on centralized clouds. Fluence’s network currently supports general-purpose computing through virtual CPUs and GPU-based processing for AI and high-performance tasks.
According to company data, it operates about 11,000 virtual CPUs and 70 terabytes of memory across nine providers. Clients using the network include Antier Solutions, NEO Foundation, and Nodes.Garden.
Other DePIN projects such as Akash Network, Aethir, and io.net are pursuing similar approaches for distributed infrastructure, covering cloud marketplaces and large-scale GPU aggregation. Together, these efforts reflect an emerging shift toward a more diversified compute layer for web3.
Right now, DePIN is reimagining physical infrastructure, including telecom and transportation networks, energy grids, and more. As it was stated in the recent a16z 2025 State of Crypto report, the World Economic Forum projects the DePIN category will grow to $3.5 trillion by 2028.
While DePIN cannot yet match the immediate global scale of a hyperscaler, its open source foundations make it far more adaptable. By building on open standards, workloads can move across multiple providers with minimal friction. Developers gain real portability instead of being locked into a single vendor’s API or billing model.
In practice, decentralized networks like Fluence are already showing how open source infrastructure can connect independent providers into one interoperable fabric that behaves like a cloud, yet remains fully portable and transparent.
Evgeny explained:
This open, cross-provider cloud model offers a path toward resilience that centralized architectures cannot match. As DePIN matures, it may redefine the baseline for reliability by making the cloud itself open source and the act of migration as simple as redeploying code.
Source: https://beincrypto.com/aws-outage-web3-depin-fluence/
