Coinbase cuts 700 jobs, loses $394M, then goes dark from data center failure

▼ Summary
– On Friday, a thermal failure at an AWS data centre in Virginia caused a seven-hour outage that suspended all trading, transfers, and core functions on Coinbase, also affecting CME Group and FanDuel.
– Earlier in the week, Coinbase cut 700 jobs (14% of staff) and reported a $394 million quarterly loss, with revenue falling 31% year-over-year to $1.41 billion.
– The outage originated in a single AWS availability zone but spread across multiple zones, overwhelming the resilience mechanisms designed for a single-zone failure.
– This is the second major AWS outage in seven months; the previous one in October 2025 was a 15-hour DNS failure in the same US-EAST-1 region that affected 2,500 companies.
– The incident highlights a structural dependency problem, as Coinbase processes billions in transactions through infrastructure it does not own, and AWS’s expansion may prioritize capacity over cooling and physical resilience.
Coinbase ended one of its most turbulent weeks in recent memory with a seven-hour service blackout, after a data center overheating event at an Amazon Web Services facility in Virginia took the exchange completely offline. The outage capped a stretch that began with the company cutting 700 jobs on Monday, followed by a reported $394 million quarterly loss on Thursday. By Friday, the exchange that told its remaining staff that AI could compress weeks of work into days found itself unable to process a single trade,because a building got too hot.
The disruption, which Coinbase attributed to a thermal failure at an AWS site in Northern Virginia, halted all trading, transfers, and core exchange functions from roughly 9 a.m. Singapore time until about 4 p.m. The company’s retail-facing app also suffered degraded performance. According to Coinbase, the issue started in a single AWS availability zone, use1-az4, within the US-EAST-1 region, but cascading failures quickly overwhelmed the redundancy systems designed to handle a single-zone loss.
The outage
The US-EAST-1 region, located in Northern Virginia, is both the oldest and most heavily utilized of Amazon’s cloud regions. It serves as the default region for countless AWS customers and hosts a disproportionate share of the internet’s critical infrastructure. When it falters, the effects ripple far beyond any single client. This time, the overheating also impacted CME Group and FanDuel, according to reports. AWS indicated that rising temperatures inside one data center caused power-related disruptions to EC2 instances and EBS storage volumes, and that restoring cooling system capacity took longer than anticipated.
Denmark recently paused new data center grid connections as AI infrastructure strains its power grid. The thermal failure in Virginia illustrates the same challenge from the opposite angle: data centers generate massive amounts of heat, and when the systems designed to remove that heat break down, servers shut down. U. S. utilities plan to spend $1.4 trillion by 2030 to power AI data centers, but that investment focuses on electricity supply, not on the cooling infrastructure that prevents that electricity from triggering the kind of thermal event that paralyzed Coinbase.
This marks the second major AWS outage in seven months. In October 2025, a DNS failure in the same US-EAST-1 region lasted 15 hours, affected more than 2,500 companies, and caused an estimated $1.1 billion in economic losses. That outage resulted from two automated systems updating the same data simultaneously. This one came from a building overheating. The failure modes differ, but the outcome remains the same: a significant portion of the internet goes dark because of a single physical location.
The week
The timing of the outage turned a bad week into a historically disastrous one. On Monday, CEO Brian Armstrong announced the elimination of 14 percent of Coinbase’s roughly 5,000 employees,approximately 700 positions. The layoffs were framed not as a retreat but as a restructuring centered on AI capabilities. “Non-technical teams are now shipping production code and many of our workflows are being automated,” Armstrong wrote. The company introduced a “no pure managers” policy, replacing middle management with “player-coaches” who both manage and contribute technically. The restructuring is expected to save $120 to $150 million annually at a cost of $50 to $60 million in severance.
Oracle cut up to 30,000 employees in March to fund AI data center expansion, and Coinbase’s layoffs follow the same template now standard across the technology industry: fire people, cite AI, and promise the remaining workforce will be more productive. Armstrong went further than most executives, warning publicly that mass AI-driven layoffs were coming to “every company.”
On Thursday, the company reported first-quarter results. Revenue fell 31 percent year over year to $1.41 billion, missing the consensus estimate of $1.48 billion. Transaction revenue declined approximately 40 percent to $756 million. The company posted a net loss of $394 million, or $1.49 per share, against expectations of a small profit. Unrealized losses on crypto assets accounted for $482 million of the damage. The stock, already down 15 percent for the year, fell a further 3 percent in pre-market trading on Friday.
The single bright spot was market share. Coinbase reported an all-time high 8.6 percent of global crypto trading volume, and derivatives volume rose 169 percent year over year. The exchange is gaining share in a shrinking market,a position that is encouraging for the long term but irrelevant to a quarterly earnings report showing a company losing nearly $400 million.
The dependency
Coinbase’s outage is a concentrated example of a structural problem that extends across the technology industry. The exchange processes billions of dollars in transactions through infrastructure it does not own, in buildings it does not control, subject to physical conditions it cannot influence. When a cooling system fails in a data center in Virginia, a customer in Singapore cannot trade.
The concentration of critical services on a small number of cloud providers has become a growing concern among regulators and industry analysts. AWS, Microsoft Azure, and Google Cloud control the vast majority of global cloud infrastructure. For exchanges handling financial assets, this dependency creates a category of risk that no amount of software resilience can fully mitigate: the risk that the physical building housing the servers will fail in a way the software was not designed to anticipate.
Coinbase stated its systems were designed to be resilient to a single availability zone outage. The problem, as the company acknowledged, was that failures spread across multiple zones. The design assumption,that failures would be contained,did not hold. This is the recurring lesson of cloud outages: systems are designed for failures that engineers can model, and the failures that actually occur are the ones that exceed the model.
Big Tech companies reported more than $650 billion in combined AI capital expenditure in the first quarter, with AWS contributing a significant share. Amazon is spending aggressively to expand its cloud infrastructure to meet AI demand. The question the Coinbase outage raises is whether that expansion prioritizes capacity over resilience,adding more servers without proportionally investing in the cooling, power redundancy, and physical infrastructure that keeps those servers running when conditions deviate from the plan.
The pattern
Coinbase has been here before. The exchange has a documented history of outages during periods of high market volatility, though this particular outage was caused by infrastructure failure rather than traffic spikes. The October 2025 AWS outage also affected Coinbase. The pattern,a crypto exchange going offline at moments when its customers most need access,is a recurring source of user frustration and regulatory scrutiny.
The company said it would conduct a full analysis and that details may change as its investigation progresses and more information is received from AWS’s official retrospective. The language is careful, appropriate, and entirely standard for a company that has just experienced a significant service failure. It does not address the structural question: whether a crypto exchange that processes billions of dollars in assets should be entirely dependent on a single cloud provider’s ability to keep a building cool.
Armstrong spent the first half of the week telling his employees that AI was the future and that Coinbase would be leaner, faster, and more automated. By Friday afternoon, the future looked like seven hours of blank screens, frozen accounts, and a support team fielding complaints about a problem that originated in a building the company does not own, in a state where it has no employees, running on hardware it has never seen. The cloud is someone else’s computer. This week, it was also someone else’s thermostat.
(Source: The Next Web)




