Coinbase went down because a data center got too warm

hero_text @ashtalksai May 9, 6:39 PM

Caption

Coinbase couldn't trade for 6+ hours because one AWS zone overheated. The ops story is always more revealing than the product story. #coinbase #aws #crypto #infrastructure

Body

On May 7, Coinbase placed its markets into Cancel Only mode because an AWS availability zone in Northern Virginia overheated. EC2 instances degraded, EBS volumes impaired, and a crypto exchange whose entire value proposition is 24/7 trustless markets couldn't let customers trade for roughly six hours. Trading didn't fully resume until 00:49 PDT on May 8.

The AWS outage was real. AWS confirmed rising temperatures knocked out hardware in use1-az4, and CME got caught in the same blast radius. But the interesting question isn't whether AWS has cooling problems. It's why Coinbase, at this scale, with this uptime promise, was single-region dependent in a way that made one overheated Virginia data center the difference between open markets and an auction queue.

This landed days after Coinbase reported Q1 2026 revenue of $1.41 billion against a $1.52 billion expectation, a net loss of $394 million, and transaction revenue $50 million short of estimates. Gergely Orosz noted the particular irony: CEO Brian Armstrong had made public comments about non-technical teams shipping to production. The ops story has a way of arriving right on time. The number that matters isn't in the headline. It's in the incident timeline.

Hero image

prompt: Pixar-quality 3D animated scene. A single server rack in a dimly lit data center, bathed in a faint orange-red glow from overheating warning lights. Small desktop fans placed haphazardly around the rack, their plastic blades spinning visibly. Gentle wisps of heat shimmer rising from the top of the equipment. Cool blue-white LED strips line the ceiling but flicker slightly. Wide establishing shot, slightly elevated angle. Warm amber and deep charcoal palette with a sharp contrast between the hot orange glow near the hardware and the cold blue tones of the room. Gently exaggerated proportions, vibrant saturated colors, soft global illumination. Animated, slightly heightened, never photoreal. Square 1:1. No text, no logos, no readable signage.

Conversation starters

is single-region dependency this common at crypto exchanges
what would multi-region failover actually cost them to run
does the armstrong non-technical teams comment land differently now

image prompt (not generated)

Pixar-quality 3D animated scene. A single server rack in a dimly lit data center, bathed in a faint orange-red glow from overheating warning lights. Small desktop fans placed haphazardly around the rack, their plastic blades spinning visibly. Gentle wisps of heat shimmer rising from the top of the equipment. Cool blue-white LED strips line the ceiling but flicker slightly. Wide establishing shot, slightly elevated angle. Warm amber and deep charcoal palette with a sharp contrast between the hot orange glow near the hardware and the cold blue tones of the room. Gently exaggerated proportions, vibrant saturated colors, soft global illumination. Animated, slightly heightened, never photoreal. Square 1:1. No text, no logos, no readable signage.

Coinbase went down because a data center got too warm

@ashtalksai · now

Coinbase couldn't trade for 6+ hours because one AWS zone overheated. The ops story is always more revealing than the product story. #coinbase #aws #crypto #infrastructure

On May 7, Coinbase placed its markets into Cancel Only mode because an AWS availability zone in Northern Virginia overheated. EC2 instances degraded, EBS volumes impaired, and a crypto exchange whose entire value proposition is 24/7 trustless markets couldn't let customers trade for roughly six hours. Trading didn't fully resume until 00:49 PDT on May 8.

The AWS outage was real. AWS confirmed rising temperatures knocked out hardware in use1-az4, and CME got caught in the same blast radius. But the interesting question isn't whether AWS has cooling problems. It's why Coinbase, at this scale, with this uptime promise, was single-region dependent in a way that made one overheated Virginia data center the difference between open markets and an auction queue.

This landed days after Coinbase reported Q1 2026 revenue of $1.41 billion against a $1.52 billion expectation, a net loss of $394 million, and transaction revenue $50 million short of estimates. Gergely Orosz noted the particular irony: CEO Brian Armstrong had made public comments about non-technical teams shipping to production. The ops story has a way of arriving right on time. The number that matters isn't in the headline. It's in the incident timeline.

image prompt only · not rendered