TLDR
A major outage at Coinbase temporarily halted crypto trading for several hours after an Amazon Web Services (AWS) failure took parts of the exchange offline.
- Coinbase experienced a service outage lasting over two hours, with trading halted or severely degraded as systems were put into Cancel Only mode.
- The root cause was overheating and multi-zone failures in an AWS US-East data center, exposing how dependent big exchanges are on centralized cloud providers.
- Coinbase has now restored trading and promised an infrastructure review, while the incident highlights practical risk controls users can apply around venue concentration.
Deep Dive
1. What Happened And For How Long
Multiple reports describe Coinbase suffering a service outage lasting over two hours, during which many users could not place trades and others saw heavy delays or failed orders.
To contain the disruption, Coinbase shifted all markets into Cancel Only mode, allowing cancellation of open orders but no new trades until systems stabilized. Coinbase repeatedly stated that customer funds remained safe throughout.
For several hours, Coinbase users effectively lost the ability to open or adjust positions in fast-moving markets, even though custody was not compromised.
2. Why AWS Caused An Exchange Outage
The incident was traced to a thermal issue in AWSs US-EAST-1 region in Northern Virginia, where overheating and power problems impaired EC2 instances and storage serving Coinbase.
Coinbase later said that failures spread across multiple AWS zones, exceeding its design for a single-zone outage and leading to extended downtime of core trading services, as described in its explanation of multi-zone AWS failures.
Even a top-tier exchange can be taken offline when its matching engine and critical systems sit on a single cloud provider that suffers a regional incident.
3. What To Watch And How Users Can Respond
Coinbase has restored full trading and signaled a review of its architecture, including whether to trade some ultra-low-latency optimizations for better resilience and faster failover.
For users, the outage underlines three practical habits: 1) avoid relying on a single exchange for all liquidity, 2) keep long-term holdings in self-custody, and 3) monitor official status pages during volatility.
Exchange outages are an operational risk; spreading venue exposure and separating trading capital from long-term holdings can reduce the impact when a centralized platform goes dark.
Conclusion
A cloud-induced failure at AWS cascaded into a multi-hour halt of trading on Coinbase, demonstrating that crypto markets still depend on centralized infrastructure at critical choke points. While funds remained safe and trading resumed, the episode is a reminder that resilience is as important as liquidity when choosing where to trade and how to structure your overall setup.
CoinsKid.Com