NEWS REPORT

AI Mode
All
Images
Videos
News
More

amazon a w s outage update
6 hours ago

There isn't a major, widespread AWS outage right now (Dec 13, 2025), but reports point to a significant incident in October 2025 where issues in the US-EAST-1 region (like DynamoDB failures) caused global disruptions, impacting services from Reddit and Snapchat to financial platforms, with AWS confirming the cause was related to network load balancers and internal systems, leading to a post-event summary on WIRED and Reuters. For current status, always check the AWS Health Dashboard. 
Key Details of the Recent Major Outage (October 2025):
Cause: Failures in DynamoDB and internal network monitoring systems in the US-EAST-1 region.
Impact: Widespread, affecting major sites, apps (Reddit, Snapchat), and even flight systems.
Resolution: AWS worked to restore services, narrowing down the cause and applying fixes over several hours.
Root Cause Analysis: A post-event summary explained it was due to issues with the network load balancer monitoring subsystem. 
How to Check for Current AWS Outages:
Official Source: Visit the AWS Health Dashboard (health.aws.amazon.com) for real-time updates on service status.
Community Reports: Use sites like Downdetector to see user-reported issues. 

undefined
undefined
undefined
9 sites
Amazon AWS outage today? Is Reddit, Snapchat down? Flight ...
Issues were first reported early Tuesday morning, with thousands of reports logged throughout the morning. * Amazon Web Services (

IndyStar

Amazon Explains How Its AWS Outage Took Down the Web - WIRED
AWS confirmed in a “post-event summary” on Thursday that its major outage on Monday was caused by Domain System Registry failures ...

WIRED

AWS outage hits major apps and services, resurfacing old questions ...
Update: As of 6 a.m., Amazon reported it was making progress on the remaining issues with EC2. The company said new instance launc...

GeekWire

Show all

share
this

Amazon’s outage that affected thousands of companies and millions of people was caused by two automated systems updating the same data simultaneously, leading to a DNS (Domain Name System) issue that brought down AWS’ DynamoDB database.

Cyber risk analytics firm CyberCube just released a preliminary insured loss estimate for AWS’ outage, projecting a loss of up to $581 million.

“We apologize for the impact this event caused our customers,” said AWS in its post-mortem report of the outage results and root cause.

[Related: AWS’ 15-Hour Outage: 5 Big AI, DNS, EC2 And Data Center Keys To Know]

“We know this event impacted many customers in significant ways,” AWS said. “We will do everything we can to learn from this event and use it to improve our availability even further.”

CRN breaks down the five biggest things to know about AWS outage that every Amazon customer, partner and user needs to know.

No. 1: CyberCube Estimates Up To $581 Million In Losses

CyberCube has released a preliminary insured loss estimate for the AWS outage, projecting a range of between $38 million and $581 million.

Cybersecurity risk analytics provider CyberCube said the outage impacted more than 2,000 large organizations and around 70,000 organizations overall.

AWS is expected to reimburse affected companies for downtime, which may limit insured losses and discourage litigation, according to the security analytics firm.

CyberCube said many customers might choose not to file claims, which is a factor contributing to its lower-end loss projection, because the outage lasted less than a day. The company expects the outage to have a low to moderate impact on cyber insurers, with the majority of losses likely to be in the lower end of CyberCube’s range.

Read through for the four other big things to know about AWS’ outage, including the root cause and changes AWS plans to make.