# AWS UAE: Multiple services — Region Availability · ORBIT Outage Dissector

- Provider: Amazon Web Services · state: chronic · duration: 67d 2h
- CHYP Magnitude: **M5.8 Storm** (severity 0.45, breadth 0.37, duration 1, reach 0.98, corroboration 0.25)
- Content SHA-256: 60164630fa99f27723576ae2530251ba6d1dcd2ddd7ef33e5d71359239b8da3e

## Story

- **What happened:** Amazon Web Services reported “AWS UAE: Multiple services — Region Availability” starting Sep 15, 3:27 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: 1 named location (AWS me-central-1).
- **How it recovered:** Still open after 67d 2h.

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

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

## Timeline (PT)

### Official status
- Nov 19, 3:38 AM PT · AWS UAE: Multiple services — Region Availability
- Nov 20, 9:53 PM PT · Official status Major outage → Operational

### Network & routing
- Nov 21, 1:00 AM 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

- 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 67d 2h. 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://health.aws.amazon.com/health/status
- NetWeather evidence page: https://www.chyp.ai/incident/event-nw-81114b4b940dc565

## Limits

- Provider-stated: this repeats what the vendor's public status page said. It is not an independent root-cause verification.
- 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-81114b4b940dc565/
> 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.
