An Amazon Web Services (AWS) data center outage in the US East region caused a four-hour disruption affecting multiple financial platforms, including FanDuel and Coinbase. The incident, which impacted EC2 instances and S3 storage, exposed vulnerabilities in cloud-dependent trading systems and raised concerns about infrastructure resilience.
Overview
The outage occurred on May 8, 2026, in AWS’s US East (Northern Virginia) region, one of the company’s largest and most widely used cloud zones. According to AWS’s status dashboard, the disruption began at approximately 10:14 AM ET and lasted until 2:18 PM ET. The root cause was traced to a failure within a cluster of EC2 compute instances, which in turn triggered cascading issues with S3 storage availability and latency.
Services relying on low-latency access to cloud infrastructure experienced significant degradation. FanDuel, a sports betting platform, reported delays in odds updates and bet settlement during peak trading hours. Coinbase, a major cryptocurrency exchange, confirmed intermittent API failures and delayed transaction confirmations, affecting high-frequency trading operations.
What it does
The affected AWS components—EC2 and S3—are foundational to most cloud-hosted applications:
- EC2 (Elastic Compute Cloud): Provides scalable virtual servers for running applications. The outage impacted a subset of instances, leading to failed launches, unexpected terminations, and elevated error rates.
- S3 (Simple Storage Service): Offers object storage with high durability. During the incident, S3 experienced increased error rates and latency spikes, particularly for cross-region replication and retrieval operations.
The combined failure disrupted backend systems that depend on rapid data access and compute availability, especially those with tight latency requirements such as financial trading platforms.
Tradeoffs
The incident highlights systemic tradeoffs in cloud architecture:
- Centralization risk: The US East region hosts a disproportionate share of critical infrastructure, making it a single point of failure for many services.
- Dependency chains: Even services not directly hosted on AWS can be affected if they rely on third-party tools or APIs that are.
- Recovery limitations: While AWS offers tools for multi-region failover, not all customers implement them due to cost, complexity, or performance constraints.
Neither FanDuel nor Coinbase reported data loss, but both acknowledged service degradation during the window. AWS stated that no physical damage occurred and that the issue was resolved through internal recovery procedures.
When to use it
This event underscores the importance of:
- Designing for region failure: Implementing active-passive or active-active architectures across multiple AWS regions.
- Testing disaster recovery plans: Regular failover drills can expose gaps in redundancy setups.
- Monitoring third-party dependencies: Organizations should assess the cloud footprint of their vendors and partners.
AWS has not announced changes to its service-level agreements or compensation for affected customers.
Bottom line: Cloud infrastructure remains critical to financial operations, but reliance on a single provider or region introduces measurable risk. Proactive redundancy planning is no longer optional for latency-sensitive applications.