Coinbase CEO Steps Up After Prolonged Outage... Armstrong Announces "Follow-up Measures"

▲ Coinbase, Exchange/AI-generated image

Coinbase has begun preparing follow-up measures after a service outage that lasted for several hours. This outage affected trading, exchange access, and balance updates, and Coinbase CEO Brian Armstrong personally addressed the situation.

U.Today reported on the 9th that Coinbase recently experienced a service disruption for several hours, and CEO Armstrong mentioned the issue via X (formerly Twitter). The Coinbase monitoring team detected a cascading quote outage in internal services at 23:50 UTC on May 7, 2026. Customer impact was observed across spot trading, Prime, International, and derivatives exchanges.

Armstrong stated that this outage was "unacceptable." He identified the root cause as multiple cooling units failing in one part of an AWS data center, leading to overheating. Coinbase designed its services to withstand a single AWS availability zone outage, and most systems functioned as intended, but not all systems did so, he explained.

During this widespread AWS outage, Coinbase's centralized exchange did not operate as expected, resulting in service disruption. Armstrong explained that the exchange has a unique structure to reduce latency and optimize client co-location. While it is possible to design an exchange more resilient to AWS availability zone failures, doing so could introduce unwanted latency and affect the client co-location structure, he pointed out.

Armstrong stated that Coinbase will re-examine these trade-offs after this incident. He emphasized the need to review the relevant structures to provide the best trading environment for users and significantly reduce the duration of outages when an AWS availability zone switch is required.

In a separate post, Armstrong responded to an initial technical summary shared by Rob Witoff, Coinbase Head of Platform. He thanked the teams who worked overnight to resolve the issue and stated that Coinbase has already begun working on the next steps.

This outage blocked trading across retail, advanced, and institutional exchanges. Customers experienced delays in balance reflection during the outage, but this issue was automatically resolved once replication caught up. U.Today reported that there was no data loss due to this incident.

*Disclaimer: This article is for investment reference only, and we are not responsible for any investment losses based on it. The content should be interpreted for informational purposes only.*