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
www.svenskbladet.se/utrikes/index.php?alias=katt-p-tangentbord-bakom-amazon-clouds-haveriThings that aren't connected to the internet?
(Do it again Leroy!)
Good to see TPU being pretty much immune from the general outage.
As for Signal, well, messages are always rather laggy, regardless of any shutdown or lack thereoff.
My only other complaint is that it can't process HDR videos properly, it's a known bug that should be resolved in time, but for now you have to convert the video to SDR first on device, then send it, or colours are washed out.
Bit of a shame to see it uses AWS, though it is encrypted and I suppose there's no real way of getting around that dominance.
I don't think it's fair to say that the messages are laggy, that's the exception, the norm is that it's pretty much the same as any other internet messaging app, in my experience, except you're not having massive privacy concerns from using a 'secure encrypted messaging service' provided by flipping Facebook, for example. I mean, even WA has irregular but repeated outages, and it seems to be much more of a target for spammers and phishing, too.
Anyway, none of this is really about AWS, the topic.
EDIT: W1zzard corrected me, they really don't depend on it much at all.Honestly it's amazing this does not happen more often, to be quite frank.
It doesn't help that the provider is on the west coast, so it's not even 5AM at their HQ.
I wouldn't call AWS' infrastructure shitty by any stretch of the imagination. Cloud service providers are offering a trade off and services. You can run your own servers and everything, but then you are on the hook for running them, maintaining them, securing them, and scaling them to demand, not to mention sourcing your own platform services for things like queueing, async processing, distributed file storage, etc. A smaller software company might not have the resources of a huge ops team, a flexible data center, and a suite of platform services with tooling to match.
To be completely fair, cloud solutions don't make much sense if all you're doing is running servers through EC2 with AWS or GCE with Google. They shine when it comes to their distributed services. Take S3 for example. You literally get multi-region replication out of the box without having to care about any of the infrastructure to do it. Same thing with Dynamo. You can provision everything with CloudFormation and use that to deploy from your CI/CD pipeline, all without having to care about infrastructure. There is a strength to that and only a fool would dismiss those tradeoffs.
So sure, you pay the Google or Amazon tax when you use their services, but on the other hand they let me scale horizontally, on demand, without having to care about the underlying infrastructure while providing distributed systems for things like file and data storage that work seamlessly with the rest of their platform. There is value to that.