AWS Outage 2025: Full List of Sites and Apps Affected as Amazon Cloud Service Disrupted

Bassyonni

ago 3 hours

AWS Outage 2025

A major AWS outage on Monday, October 20, 2025 rippled across the internet, taking popular apps and critical services offline for hours. The disruption centered on US-EAST-1 (Northern Virginia) and involved internal service dependencies with knock-on DNS/connectivity issues. Recovery is largely in progress, but some platforms continue to report intermittent errors as traffic backlogs clear. There is no verified evidence of a cyberattack; indicators point to an internal incident within AWS.

Full list: sites and apps hit by the AWS outage (grouped by category)

Social & communications

Snapchat, Signal, Reddit (logins, feeds, and message delivery affected)
Some status pages and help centers throttled during peak error windows

Education & learning

Canvas (LMS), College Board tools
Language and learning apps including Duolingo

Finance & payments

Coinbase, Robinhood, Venmo, Chime
Sporadic issues at additional banking portals tied to cloud-hosted components

Smart home & Amazon ecosystem

Alexa, Ring (device connectivity and notifications delayed)
Elements of Amazon.com retail and Prime Video intermittently degraded

Gaming & entertainment

Fortnite, Epic Games Store, Roblox
PUBG: Battlegrounds, Rainbow Six Siege, Clash of Clans/Royale
Casual and puzzle titles including Wordle experienced slow or failed loads

Streaming, media & creators

Twitch, Vimeo; some news and puzzle portals saw intermittent availability
Playback and login flows for several TV/music apps briefly unstable

Design, productivity & developer tools

Canva, Airtable, Zapier
Collaboration and project suites (e.g., Slack, Atlassian properties) with degraded workflows
E-commerce and storefront backends including Shopify

Transportation, retail & food apps

McDonald’s app and other quick-service ordering tools
Assorted delivery and retail checkout systems that rely on cloud APIs

Note: Impact varied by customer architecture and region. Some brands recovered earlier than others, and a few saw only partial feature degradation (e.g., logins failing while cached content still loaded).

Timeline and status

~Early morning ET (Oct 20): AWS posts elevated error rates/latency in US-EAST-1 affecting compute, networking, and services that rely on those endpoints.
Midday to afternoon: Mitigations reduce EC2 launch failures, improve Lambda invocation stability, and ease network connectivity issues.
Evening into night: AWS reports core issues mitigated; many customer workloads stable, but residual failures persist as DNS caches and queues drain.
Today: Most consumer-facing apps are operational, with sporadic errors possible during retries and backlog processing.

What caused the AWS outage?

Preliminary signals point to an internal service malfunction in the affected region that cascaded into dependency layers (including load-balancer/health-monitoring behavior and DNS resolution), making healthy endpoints appear unreachable and throttling new capacity launches. Formal post-incident notes typically follow later; for now, the working summary is internal AWS fault, not an external attack.

Why so many apps went down at once

Even multi-region apps share common control planes—identity, DNS, monitoring, orchestration—and third-party SDKs that are anchored in US-EAST-1. When those shared layers wobble, thousands of independent services can fail together, producing a “many apps, one root” scenario.

If your app is still glitchy: quick fixes

Hard refresh / relaunch the app; on mobile, force-quit first.
Toggle networks (Wi-Fi ↔ cellular) to refresh DNS paths.
Clear cache or try private mode to pick up updated endpoints.
Avoid repeated submissions (orders, forms, payments) until status banners show stable; duplicates can process once queues clear.
Canvas users: Screenshot error timestamps and contact instructors—institutions commonly extend deadlines after widespread outages.

FAQs

Is AWS still down?
Core services are mostly recovered; lingering errors may appear as systems rebalance.

Was this a cyberattack?
There’s no verified indication of one. Evidence points to internal AWS issues in US-EAST-1 with DNS side effects.

Did this affect my data?
Incidents like this primarily impact availability, not integrity. Still, verify payments, trades, and submissions started during the outage window.

When will everything be fully normal?
Stabilization is service-by-service. Most consumer apps normalize within hours of mitigation; some edge cases take longer as caches expire and backlogs flush.

The AWS outage of October 20, 2025 briefly broke a big slice of the internet, impacting social, finance, gaming, education, and smart-home apps. Services are largely back, but intermittent issues can continue until the ecosystem fully clears.