# AS16509 (AWS) BGP update churn -0.7σ vs 24h · ORBIT Outage Dissector

- Provider: Amazon Web Services · state: baseline · duration: 2d 4h
- CHYP Magnitude: **M5.5 Storm** (severity 0.45, breadth 0.3, duration 0.87, reach 0.98, corroboration 0.25)
- Content SHA-256: 54580bd503f25b58e237fbc71b5d50f37521cd68ad2c11de3c113352303ffd75

## Story

- **What happened:** Amazon Web Services reported “AS16509 (AWS) BGP update churn -0.7σ vs 24h” starting Nov 19, 1:00 AM PT.
- **What broke:** UAE, Bahrain.
- **Who was hit:** 136 catalogued services run on Amazon Web Services (inferred); 6 of them show an official problem in the same window (coincidence, not causation). Hit: global/unspecified.
- **How it recovered:** Still open after 2d 4h, at or near its peak (1 state).

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

- Dependency cascade: 75% (“multiple services”, 6 dependents also unwell)
- Config propagation: 60% (“update”, “updates”)

## Timeline (PT)

### Official status
- Nov 19, 4:00 AM PT · AS16509 (AWS) BGP update churn -1.3σ vs 24h
- Nov 19, 6:00 AM PT · AS16509 (AWS) BGP update churn +0.0σ vs 24h
- Nov 19, 7:00 AM PT · AS16509 (AWS) BGP update churn +0.3σ vs 24h
- Nov 19, 8:00 AM PT · AS16509 (AWS) BGP update churn -0.7σ vs 24h
- Nov 19, 9:00 AM PT · AS16509 (AWS) BGP update churn -0.9σ vs 24h
- Nov 19, 10:00 AM PT · AS16509 (AWS) BGP update churn -1.4σ vs 24h
- Nov 19, 12:00 PM PT · AS16509 (AWS) BGP update churn -0.9σ vs 24h
- Nov 19, 1:30 PM PT · AS16509 (AWS) BGP update churn -1.1σ vs 24h
- Nov 19, 2:00 PM PT · AS16509 (AWS) BGP update churn -0.6σ vs 24h
- Nov 19, 4:00 PM PT · AS16509 (AWS) BGP update churn -1.7σ vs 24h
- Nov 19, 5:00 PM PT · AS16509 (AWS) BGP update churn -1.8σ vs 24h
- Nov 19, 6:01 PM PT · AS16509 (AWS) BGP update churn -1.8σ vs 24h
- Nov 19, 6:30 PM PT · AS16509 (AWS) BGP update churn +1.3σ vs 24h
- Nov 19, 7:00 PM PT · AS16509 (AWS) BGP update churn +1.4σ vs 24h
- Nov 19, 8:00 PM PT · AS16509 (AWS) BGP update churn +0.1σ vs 24h
- Nov 19, 9:00 PM PT · AS16509 (AWS) BGP update churn +0.2σ vs 24h
- Nov 19, 10:30 PM PT · AS16509 (AWS) BGP update churn -0.5σ vs 24h
- Nov 20, 12:00 AM PT · AS16509 (AWS) BGP update churn -1.3σ vs 24h
- Nov 20, 2:00 AM PT · AS16509 (AWS) BGP update churn -1.2σ vs 24h
- Nov 20, 4:00 AM PT · AS16509 (AWS) BGP update churn -0.3σ vs 24h
- Nov 20, 6:30 AM PT · AS16509 (AWS) BGP update churn +0.7σ vs 24h
- Nov 20, 8:30 AM PT · AS16509 (AWS) BGP update churn +0.3σ vs 24h
- Nov 20, 9:00 AM PT · AS16509 (AWS) BGP update churn +0.3σ vs 24h
- Nov 20, 11:30 AM PT · AS16509 (AWS) BGP update churn -1.1σ vs 24h
- Nov 20, 12:30 PM PT · AS16509 (AWS) BGP update churn -0.1σ vs 24h
- Nov 20, 2:00 PM PT · AS16509 (AWS) BGP update churn +7.2σ vs 24h
- Nov 20, 4:30 PM PT · AS16509 (AWS) BGP update churn -1.5σ vs 24h
- Nov 20, 6:00 PM PT · AS16509 (AWS) BGP update churn -1.3σ vs 24h
- Nov 20, 7:00 PM PT · AS16509 (AWS) BGP update churn -1.8σ vs 24h
- Nov 20, 8:00 PM PT · AS16509 (AWS) BGP update churn -1.6σ vs 24h
- Nov 20, 9:00 PM PT · AS16509 (AWS) BGP update churn -1.9σ vs 24h
- Nov 20, 9:53 PM PT · Official status Major outage → Operational
- Nov 20, 11:00 PM PT · AS16509 (AWS) BGP update churn -1.9σ vs 24h
- Nov 21, 12:00 AM PT · AS16509 (AWS) BGP update churn +0.9σ vs 24h
- Nov 21, 2:00 AM PT · AS16509 (AWS) BGP update churn -0.4σ vs 24h
- Nov 21, 4:00 AM PT · AS16509 (AWS) BGP update churn -0.7σ vs 24h

### Network & routing

### Early signals

### News

### Coincidence (KEV)

## Historical twins

- 85% · 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 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/
- 66% · 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)

- Open 2d 4h. At that age this is a standing condition, not an incident. It deserves its own runbook and its own SLO conversation.
- 6 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 19 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://stat.ripe.net/AS16509
- NetWeather evidence page: https://www.chyp.ai/incident/event-nw-face4ea50757bcdf

## Limits

- A measured routing/public-network change. It does not by itself prove end-user impact or an incident.
- 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-face4ea50757bcdf/
> 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.
