- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Coaching Changes
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Any word on the cause of the Amazon crash?
Posted on 10/20/25 at 2:49 pm
Posted on 10/20/25 at 2:49 pm
Millions are being lost.
Posted on 10/20/25 at 2:52 pm to Gaspergou202
As someone in the field, I can say that identifying the root-cause of the problem almost always comes after the mitigation. Especially in something as wide-reaching as this.
Posted on 10/20/25 at 2:54 pm to Gaspergou202
I wonder if it has anything to do with the streamer being sexually assaulted on camera at twitch con?
Posted on 10/20/25 at 2:54 pm to HurricaneTiger
Posted on 10/20/25 at 2:56 pm to Gaspergou202
Cause of the AWS Outage
Overview
Amazon Web Services (AWS) experienced a significant outage on October 20, 2025, primarily due to issues with its core database service, DynamoDB.
This disruption affected numerous websites and applications globally.
Technical Details
Root Cause: The outage stemmed from a problem with an internal subsystem responsible for monitoring the health of AWS's network load balancers.
Affected Services: The issues impacted multiple AWS services, including:
DynamoDB
EC2 (Elastic Compute Cloud)
SQS (Simple Queue Service)
Amazon Connect
Timeline of Events
Initial Report: AWS reported the outage at 3:11 AM ET, indicating operational issues in its US-East-1 region, located in Northern Virginia.
Mitigation Efforts: By 6:35 AM ET, AWS stated that the underlying DNS issue had been "fully mitigated," but connectivity problems persisted for some services.
Continued Issues: Despite initial recovery efforts, significant API errors and connectivity issues were still being reported throughout the morning.
Impact
The outage affected over 500 companies and millions of users, disrupting services for popular platforms like Snapchat, Coinbase, and Robinhood, highlighting the fragility of cloud-based infrastructures.
Overview
Amazon Web Services (AWS) experienced a significant outage on October 20, 2025, primarily due to issues with its core database service, DynamoDB.
This disruption affected numerous websites and applications globally.
Technical Details
Root Cause: The outage stemmed from a problem with an internal subsystem responsible for monitoring the health of AWS's network load balancers.
Affected Services: The issues impacted multiple AWS services, including:
DynamoDB
EC2 (Elastic Compute Cloud)
SQS (Simple Queue Service)
Amazon Connect
Timeline of Events
Initial Report: AWS reported the outage at 3:11 AM ET, indicating operational issues in its US-East-1 region, located in Northern Virginia.
Mitigation Efforts: By 6:35 AM ET, AWS stated that the underlying DNS issue had been "fully mitigated," but connectivity problems persisted for some services.
Continued Issues: Despite initial recovery efforts, significant API errors and connectivity issues were still being reported throughout the morning.
Impact
The outage affected over 500 companies and millions of users, disrupting services for popular platforms like Snapchat, Coinbase, and Robinhood, highlighting the fragility of cloud-based infrastructures.
Posted on 10/20/25 at 2:58 pm to Gaspergou202
maybe they should try rebooting?
Posted on 10/20/25 at 2:58 pm to Barstools
quote:
I wonder if it has anything to do with the streamer being sexually assaulted on camera at twitch con?
That’s a whole different thing, and twitch is quite the… something. When it rains, it pours.
Posted on 10/20/25 at 2:59 pm to hashtag
quote:
I'm 99% sure it will get blamed on "the network".
Well, Meta’s problems usually occur due to networking issues. Otherwise, the problems wouldn’t normally tear down their entire service catalog. Usually, it’s something to do with DNS or networking configurations that causes these things.
Posted on 10/20/25 at 3:01 pm to Stevo
quote:
maybe they should try rebooting
Is there anything more infuriating than having to call IT for some issue and having go through the mindless algorithm of rebooting?
Posted on 10/20/25 at 3:03 pm to Gaspergou202
quote:
DNS resolution of the DynamoDB API endpoint in US-EAST-1.
Posted on 10/20/25 at 3:07 pm to Gaspergou202
Patches was cold and climbed inside a rack of servers…


Posted on 10/20/25 at 3:09 pm to Gaspergou202
We do online highschool... our school day is at least 40% screwed. 
Posted on 10/20/25 at 3:28 pm to SallysHuman
quote:
We do online highschool... our school day is at least 40% screwed.
my freshman in college can't get into Canvas to do classes today.
Posted on 10/20/25 at 3:39 pm to 3nOut
quote:
my freshman in college can't get into Canvas to do classes today
Extra day of drinking. I'm sure they are heartbroken.
Posted on 10/20/25 at 3:46 pm to BigTigerJoe
quote:
Cause of the AWS Outage
Overview
Amazon Web Services (AWS) experienced a significant outage on October 20, 2025, primarily due to issues with its core database service, DynamoDB.
This disruption affected numerous websites and applications globally.
Technical Details
Root Cause: The outage stemmed from a problem with an internal subsystem responsible for monitoring the health of AWS's network load balancers.
Affected Services: The issues impacted multiple AWS services, including:
DynamoDB
EC2 (Elastic Compute Cloud)
SQS (Simple Queue Service)
Amazon Connect
Timeline of Events
Initial Report: AWS reported the outage at 3:11 AM ET, indicating operational issues in its US-East-1 region, located in Northern Virginia.
Mitigation Efforts: By 6:35 AM ET, AWS stated that the underlying DNS issue had been "fully mitigated," but connectivity problems persisted for some services.
Continued Issues: Despite initial recovery efforts, significant API errors and connectivity issues were still being reported throughout the morning.
Impact
The outage affected over 500 companies and millions of users, disrupting services for popular platforms like Snapchat, Coinbase, and Robinhood, highlighting the fragility of cloud-based infrastructures.
Breaking this down for the street level people, Amazon was likely the target of a cyber attack.
Posted on 10/20/25 at 4:11 pm to Bass Tiger
quote:
Breaking this down for the street level people, Amazon was likely the target of a cyber attack.

Posted on 10/20/25 at 4:14 pm to Gaspergou202
Let's figure that out after we triage and recover. This will be a thing for months after today.
Posted on 10/20/25 at 4:23 pm to SingleMalt1973
More proof the seventies bush is back.


Posted on 10/20/25 at 4:47 pm to 3nOut
quote:
can't get into Canvas to do classes today.
Yup, showed up to lecture… couldn’t access Canvas for the notes, let class out early, my majors rejoiced…I got home around 9ish, yard work and a day drunk. ‘Merica
Popular
Back to top
9














