# AWS got hit by an outage too. Here's why you didn't hear about it · ORBIT Outage Dissector

- Provider: Amazon Web Services · state: active · duration: 11h 43m
- CHYP Magnitude: **M5.3 Storm** (severity 0.45, breadth 0.3, duration 0.71, reach 0.98, corroboration 0.25)
- Content SHA-256: 51c1d5c42939408aff8105a08dcde677544d4b96bbddad6ea66c3de01ac92741

## Story

- **What happened:** Amazon Web Services reported “AWS got hit by an outage too. Here's why you didn't hear about it” starting Nov 21, 6:35 AM PT.
- **What broke:** UAE, Bahrain.
- **Who was hit:** 136 catalogued services run on Amazon Web Services (inferred); 4 of them show an official problem in the same window (coincidence, not causation). Hit: global/unspecified.
- **How it recovered:** Still open after 11h 43m.

## Failure-mode fingerprint (automated keyword read (hypothesis, not root cause))

- Dependency cascade: 75% (“multiple services”, 4 dependents also unwell)

## Timeline (PT)

### Official status
- Nov 21, 6:40 AM PT · AWS got hit by an outage too. Here's why you didn't hear about it

### Network & routing
- Nov 21, 1:00 PM PT · AS16509 (AWS) BGP update churn -0.7σ vs 24h (https://www.chyp.ai/incident/event-nw-face4ea50757bcdf)

### Early signals

### News

### Coincidence (KEV)

## Historical twins

- 77% · Amazon Web Services 2025-10-19: DynamoDB DNS automation wrote an empty record it could not repair (14h 32m overall (three distinct impact periods)) https://www.chyp.ai/dissect/m/aws-dynamodb-2025-10-19/
- 70% · Amazon Web Services 2024-07-30: Kinesis cell-management misidentified healthy hosts during a deployment (6h 52m) https://www.chyp.ai/dissect/m/aws-kinesis-2024-07-30/
- 70% · Amazon Web Services 2023-06-13: Lambda cell crossed a capacity threshold and hit a latent defect (3h 48m to full recovery) https://www.chyp.ai/dissect/m/aws-lambda-2023-06-13/

## Cloudy_Day take (automated)

- 4 services that sit on Amazon Web Services are unwell at the same time. That's a lead to check, not proof of a cascade.
- 136 catalogued services lean on one provider. That's concentration risk, and it's the real headline.
- By the clock it has outlasted 17 of 19 indexed meltdowns (median 3h 48m). By impact it isn't close. That's why ORBIT ranks by magnitude, not minutes.

## Sources

- Amazon Web Services official status page: https://www.theregister.com/columnists/2026/11/21/aws-got-hit-by-an-outage-too-heres-why-you-didnt-hear-about-it/5311511
- NetWeather evidence page: https://www.chyp.ai/incident/event-nw-40de7832e3907106

## Limits

- Media or community attention. It is reporting evidence, not network telemetry, and is excluded from the v2 Network Signals index.
- Region: global / unspecified. The source did not assert a region; none was inferred from publisher location.
- Temporal overlap with other events is coincidence, not causation, unless a provider states a causal link.
- NetWeather is independent research, not an official status source. Confirm with the provider.
- Correlation is not causation.

> Cite: ORBIT by Cloudy_Day, Outage Dissector, https://www.chyp.ai/dissect/event-nw-40de7832e3907106/
> Automated data from ORBIT (Cloudy_Day Security Suite). Independent research, not affiliated with any government agency, vendor or data provider. Not an official status source.
