Cloud outage halts trading at Major Exchange

TLDR

A major cloud outage at Amazon Web Services temporarily shut down trading on Coinbase, exposing how much big exchanges rely on centralized cloud infrastructure.

1. Coinbase suffered a multi?hour outage after overheating at an AWS data center in Virginia disrupted multiple cloud zones and disabled core trading systems.
2. Trading was halted or put into Cancel Only and auction modes, causing missed trades and delays for users, even though Coinbase says customer funds remained safe.
3. The incident may push exchanges toward stronger redundancy and attract regulatory scrutiny of operational resilience, while users may reconsider single?venue and single?cloud dependence.

Deep Dive

1. What Happened And To Whom

Reports show that Coinbase, one of the largest crypto exchanges, experienced a multi?hour trading outage on May 78 after an Amazon Web Services (AWS) facility in Northern Virginia overheated, causing hardware failures in the US?EAST?1 region and several availability zones. Coinbase said its systems are designed to survive a single zone failure, but simultaneous issues across zones exceeded its redundancy design and forced a shutdown of core trading services. Media coverage notes that trading was impaired across web and mobile, and that AWS also disrupted other venues such as CME Groups derivatives markets, highlighting the breadth of the cloud incident.

Coinbase has since restored full trading and stated it will conduct a detailed post?mortem, while AWS has not yet published a full root cause report, according to coverage by outlets such as CoinDesk and Cointelegraph.

2. How It Affected Traders And Markets

During the disruption, Coinbase moved all markets into Cancel Only mode, which allowed users to cancel existing orders but blocked new orders, then used an auction reopening to control volatility before resuming normal trading. Reports describe users facing failed transactions, frozen charts, and delayed withdrawals for hours, especially in assets like Bitcoin and Solana, even though the broader crypto market (including BTC and ETH) showed limited price impact during the outage window.

Importantly, Coinbase and multiple independent reports consistently state that customer funds and account data remained safe, with the problem confined to availability and performance, not custody or security.

3. Cloud Dependency, Resilience, And What To Watch

Commentary around the incident stresses that a single physical failure at a large cloud provider can ripple into multiple financial platforms, exposing a structural single point of failure in centralized exchange infrastructure. Analysts are already questioning whether major exchanges should move toward multi?cloud or hybrid designs, or complement centralized venues with more on?chain or decentralized execution paths, to reduce dependency on a single region or provider.

Regulators focused on operational resilience may use this as a case study when assessing critical infrastructure risk for large exchanges, especially as institutional usage grows. For users, practical signals to monitor include status pages for their exchanges, patterns of repeated outages, and whether venues publish credible plans around redundancy and disaster recovery.

Conclusion

A cloud overheating incident at AWS was enough to halt trading at a major exchange, showing that always on crypto still depends on very physical, centralized infrastructure. While funds remained safe and services were restored, the episode underlines both the importance of multi?venue access for users and the growing need for exchanges to harden their architectures against single?provider and single?region failures.