The AWS outage is proof that a decentralized web isn’t just desirable — it’s essential | Opinion

 Not any more. The latest generation of web3 infra is faster, cheaper, and more reliable than anything that’s gone before and is capable of giving the leading cloud providers a run for their money. Crypto networks like Bitcoin 

 have operated with 100% uptime for over a decade, while DePIN has shown that enterprises can have their needs met by decentralized networks that connect them with the resources they need to thrive.

If Bitcoin is the money of last resort, blockchain is the infrastructure of last resort. Not because that’s the only occasion when it should be utilized, but because such occasions are precisely when it shines. You don’t need a decentralized web until you do.

As the old political maxim goes, “Never let a crisis go to waste.” Make no mistake, the AWS outage was a crisis that was waiting to happen. On October 20, it detonated with far-reaching consequences, the aftershocks of which are still being felt. On this occasion, it was “just” AWS that was toppled. Imagine what would happen if the gremlin in the works also took out Azure and Google Cloud? The internet as we know it would grind to a halt.

The world has woken up to the dangers of relying on centralized infrastructure. The onus is now on the blockchain industry to capitalize on this crisis, not to score points, but to demonstrate that there’s a better way to build the web – one that will keep core services online all the time.

The case for decentralizing the web

The current web infrastructure depends heavily on a handful of providers like AWS, which control vast portions of cloud services, meaning that when vulnerabilities occur, the effects are cataclysmic. The AWS outage of October 20 disrupted services for millions, including major apps and businesses, revealing single points of failure.

The problem stemmed from a specific AWS misconfiguration — DNS issues in the company’s US-EAST-1 region, to be precise — but its effects were felt globally due to Amazon’s dominance of the cloud market. It’s understandable why enterprises should rely on AWS, given that most of the time its service is both reliable and scalable, but these very attributes are responsible for making its cloud service a liability — an accident waiting to happen.

With AWS holding over 30% of the global cloud market, this concentration amplifies risks during failures. This isn’t about what happens during 99.9% of the time when the cloud is working as expected — it’s about what happens the other 0.1% of the time, when edge cases are elevated into systemic shocks.