Early Monday morning, October 20, 2025, millions of users woke up to broken apps, frozen devices and websites that simply wouldn’t load as a result of an data-analytics-id=”inline-link” href=”https://www.tomsguide.com/news/live/amazon-outage-october-2025″ data-before-rewrite-localise=”https://www.tomsguide.com/news/live/amazon-outage-october-2025″>AWS outage we’re tracking live. Services like data-analytics-id=”inline-link” href=”https://www.tomsguide.com/news/live/snapchat-outage-live-october-20″ data-before-rewrite-localise=”https://www.tomsguide.com/news/live/snapchat-outage-live-october-20″>Snapchat, Ring, Alexa, data-analytics-id=”inline-link” href=”https://www.tomsguide.com/tag/fortnite” data-auto-tag-linker=”true” data-before-rewrite-localise=”https://www.tomsguide.com/tag/fortnite”>Fortnite and even some online banking services went dark for several hours — all because of one cloud region in Northern Virginia.
AWS says the culprit was a DNS issue inside its DynamoDB service, which caused a chain reaction that rippled across the web. In simpler terms: one of…
