<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Why Coinbase Could Not Simply Switch to a Backup During the AWS Outage]]></title><description><![CDATA[<p dir="auto"><img src="/forum/assets/uploads/files/1778403660879-819a5dae-52a2-4d27-a454-965ff43048c1-image.png" alt="819a5dae-52a2-4d27-a454-965ff43048c1-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">Coinbase has explained why an AWS data center problem in Northern Virginia produced a 12-hour trading outage rather than a brief disruption absorbed by backup infrastructure, and the technical detail is worth understanding for anyone who assumed that a company of Coinbase's scale would have instant failover capabilities. The exchange said its systems are specifically designed to withstand an outage in a single AWS Availability Zone and recover quickly when one occurs — which is the standard redundancy architecture for major cloud-dependent platforms. The problem on Thursday was that failures were observed across multiple AWS Availability Zones simultaneously, meaning more than one of the separate data center clusters within AWS's US-EAST-1 Northern Virginia region was affected at the same time. When multiple zones fail concurrently rather than a single zone failing in isolation, the redundancy architecture designed to route around a single failure point cannot fully compensate, and core services go down rather than seamlessly shifting to backup infrastructure.</p>
<p dir="auto">AWS attributed the incident to increased temperatures in the affected data center causing infrastructure impairment, which forced it to shift traffic away from the compromised Availability Zone. The physical cause — overheating data center equipment — represents a category of infrastructure failure that is qualitatively different from software bugs or network issues, as it can propagate across physically co-located equipment in ways that affect multiple redundancy zones before cooling or containment measures take effect. For Coinbase specifically, the failure mode revealed a gap between its stated resilience design — tolerant of single-zone failures — and the actual conditions of a multi-zone thermal incident. The exchange said it will publish a full post-incident analysis once its investigation and AWS's official retrospective are complete, which should provide more detail on whether architectural changes are planned to address the multi-zone failure scenario that its current design did not fully account for.</p>
]]></description><link>https://undeads.com/forum/topic/19760/why-coinbase-could-not-simply-switch-to-a-backup-during-the-aws-outage</link><generator>RSS for Node</generator><lastBuildDate>Tue, 09 Jun 2026 00:33:17 GMT</lastBuildDate><atom:link href="https://undeads.com/forum/topic/19760.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 10 May 2026 09:01:02 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Why Coinbase Could Not Simply Switch to a Backup During the AWS Outage on Sun, 10 May 2026 11:34:57 GMT]]></title><description><![CDATA[<p dir="auto">12-hour trading outage because a building got too warm, infrastructure fragility found a very mundane cause</p>
]]></description><link>https://undeads.com/forum/post/54948</link><guid isPermaLink="true">https://undeads.com/forum/post/54948</guid><dc:creator><![CDATA[madtrader]]></dc:creator><pubDate>Sun, 10 May 2026 11:34:57 GMT</pubDate></item><item><title><![CDATA[Reply to Why Coinbase Could Not Simply Switch to a Backup During the AWS Outage on Sun, 10 May 2026 11:34:40 GMT]]></title><description><![CDATA[<p dir="auto">AWS US-EAST-1 concentration creating single geographic failure risk for multiple major platforms simultaneously is systemic infrastructure concern</p>
]]></description><link>https://undeads.com/forum/post/54947</link><guid isPermaLink="true">https://undeads.com/forum/post/54947</guid><dc:creator><![CDATA[madtrader]]></dc:creator><pubDate>Sun, 10 May 2026 11:34:40 GMT</pubDate></item></channel></rss>