Monday, October 20th 2025
AWS Outage Takes Half of the Internet Down, Services Now Recovering
Amazon Web Services (AWS) outage has just taken down half of the known internet. However, services are now recovering. Just as Monday started on the Pacific Daylight Time (PDT), AWS reported incidents of multiple AWS services being down, with a simple confirmation that "We are investigating increased error rates and latencies for multiple AWS services in the US-EAST-1 Region." Online services like Amazon.com, Alexa, ChatGPT, Epic Games Store, Epic Online Services, social media like Snapchat, and games like Fortnite, have been down since.
A few hours later, AWS confirmed that it had isolated the issue. "We have identified a potential root cause for error rates affecting the DynamoDB APIs in the US-EAST-1 Region," they stated, adding, "This issue also impacts other AWS services in the US-EAST-1 Region. Global services or features that rely on US-EAST-1 endpoints, such as IAM updates and DynamoDB Global tables, may also be experiencing issues. During this time, customers may be unable to create or update Support Cases. We recommend customers continue to retry any failed requests." Subsequently, AWS confirmed that the "underlying DNS issue has been fully mitigated, and most AWS service operations are now succeeding normally."
Update 19:45 UTC: AWS is still experiencing some outage, but full recovery is in progress. The team stated "We continue to observe recovery across all AWS services, and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions."As AWS works towards a full resolution, customers who haven't resolved their issues are advised to flush their DNS caches. At TechPowerUp, our sovereign infrastructure is intentionally designed to operate without relying on external cloud providers. When an AWS, Azure, or GCP outage occurs, any service dependent on them is affected. If our infrastructure fails, it is solely due to our own error. Hence, this AWS outage hasn't affected our server. We provide a technical issues forum thread to update the community during an outage, which you can check out here.
Sources:
AWS Status, via The Verge
A few hours later, AWS confirmed that it had isolated the issue. "We have identified a potential root cause for error rates affecting the DynamoDB APIs in the US-EAST-1 Region," they stated, adding, "This issue also impacts other AWS services in the US-EAST-1 Region. Global services or features that rely on US-EAST-1 endpoints, such as IAM updates and DynamoDB Global tables, may also be experiencing issues. During this time, customers may be unable to create or update Support Cases. We recommend customers continue to retry any failed requests." Subsequently, AWS confirmed that the "underlying DNS issue has been fully mitigated, and most AWS service operations are now succeeding normally."
Update 19:45 UTC: AWS is still experiencing some outage, but full recovery is in progress. The team stated "We continue to observe recovery across all AWS services, and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions."As AWS works towards a full resolution, customers who haven't resolved their issues are advised to flush their DNS caches. At TechPowerUp, our sovereign infrastructure is intentionally designed to operate without relying on external cloud providers. When an AWS, Azure, or GCP outage occurs, any service dependent on them is affected. If our infrastructure fails, it is solely due to our own error. Hence, this AWS outage hasn't affected our server. We provide a technical issues forum thread to update the community during an outage, which you can check out here.


54 Comments on AWS Outage Takes Half of the Internet Down, Services Now Recovering
aws.amazon.com/s3/sla/
1. buy servers, switches, firewalls,
2. go to the datacenter, go through the background check, rent rack space for $$$$,
3. install your switches, firewall, server, storge (DAS or SAN depending on arch),
4. pay windows cals and /or install a VM hypervisor, provision virtual machines,
5. pay a sysadmin, network tech, and general support IT guy, to set it all up and to keep those running and locked down -
6. pay for licensing for managed switches, firewall, security software, redundant managed PDUs, and
7. pay security consultant to do a pentest/security report (if you're in finance or healthcare this is essentially mandatory).
8. Do the same thing at another COLO and configure a hot failover for redundancy (if you can afford it)
or you can
1. Click a few buttons on a WI, set up hot az failover, elastic storage.
2. Set up your OS, SGs, Subnets
3. Download AWS ISO/HIPAA/FERPA/HITRUST certs and attest that you have configured your services properly.
Also - good luck if you're a startup - if you have to shutter the business in 6 months and you're locked into a 12-36 month datacenter hosting agreement.
Ships sail (and float) with luck.
Also, if you're just using the WI and not CloudFormation in AWS for a real deployment, you should be slapped for not using IAC.
Remember when “cost/benefit analysis” meant “move all your manufacturing to China?”
(Sorry.)
But yeah, I saw more people reporting on this than I noticed it, so I might not have noticed it otherwise. But it also seemed to largely happen overnight for my time zone.
And these are manufacturing sectors where economies of scale play a far, far larger role than cloud services.
Could still start it manually, but then it will not ignore zones it's not allowed in.
Always online stuff like that seriously needs to be banned.
The computer still works though.
I've had tons of controllers fail over the years.
Then there's software. Windows 95 software didnt require an internet connection, how much of that just runs on a modern PC? I'd guess very little. Sure there's compatibility patches and mods and things like DOSBOX, but the OOTB experience with old software is pretty dire, just like modern internet connected software.
There are too many eggs in one basket.