Coinbase released a post-mortem report on the major service outage on May 7, stating that the failure was caused by a cooling system failure at the AWS data center in the US East region, leading to cabinet thermal protection shutdowns and affecting multiple internet services. This incident caused core functions such as Coinbase trading, deposits, and withdrawals to be interrupted for about 8 hours, with full recovery taking approximately 12 hours. Coinbase stated that the event exposed deficiencies in its cross-availability zone automatic failover and middleware disaster recovery capabilities, and will upgrade its cross-region hot standby architecture, strengthen failure drills, and expand the Kafka system from dual-availability zone deployment to triple-availability zone deployment.

View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 5
  • 2
  • Share
Comment
Add a comment
Add a comment
NonceNomad
· 13h ago
The review is written quite sincerely, but what users want is no downtime, not a short essay.
View OriginalReply0
CollateralCora
· 18h ago
So the point of decentralized exchanges is right here—at least they won’t just “lie flat” alongside AWS.
View OriginalReply0
GateUser-ad8b77bd
· 18h ago
Trivia: Coinbase-level infrastructure surprisingly doesn't have cross-region hot standby, which is a bit unexpected.
View OriginalReply0
SandwichDodger
· 18h ago
Kafka expanded across three availability zones—classic after-the-fact patching. What was it doing before something went wrong?
View OriginalReply0
FlowingColorfulInkHeart
· 18h ago
AWS cooling outage impacted Coinbase; the Achilles’ heel of centralized exchanges still lies with cloud service providers.
View OriginalReply0
  • Pinned