#us-east-1 — Public Fediverse posts

lol, seid ihr alle schon ganz digital unabhängig auf #Signal unterwegs gewesen?

#aws #useast1 #did #dat #dut

What Caused the Massive AWS Outage in 2025? Understanding the Global Internet Meltdown

Published: October 25, 2025 – DoRaleigh.com Tech & Digital Infrastructure News

On October 20, 2025, the world witnessed one of the most severe cloud disruptions in modern history — a massive AWS outage that rippled across the entire digital landscape. The hours-long event shut down major companies, stalled global commerce, disrupted travel, and reminded everyone just how dependent we’ve become on Amazon Web Services.

If you woke up on Monday wondering why your bank app wasn’t working, why Alexa wasn’t responding, or why your business tools refused to load, you weren’t alone. A single malfunction inside AWS’s northern Virginia data center brought significant portions of the internet to a halt.

Below, we break down exactly what caused the AWS outage, who was affected, and why this failure matters for the future of cloud computing.

What Triggered the AWS Outage on October 20, 2025?

Amazon confirmed that the outage originated inside its US-EAST-1 region, the company’s oldest — and most relied-upon — data center cluster located in northern Virginia.

The Root Cause: A Malfunctioning Internal Monitoring Subsystem

According to AWS:

An internal subsystem responsible for monitoring the health of network load balancers within its EC2 service malfunctioned. This triggered a cascade of DNS resolution failures, preventing AWS services from translating domain names to IP addresses. With DNS failing, critical services such as DynamoDB — a database underpinning more than 100 AWS tools — stopped functioning properly. As DynamoDB and EC2 degraded, systems across the global internet collapsed under the pressure.

In short:

A small internal failure disrupted the internet’s traffic routers, broke DNS, and halted key AWS services powering thousands of companies worldwide.

How Long Did the AWS Outage Last?

The outage lasted several hours, spanning the late morning through evening on October 20. Amazon restored most core functions by nighttime, but many companies continued experiencing:

Delays Slow service recovery Massive backlogs of queued requests

For businesses relying on real-time operations — think airports, banks, and delivery services — every hour mattered.

Which Companies Were Affected by the 2025 AWS Outage?

The short answer: Almost everyone.

Millions of consumers faced app crashes, login failures, and communication blackouts as services across entertainment, finance, retail, and transportation ground to a halt.

Major Companies Affected

Finance & Payments:

Venmo Coinbase Robinhood

Communication & Tech:

Slack Zoom Microsoft Teams WhatsApp Signal Reddit Perplexity

Entertainment & Gaming:

Hulu HBO Max Fortnite Spotify

Retail & Food Service:

Starbucks McDonald’s Instacart

Transportation:

Delta United Airlines Uber Lyft

Telecom:

AT&T Verizon T-Mobile

Even Amazon itself wasn’t spared — Alexa, Prime Video, Ring, and parts of Amazon’s warehouse operations went offline.

Public agencies were hit as well, including the NYC MTA and the U.K.’s HMRC tax website.

Why Was This AWS Outage Such a Big Deal?

AWS isn’t just another cloud provider. It powers:

A third of the global cloud computing market Millions of websites and mobile apps Critical infrastructure from airlines to hospitals Retail and logistics systems used worldwide

This incident marks the third major outage in five years linked to the same data cluster, US-EAST-1 — a region so essential that downtime there often looks like downtime everywhere.

Just a year after the disastrous Crowdstrike malfunction of 2024, which impacted healthcare and transportation networks globally, the 2025 AWS outage reinforced a hard truth:

The world’s digital infrastructure is concentrated in the hands of a few tech giants. When one of them falters — even briefly — the world feels it immediately.

Was the AWS Outage Caused by a Cyberattack?

No.

Amazon reported no evidence of hacking, malware, or external interference.

Instead, the outage was triggered by an internal technical malfunction — proof that even routine system failures can have enormous consequences when cloud platforms are this interconnected.

What Is AWS, and Why Does It Matter So Much?

For those who don’t work directly in cloud services, here’s a quick refresher:

What AWS Provides

Cloud storage Virtual servers Databases Networking AI tools Enterprise hosting App infrastructure

AWS essentially acts as the scaffolding of the internet, allowing companies to scale up without maintaining physical servers.

From startups to Fortune 500s, most digital services run on AWS — which explains why this outage reached nearly every corner of daily life.

How the AWS Outage Impacts Raleigh & the Triangle

Though the outage was global, the Triangle felt the effects locally:

Raleigh’s tech companies relying on AWS tools like EC2, S3, and Lambda reported delays and downtime. Local residents struggled with apps like Instacart, Lyft, Slack, and Venmo. RDU travelers reported check-in issues with airlines whose systems rely on AWS. Smart home users across Durham, Cary, and Raleigh experienced Alexa failures throughout the day.

The Triangle’s growing reputation as a tech hub means regional businesses increasingly depend on cloud platforms — outages like this highlight the need for redundancy and disaster-planning.

Final Thoughts: A Wake-Up Call for Global Tech Infrastructure

The 2025 AWS outage wasn’t just an inconvenience — it was a global warning shot. As the digital world continues to centralize around a small number of cloud providers, even minor internal failures can cause:

Financial losses Systemic business disruptions Transportation delays Communication breakdowns Global economic ripple effects

While AWS restored functionality by the end of the day, the event exposed just how fragile the internet truly is — and how vital it is for governments, companies, and cloud providers to invest in more resilient infrastructure.

Follow DoRaleigh.com for daily updates on government meetings, local festivals, and community happenings — your one-stop guide to everything Raleigh!

Follow Us: Instagram | Facebook | BSky | Linkedin

#amazon #amazonWebServices #aws #cloudComputing #cloudOutage #dnsFailure #infrastructure #internetOutage #news #raleighTech #techNews #technology #usEast1

Lỗi DNS bên trong hệ thống của AWS gây ra sự cố ngừng hoạt động của us-east-1, không phải do DynamoDB. Hệ thống DNS nhiều lớp của AWS bị lỗi, dẫn đến các dịch vụ phụ thuộc vào DynamoDB bị ảnh hưởng. #AWS #DynamoDB #DNS #LỗiHệThống #CôngNghệ #SựCố #UsEast1 #LỗiDNS #HệThốngPhânTán #CôngNghệThôngTin #LỗiKỹThuật

https://www.reddit.com/r/programming/comments/1omfq4q/what_actually_caused_the_aws_useast1_outage_a/

https://www.europesays.com/pl/75145/ Awaria ekosystemu Microsoft, brak możliwości logowania do Azure, Minecraft i pakietu biurowego 365. W tle ponownie Amazon AWS #AmazonWebServices #awaria #aws #azure #Biznes #Business #ChmuraObliczeniowa #cyberbezpieczenstwo #dns #InfrastrukturaIT #logowanie #microsoft #Microsoft365 #minecraft #PL #Poland #Polish #Polska #Polski #problemy #USEAST1

https://www.europesays.com/pl/69457/ Pusty rekord DNS położył pół internetu. Amazon ujawnia szokujące kulisy 15-godzinnej katastrofy dla 3500 firm i 17 mln użytkowników #AmazonWebServices #awaria #aws #Biznes #Business #ChmuraObliczeniowa #cyberbezpieczenstwo #dns #DORA #DynamoDB #InfrastrukturaIT #KoncentracjaRyzyka #PL #Poland #Polish #Polska #Polski #RaceCondition #RegulacjeUE #roblox #snapchat #USEAST1

Summary of the Amazon DynamoDB Service Disruption in US-East-1 Region

https://aws.amazon.com/message/101925/

#HackerNews #AmazonDynamoDB #ServiceDisruption #USEast1 #CloudComputing #AWS #News

[Перевод] Сбой AWS 19­–20 октября: во всём виноват DNS. Постмортем

19–20 октября 2025 года в регионе us-east-1 произошёл каскадный сбой, повлиявший на доступность глобальных сервисов. Компания AWS опубликовала детальный разбор, в котором раскрыла первопричину — дефект в автоматизированной системе управления DNS для сервиса DynamoDB. В статье приводятся полная хронология событий, описание воздействия на смежные сервисы (EC2, NLB, Lambda) и список запланированных улучшений для предотвращения подобных инцидентов в будущем.

https://habr.com/ru/companies/flant/articles/959422/

#dns #aws #dynamodb #lambda #ec2 #useast1 #сбой #nlb #amazon_web_services #сбой_aws

https://blog.gslin.org/archives/2025/10/23/12696/%e9%80%99%e6%ac%a1-us-east-1-%e7%82%b8%e6%8e%89%ef%bc%8caws-%e5%ae%98%e6%96%b9%e5%a0%b1%e5%91%8a%e5%87%ba%e7%88%90%e4%ba%86/

這次 us-east-1 炸掉，AWS 官方報告出爐了

#amazon #analysis #aws #cause #cloud #down #downtime #dynamodb #outage #rca #region #report #root #service #uptime #UsEast1

Do we need to mention that Coocook.org was NOT affected by the #AWSdown #USEast1 disaster? 😜

Instead, to be honest, it’s running on a 10+ year old 1U server at a community-organized ISP in my hometown #Leipzig without any complex #HighAvailability setup. The machine has been running like this surprisingly steady all those years 🙈

If you feel this should be changed, please comment and consider donating for new hardware or professional hosting via https://coocook.org/about 😇

@beandev Ich war am stärksten durch den Ausfall von #SignalApp betroffen und konnte das recht geräuschlos überdauern.

Jetzt gebe ich der Sache ein paar Tage ohne Spekulationen, um dann genüsslich ein Post Mortem zu lesen …

#useast1

War es nun DNS oder menschliches Versagen?

#aws #useast1

@leftpaddotpy

us-east-1 should just do an OVH and a lot of problems would be solved. Longterm at least...

#AWS #OVH #useast1

@Illdisposed just to be clear, the internet (as in network of networks) worked just fine. But it does not help to have all eggs in one basket when you drop it. Eggs in this case are services accessed over the internet and the basket is #aws #useast1. See also https://chaos.social/@pcdog/115405696703809435

Baskets are expensive. That's why most companies put all their eggs in just one. #useast1

after the fiasco of us-east dying yesterday we're considering spinning up a matrix instance and moving from signal eventually so we can keep in contact with our loved ones . . .

Does anyone run their own instance?
Any issues with running it? or fixes to bugs?
Tricks and tips?

(Boosts Welcome!)

#matrix #useast1 #aws #signal #selfhosting

Every time #aws #useast1 goes down, we indulge in a good snark post on how alarms, cat feeders, HVAC, and lighting need local-first control planes, but then keep merrily building the Internet of 💩.
Until next time ...

Okay. This one made me snort. #awsoutage #us-east-1

RE: https://bsky.app/profile/did:plc:mgflc2hwqonaafnbb3xok6re/post/3m3mmwicyfin2

That aged entertainingly.

#aws #useast1 #amazon #cloud

https://hachyderm.io/@BenjaminHCCarr/112339196589769612

War die Idee der Cloud nicht, dass alles weiterläuft, wenn mal ein Teil ausfällt?

Jaja, ich finde selbst heraus.

#aws #useast1

Major AWS Outage

Amazon Web Services is experiencing a large-scale failure in the US-EAST-1 region, disrupting core AWS infrastructure and major third-party apps worldwide.

forum.hashpwn.net/post/4994

#aws #outage #amazon #useast1 #cybersecurity #news #hashpwn

We've had one, yes,

#aws #UsEast1

#useast1 lessons learned: #Decentralize!

I wonder how many cars wouldn't start this morning?

#UsEast1

@isotopp 🤦

Good thing of them dogfooding: if they fuck up, they do not get support spammed as you can not open support requests. #aws #useast1 #dogfooding

Anyone know if there's an equivalent to https://grid.iamkate.com/ for USA/ North Virginia? I'm wondering if the #AWS #useast1 #dns #outage and recovery had a visible effect on the power consumption

#grid #electricity #powergrids

Remember, kids, every outside ("cloud") service is one more point of failure you're not allowed to fix yourself.

#UsEast1

Alle beschweren sich hier im Fediverse, dass nix mehr mit dem Ausfall von AWS funktioniert, im Internet.

Also eure Nachrichten erreichen mich.

Das Fediverse funktioniert. 😊

#aws #useast1 #Fediverse

I think I get an inkling that us-east-1 going down was just as bad as I and others imagined.

https://ioc.exchange/@flyingsaceur/115274432764105605

#AWS #USEast1

In Anlehnung an https://www.reddit.com/r/networkingmemes/s/5xseMpXaPY sollten wir das Diagramm für Hosting anpassen...

#useast1 #awsoutage

Why should UK banks be affected by the AWS US-East-1 outage? Why are we using a US datacentre for UK consumer financial operations - Lloyds, Halifax, Bank of Scotland, others? Why are they not using the UK region, or an EU region at least?

#AWS #useast1

A major #AWS #outage is impacting services like Alexa, Snapchat, Fortnite, and more, particularly in the #USEAST1 Region. The cause is under investigation, and #recovery is underway. https://www.theverge.com/news/802486/aws-outage-alexa-fortnite-snapchat-offline?eicker.news #tech #media #news

Kaum bin ich im Urlaub, fällt AWS aus.

Sorry.

#aws #useast1

Amazon people frantically editing /etc/hosts files everywhere to get DynamoDB working again ;) Time for a coffee.

https://health.aws.amazon.com/health/status

#ItsAlwaysDNS #AWS #DynamoDB #USEAST1

ale ten Signal, to mně teda netěší...

#aws #useast1 #outage

https://blog.gslin.org/archives/2025/06/06/12439/%e5%bf%98%e8%a8%98%e6%af%94%e8%bc%83-us-east-1-%e8%88%87-ap-east-2-%e7%9a%84%e5%83%b9%e9%8c%a2%e4%ba%86%ef%bc%9f/

忘記比較 us-east-1 與 ap-east-2 的價錢了？

#amazon #ApEast2 #aws #cloud #ec2 #pricing #region #s3 #service #taipei #taiwan #UsEast1

AWS 打算把 us-east-1 拓展到 Maryland

看到 AWS 的公告提到要把 us-east-1 拓展到 Maryland：「In the works – New Availability Zone in Maryland for US East (Northern Virginia) Region」。 us-east-1 有不少機房在 Ashburn，不過 AWS 不會公開提/承認，主要還是各種第三方蒐集的資料：「Amazon AWS: Ashburn Data Centers Locations (15)」。 AWS 要求 AZ 之間必須在 100km 內 (剛好維持光纖來回在 1ms 以下)： All Availability Zones are physically sep…

https://blog.gslin.org/archives/2025/04/25/12365/aws-%e6%89%93%e7%ae%97%e6%8a%8a-us-east-1-%e6%8b%93%e5%b1%95%e5%88%b0-maryland/

#amazon #ashburn #aws #cloud #maryland #northern #region #service #UsEast1 #virginia

It's always #useast1

#aws

#USEAST1 region is not the cloudy crock it's made out to be, claims #AWS #EC2 boss
It's the region where stuff gets stressed at scale first, says Dave Brown, as he plots variants of #Amazon's Outposts. #AmazonWebServices' US-EAST-1 region is not a problem child – it's the region where the cloudy colossus often runs things at bigger scale than elsewhere and therefore stresses services the most, according to Dave Brown, global veep for compute and networking. https://www.theregister.com/2024/04/10/aws_dave_brown_ec2_futures/

Sodding #useast1

#aws

I'm literally right now putting together a presentation on DR and mutiregion resilience for a workshop at the end of the month, and I would like to thank AWS US East 1 for its service.

#useast1 #use1 #aws #dr #resilience #failover #activeshmactive