# AS8075 (Microsoft Azure) BGP update churn +1.3σ vs 24h · ORBIT Outage Dissector

- Provider: Microsoft Azure · state: baseline · duration: 2d 23h
- CHYP Magnitude: **M4.9 Squall** (severity 0.45, breadth 0.3, duration 0.91, reach 0.64, corroboration 0.25)
- Content SHA-256: fd54243d58d936d7db340a4c3b255ed4db9fd0bccbbe3bfbe0fded7a03a790eb

## Story

- **What happened:** Microsoft Azure reported “AS8075 (Microsoft Azure) BGP update churn +1.3σ vs 24h” starting Nov 19, 1:00 AM PT.
- **What broke:** The official source does not list components.
- **Who was hit:** 24 catalogued services run on Microsoft Azure (inferred); 1 of them show an official problem in the same window (coincidence, not causation). Hit: global/unspecified.
- **How it recovered:** Still open after 2d 23h, at or near its peak (1 state).

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

- Config propagation: 60% (“update”, “updates”)
- Dependency cascade: 15% (1 dependent also unwell)

## Timeline (PT)

### Official status
- Nov 19, 4:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +5.5σ vs 24h
- Nov 19, 6:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +1.3σ vs 24h
- Nov 19, 8:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.8σ vs 24h
- Nov 19, 10:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +1.0σ vs 24h
- Nov 19, 11:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +1.3σ vs 24h
- Nov 19, 12:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24h
- Nov 19, 2:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +4.7σ vs 24h
- Nov 19, 4:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24h
- Nov 19, 6:01 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24h
- Nov 19, 7:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.4σ vs 24h
- Nov 19, 8:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.6σ vs 24h
- Nov 19, 9:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.7σ vs 24h
- Nov 19, 10:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.1σ vs 24h
- Nov 19, 11:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.3σ vs 24h
- Nov 20, 12:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +0.5σ vs 24h
- Nov 20, 1:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +0.6σ vs 24h
- Nov 20, 2:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -1.0σ vs 24h
- Nov 20, 3:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -1.1σ vs 24h
- Nov 20, 4:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +4.2σ vs 24h
- Nov 20, 5:01 AM PT · AS8075 (Microsoft Azure) BGP update churn +4.4σ vs 24h
- Nov 20, 6:30 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24h
- Nov 20, 7:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24h
- Nov 20, 8:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +1.5σ vs 24h
- Nov 20, 9:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +2.2σ vs 24h
- Nov 20, 12:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.7σ vs 24h
- Nov 20, 1:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.7σ vs 24h
- Nov 20, 2:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.1σ vs 24h
- Nov 20, 4:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.2σ vs 24h
- Nov 20, 4:30 PM PT · AS8075 (Microsoft Azure) BGP update churn +5.3σ vs 24h
- Nov 20, 5:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +5.6σ vs 24h
- Nov 20, 7:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.0σ vs 24h
- Nov 20, 9:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.4σ vs 24h
- Nov 20, 10:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.9σ vs 24h
- Nov 20, 11:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.4σ vs 24h
- Nov 21, 12:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h
- Nov 21, 1:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h
- Nov 21, 2:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +2.7σ vs 24h
- Nov 21, 3:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +2.8σ vs 24h
- Nov 21, 4:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.2σ vs 24h
- Nov 21, 6:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h
- Nov 21, 7:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h
- Nov 21, 8:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.2σ vs 24h
- Nov 21, 10:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.7σ vs 24h
- Nov 21, 11:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.8σ vs 24h
- Nov 21, 12:30 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h
- Nov 21, 1:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h
- Nov 21, 2:30 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.5σ vs 24h
- Nov 21, 4:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.4σ vs 24h
- Nov 21, 4:30 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.7σ vs 24h
- Nov 21, 6:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.9σ vs 24h
- Nov 21, 7:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h
- Nov 21, 8:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.6σ vs 24h
- Nov 21, 9:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.5σ vs 24h
- Nov 21, 10:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h
- Nov 22, 12:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +1.3σ vs 24h

### Network & routing

### Early signals

### News

### Coincidence (KEV)

## Historical twins

- 77% · Microsoft Azure 2024-09-27: ARM control plane blocked by a global Cosmos DB misconfiguration (1h 38m) https://www.chyp.ai/dissect/m/azure-arm-gov-2024-09-27/
- 68% · Microsoft Azure 2025-10-09: Front Door: manual metadata cleanup bypassed protection (8h 10m (availability restored 12:50 UTC)) https://www.chyp.ai/dissect/m/azure-afd-2025-10-09/
- 68% · Microsoft Azure 2024-07-30: Front Door: network control-plane failure plus latent routing configuration (7h 58m (majority by 13:58 UTC)) https://www.chyp.ai/dissect/m/azure-afd-2024-07-30/

## Cloudy_Day take (automated)

- Open 2d 23h. At that age this is a standing condition, not an incident. It deserves its own runbook and its own SLO conversation.
- The words in the public updates point at a change or rollout. If that holds, the question is why it got past canary.
- 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.
- ORBIT first saw this 3h 1m after the source's own start time. The gap is part of the story: public status trails reality.

## Sources

- Microsoft Azure official status page: https://stat.ripe.net/AS8075
- NetWeather evidence page: https://www.chyp.ai/incident/event-nw-58452ceaa55a2b36

## 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-58452ceaa55a2b36/
> 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.
