Coinbase suffered a multi-hour trading disruption on Thursday after Amazon Web Services experienced failures across several availability zones in its US Eastern Region, located in Virginia. The supporting evidence appears in the cited X post.
The Nasdaq-listed crypto exchange said the incident temporarily prevented customers from transacting across both its web and mobile platforms.
The company confirmed service has since been fully restored, but the outage arrives at a difficult moment for Coinbase, which is simultaneously managing weaker-than-expected first-quarter results, a declining share price, and a workforce reduction of roughly 14%.
What Caused the Extended Disruption
Coinbase’s status page attributed the outage to thermal issues inside AWS infrastructure. “Coinbase experienced service disruptions due to increased temperatures in the affected AWS service,” the company wrote in an update posted during the incident.
Engineers traced the root cause to failures spanning multiple AWS availability zones, not a single isolated zone. That detail matters because Coinbase’s own infrastructure is designed to tolerate a single-zone failure. In an official statement posted to X by Coinbase Support, the company said: “Coinbase systems are designed to be resilient to a single zone outage. In this case, we observed failures impacting multiple AWS zones, which caused an extended outage of core trading services.”
As the situation developed, Coinbase briefly shifted markets into a “cancel only” mode, meaning customers could cancel existing orders but could not place new trades. Full trading functionality was later restored, and the company confirmed the primary issue was resolved in a follow-up post on Friday.
Coinbase added that its engineering team would conduct a full investigation into the incident and that details could change as AWS publishes its own official retrospective on the infrastructure failure.
That kind of dependency on a third-party cloud provider’s post-mortem timeline is itself part of the criticism being directed at the exchange.
Criticism Mounts Over Technical Resilience
The outage quickly attracted pointed commentary from within the technology industry. Gergely Orosz, a software engineer previously employed at Uber and Skype who counts more than 310,000 followers on X, framed the incident as a reputational problem for the exchange. Orosz wrote on Friday: “Unfortunate optics for Coinbase to have an hours-long outage when customers could not trade, a few days after their CEO said how non-technical teams are shipping code to production.”
That observation landed hard given the timing.
Coinbase CEO Brian Armstrong had recently made public remarks about expanding the scope of non-engineering staff contributing directly to production systems, a statement that raised eyebrows among developers and architects already skeptical of the company’s infrastructure priorities.
Coinbase is no stranger to criticism over platform availability. The exchange has faced repeated scrutiny during periods of intense market volatility, with a notable outage occurring in 2020 when bitcoin prices experienced a sharp intraday drop.
The pattern has fed a persistent narrative that Coinbase’s infrastructure has not always scaled proportionally with its user base and trading volumes.
What makes the May 2026 incident particularly sensitive is that it did not occur during a viral price surge or a record trading session. The outage happened against a backdrop of reduced activity, suggesting the platform’s cloud architecture carries risks even under comparatively normal load conditions.
Coinbase’s heavy reliance on AWS is itself a structural consideration that enterprise architects have long flagged as a single point of systemic risk for centralized exchanges.
Multi-cloud or hybrid infrastructure strategies are common among large financial platforms precisely to reduce this kind of exposure, and Thursday’s disruption will likely accelerate internal conversations about that architecture at Coinbase.
The exchange said its team will incorporate findings from AWS’s official retrospective once that document is published, signaling that the full picture of what caused the multi-zone thermal failure is not yet available.
Customers and analysts will be watching closely to determine whether Coinbase makes any concrete infrastructure commitments in response to the incident or whether it treats the event as an isolated third-party failure outside its direct control.
For users who were locked out of positions during a live market session, the distinction between a Coinbase fault and an AWS fault may matter less than the fact that trades could not be executed for an extended period.
In crypto markets, where prices can shift materially within minutes, hours of enforced inactivity carry real financial consequences regardless of where the technical blame is ultimately assigned.
Not Financial Advice: This article is for informational purposes only. Crypto investments are highly volatile. Always do your own research.
