Coinbase suffered more than two hours of degraded performance Friday morning after an Amazon Web Services outage knocked trading and withdrawal functions offline for thousands of users worldwide. The disruption at one of the largest crypto exchanges by volume underscores how even the biggest platforms remain tethered to centralized cloud infrastructure.
What users saw Friday morning
Users began reporting issues around 9:30 a.m. UTC on May 8. The exchange's status page marked trading as "degraded" and withdrawals as "interrupted." For about two and a half hours, many couldn't place orders or move funds. The timing wasn't great — a Friday morning when retail traders often check positions ahead of the weekend.
The AWS link
Coinbase blamed an AWS outage for the problems. The cloud provider's services in one of its regions went down, taking the exchange's front-end and API with it. Coinbase runs much of its infrastructure on AWS, a common setup across crypto. When AWS stumbles, so do its tenants.
A familiar vulnerability
This isn't the first time a cloud failure has choked a major exchange. The structure is the problem: a single point of failure in a system that's supposed to be trustless. Coinbase's own engineers likely spent Friday rerouting traffic and spinning up backups. But for two hours, users who needed to trade or withdraw were stuck — a reminder that "decentralized" platforms often sit on very centralized foundations.
Coinbase hasn't published a post-mortem yet. The outage itself is over, but the questions it raises about infrastructure resilience aren't going anywhere.
