Gracy Chen, CEO at Bitget Global, said AWS data centre issues had an impact on several centralised exchanges—but there’s no need for alarm. She described the incident as a useful reminder that it might be worth exploring decentralised cloud options.
Dominic Williams chimed in with strong agreement. He pointed out that today only one blockchain can run online apps and services end-to-end, fully on-chain, with even AI capable of acting as a smart contract and building. That platform is ICP.
Their discussion highlights a growing concern within the crypto industry: reliance on centralised cloud providers may leave exchanges and services vulnerable to outages or disruptions. By contrast, decentralised infrastructure, like that offered by ICP, could offer improved resilience.
It’s an issue that resonates beyond the crypto world. When major cloud services falter, businesses across sectors experience ripple effects. The question now is whether crypto platforms see this event as a warning or simply as a temporary hiccup.
Chen’s tone was calmly reassuring. She stopped short of calling for an immediate overhaul. Instead, she framed the situation as a chance to consider long-term strategies for infrastructure diversity. Williams, meanwhile, seized the moment to broaden the conversation. By stressing ICP’s capability to support fully on-chain applications—from social tools to enterprise systems—and even enabling AI to function within smart contracts, he offered a vision of a new infrastructure paradigm.
The balance here is crucial. It wouldn’t be fair to dismiss centralised models outright; they remain reliable, efficient, and widely used. But as the AWS incident showed, a single point of failure can affect many operators. Decentralised alternatives may address these concerns, yet they often carry their own challenges—such as complexity, cost, or varying levels of adoption.
As the crypto sector continues to evolve, the industry may well head toward a hybrid approach: centralised systems for day-to-day efficiency, paired with decentralised options as backup or for critical functions. For now, the Bitget and ICP executives appear to agree on one thing: this AWS outage serves as a timely prompt to reassess infrastructure dependence.
In the end, the industry faces a choice. Stick with familiar, established systems—or explore emerging models that promise greater resilience. For firms considering that choice, this latest episode offers food for thought.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
🪙 BTC Wallet: bc1pp5kuez9r2atdmrp4jmu6fxersny4uhnaxyrxau4dg7365je8sy2q9zff6p
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion