Table of content
This updated analysis is based on StatusGator outage data collected from January 1 to December 9, 2025. We decided to review our AWS analysis of outages in 2022 due to several new AWS incidents, especially another widely discussed AWS outage in us-east-1 (N. Virginia) that occurred on October 20, 2025.
We’ve expanded the report with fresh 2025 regional data as well as a new breakdown of affected AWS services.
StatusGator continuously monitors the official AWS status pages and aggregates incidents across every public AWS Region. This analysis reflects:
So let’s take a look at the number of outages, duration, and components affected.
| Region | Number of outages | Duration | Components Affected |
|---|---|---|---|
| Regionless | 12 | 31:55:19 | 14 |
| Canada-Central | 1 | 3:49:57 | 19 |
| Hyderabad | 1 | 0:44:59 | 46 |
| Ireland | 1 | 0:44:51 | 10 |
| N. Virginia | 10 | 33:49:33 | 126 |
| Ohio | 2 | 1:20:45 | 2 |
| Oregon | 3 | 2:59:41 | 3 |
| Osaka | 1 | 2:15:01 | 11 |
| Sao Paulo | 1 | 0:44:51 | 9 |
| Singapore | 1 | 0:54:59 | 1 |
| Stockholm | 2 | 11:54:49 | 81 |
| Sydney | 1 | 0:50:00 | 1 |
| Tokyo | 3 | 1:24:51 | 18 |
| Zurich | 1 | 4:54:55 | 7 |
N. Virginia (us-east-1) is once again the least reliable AWS Region.
It leads the dataset in:
No other region even comes close. Stockholm ranks second in downtime (11+ hours). Despite only 2 outages, each incident had a massive regional impact.
Regionless outages were unusually high. This category recorded 12 outages and 32 hours of downtime, indicating:
AWS doesn’t just experience regional outages. Service-level incidents are just as impactful.
We analyzed the most frequently disrupted AWS services in 2025, ranked by the number of outages.
| Service | Number of Outages | Duration |
|---|---|---|
| Amazon EC2 | 14 | 19:14:01 |
| Amazon SageMaker | 11 | 20:40:21 |
| AWS Glue | 10 | 15:51:40 |
| Amazon EMR | 10 | 21:39:31 |
| Amazon ECS | 10 | 19:54:32 |
These services didn’t always have the highest count, but had the longest or most severe incidents.
| Service | Number of Outages | Duration |
|---|---|---|
| Amazon OpenSearch Service | 6 | 25:36:36 |
| Amazon EMR Serverless | 7 | 25:30:08 |
| Amazon CloudWatch | 6 | 24:58:49 |
| Amazon Connect | 5 | 22:52:42 |
| AWS STS | 5 | 22:48:39 |
| Amazon VPC Lattice | 7 | 22:35:47 |
| Amazon EMR | 10 | 21:39:31 |
| Amazon EventBridge | 5 | 21:24:32 |
| Amazon Kinesis Data Streams | 5 | 21:15:00 |
| AWS DataSync | 9 | 20:36:52 |
| Amazon Elastic Load Balancing | 9 | 12:34:20 |
| Amazon DynamoDB | 9 | 13:19:18 |
| AWS Transit Gateway | 8 | 17:14:51 |
| AWS Lambda | 8 | 13:50:15 |
Across Tables 1–3 above, we see a consistent pattern emerge:
1. Many of the affected components were concentrated in N. Virginia
With 126 components affected, us-east-1 experienced the widest service disruption footprint.
2. Region-level outages and service-level outages are correlated
Major incidents involving:
…almost always touch N. Virginia due to:
3. The longest-running outages disproportionately affected us-east-1
Duration-heavy outages (CloudWatch, OpenSearch, EMR Serverless) frequently included N. Virginia, driving up the region’s total downtime.
Conclusion:
N. Virginia is not only the region with the most outages, but it is also the region where service outages cascade the widest and run the longest.
On October 20, 2025, AWS experienced one of the most significant cloud outages in its history. 76 individual AWS components in the N. Virginia region alone showed disruption, by far the most heavily affected region.
Portions of Amazon Web Services were down for nearly 15 hours, causing cascading failures across thousands of SaaS platforms.
StatusGator’s Early Warning Signals detected the incident approximately ten minutes before AWS officially acknowledged it, ultimately identifying outages across more than 2,000 of the 6,000 services in our monitoring network.
However, the magnitude of the event meant StatusGator was also impacted, experiencing two periods of dashboard and status page downtime due to a surge in global traffic and failures in upstream infrastructure.
Despite these disruptions, StatusGator delivered over 100,000 outage notifications throughout the incident and has since implemented architectural improvements to strengthen reliability during future large-scale cloud failures.
We revisited the three common theories from our 2023 AWS outage analysis and compared them against this year’s dataset.
In 2023, we found this explanation to be weak. But the 2025 “Components Affected” numbers tell a new story:
This indicates:
Still, high service count alone doesn’t explain the full scale:
Regions like Oregon and Ireland offer nearly as many services but have far fewer issues.
So the number of components contributes to complexity, but not the root cause.
This remains the strongest and most likely explanation. StatusGator monitoring AWS status data historically shows:
More customers → heavier load → more real-world stress → more outages that reach public visibility.
So this assumption is very likely true, and reinforced by 2025 data.
AWS provides no evidence that us-east-1 uses a fundamentally different architecture. And our 2025 numbers don’t suggest “old region issues”:
Like in 2023, we still see no evidence supporting this theory.
With only weeks left in 2025, the data is clear:
EC2, SageMaker, Glue, EMR, and ECS led the list.
OpenSearch, CloudWatch, EMR Serverless, and STS had over 24 hours of cumulative downtime.
The Regionless category shows a notable rise in cross-region or global incidents in 2025.
StatusGator aggregates every AWS service and region into a single unified dashboard.
We alert you instantly, often before AWS posts the incident publicly.
Get instant, account-specific AWS outage alerts through StatusGator’s unified dashboard, now enhanced with AWS Health integration for Enterprise customers. It delivers trusted, direct notifications about incidents, outages, and maintenance affecting your services, with built-in filtering to reduce noise, and seamless delivery to Slack, Microsoft Teams, Discord, Google Chat, and more.
Monitor AWS outages in real time with StatusGator — free to try.