It took just one disruption at an Amazon Web Services (AWS) data centre in Tokyo to trigger disarray across some of the world’s biggest crypto exchanges. Withdrawals stalled. Charts glitched.
Order cancellations failed. And yet again, the cryptocurrency space was forced to reckon with the risks of depending too heavily on a single cloud provider.
At around 9:15am (8:15am GMT) on Tuesday, AWS reported a connectivity issue that affected at least a dozen of its services. The incident, which lasted for less than 40 minutes, impacted centralised exchanges that rely on AWS to power their operations.
Binance was the first to sound the alarm. For 23 minutes, users couldn’t withdraw their assets. The platform posted a brief message on X (formerly Twitter): “To keep safe, we’ve temporarily suspended withdrawals.” Barely ten minutes later, they were back online. But the damage had already begun.
KuCoin followed. “Due to a large-scale network outage with AWS services, our platform is currently experiencing temporary disruptions,” the exchange announced on X. Their spokesperson confirmed the outage hit Tokyo’s data centre directly.
“Some services have already been restored, and our team is working closely with AWS to recover full functionality as quickly as possible. No user assets or data have been affected.”
MEXC also felt the heat. Users were left staring at abnormal candlestick charts, failed order cancellations and delays in asset transfers. “We want to assure you that your assets on MEXC remain fully secure. For any losses incurred as a result of this platform-related issue, we will prepare a compensation plan to appropriately reimburse affected users,” the exchange stated publicly.
Coinstore, Gate.io, DeBank, Rabby Wallet, Weex—one by one, platforms reported similar issues. By mid-morning, more than eight exchanges had acknowledged problems linked to the AWS outage.
For anyone watching closely, this wasn’t just a technical hiccup. It was a warning siren.
AWS, known for providing fast, scalable infrastructure, has become the spine of the crypto economy. From Binance to Coinbase, Crypto.com to Kraken, most big-name exchanges run on its cloud. When that spine snaps—even momentarily—the entire ecosystem wobbles.
“The issue has been resolved and the service is operating normally,” said an AWS spokesperson after full service was restored. But not everyone is ready to move on.
Gracy Chen, CEO of Bitget exchange, said: “AWS data centre issues impacted several CEXs — no need to panic. It’s a solid reminder: Maybe it’s time to explore decentralised cloud services.”
It’s not the first time this conversation has come up. Centralised infrastructure in crypto—ironically—is a contradiction that continues to haunt the industry. It’s efficient. It’s scalable. But it’s also brittle. One crack in the system, and everything unravels.
Edmund Chua, head of mETH Protocol, didn’t hold back: “AWS down and 90% of crypto is down. Decentralisation is a meme.”
There are already decentralised alternatives out there: Filecoin for storage, Akash Network for computing, Render Network for graphics processing. But adoption has been slow, and trust in cloud giants like AWS remains the norm—until moments like this remind everyone why that might be dangerous.
In the end, yes—assets were safe. Services came back online. But as I watched events in real time, it became clear that fixing a technical error wasn’t the only issue. The need to confront a deeper problem is a must.
Crypto was built on the idea of freedom from central control. Yet here we are, watching entire exchanges freeze because one cloud provider faltered.
