CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h

Microsoft Azure baseline M4.9 Squall since Nov 19, 1:00 AM PT

Microsoft Azure reported “AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h” starting Nov 19, 1:00 AM PT.

  • 2d 22hDurationand counting
  • —Systems namedfrom the source
  • —Places named0 on the map
  • 24Dependentscatalogued, inferred
  • 1/4Evidence kindsindependent families
  • 54Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 19, 3 AMNov 19, 4 PMNov 20, 5 AMNov 20, 7 PMNov 21, 8 AMNov 21, 9 PM Official statusNov 19, 4:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +5.5σ vs 24hNov 19, 6:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +1.3σ vs 24hNov 19, 8:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.8σ vs 24hNov 19, 10:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +1.0σ vs 24hNov 19, 11:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +1.3σ vs 24hNov 19, 12:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24hNov 19, 2:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +4.7σ vs 24hNov 19, 4:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24hNov 19, 6:01 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24hNov 19, 7:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.4σ vs 24hNov 19, 8:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.6σ vs 24hNov 19, 9:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.7σ vs 24hNov 19, 10:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.1σ vs 24hNov 19, 11:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.3σ vs 24hNov 20, 12:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +0.5σ vs 24hNov 20, 1:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +0.6σ vs 24hNov 20, 2:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -1.0σ vs 24hNov 20, 3:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -1.1σ vs 24hNov 20, 4:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +4.2σ vs 24hNov 20, 5:01 AM PT · AS8075 (Microsoft Azure) BGP update churn +4.4σ vs 24hNov 20, 6:30 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24hNov 20, 7:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.4σ vs 24hNov 20, 8:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +1.5σ vs 24hNov 20, 9:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +2.2σ vs 24hNov 20, 12:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.7σ vs 24hNov 20, 1:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.7σ vs 24hNov 20, 2:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.1σ vs 24hNov 20, 4:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.2σ vs 24hNov 20, 4:30 PM PT · AS8075 (Microsoft Azure) BGP update churn +5.3σ vs 24hNov 20, 5:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +5.6σ vs 24hNov 20, 7:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.0σ vs 24hNov 20, 9:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.4σ vs 24hNov 20, 10:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.9σ vs 24hNov 20, 11:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.4σ vs 24hNov 21, 12:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24hNov 21, 1:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24hNov 21, 2:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +2.7σ vs 24hNov 21, 3:00 AM PT · AS8075 (Microsoft Azure) BGP update churn +2.8σ vs 24hNov 21, 4:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.2σ vs 24hNov 21, 6:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24hNov 21, 7:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24hNov 21, 8:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.2σ vs 24hNov 21, 10:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.7σ vs 24hNov 21, 11:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.8σ vs 24hNov 21, 12:30 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24hNov 21, 1:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24hNov 21, 2:30 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.5σ vs 24hNov 21, 4:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.4σ vs 24hNov 21, 4:30 PM PT · AS8075 (Microsoft Azure) BGP update churn +1.7σ vs 24hNov 21, 6:00 PM PT · AS8075 (Microsoft Azure) BGP update churn +0.9σ vs 24hNov 21, 7:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24hNov 21, 8:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.6σ vs 24hNov 21, 9:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.5σ vs 24hNov 21, 10:00 PM PT · AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24hNetwork & routingnothing in this windowEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (KEV)nothing in this window ▼ startnow ▼

Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.

What happened

Microsoft Azure reported “AS8075 (Microsoft Azure) BGP update churn -0.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 22h, at or near its peak (1 state).

2Blast radius

Elastic Cloud · Degraded / minor incident · unwell in the same window (coincidence, not causation)Elastic CloudJFrog · MaintenanceJFrogAiven · OperationalAivenGitHub · OperationalGitHubGitHub Copilot · OperationalGitHub CopilotGrafana Cloud · OperationalGrafana CloudLinkedIn · OperationalLinkedInMongoDB Atlas · OperationalMongoDB AtlasOpenAI (ChatGPT & API) · OperationalOpenAI (ChatGPT…Snowflake · OperationalSnowflakeAdobe Creative Cloud · no official feed / staleAdobe Creative …Bitwarden · no official feed / staleBitwardenCostco · no official feed / staleCostcoDatabricks · no official feed / staleDatabricksDatadog · no official feed / staleDatadogDocusign · no official feed / staleDocusignMicrosoft 365 · no official feed / staleMicrosoft 365Microsoft Teams · no official feed / staleMicrosoft TeamsMinecraft · no official feed / staleMinecraftNeon · no official feed / staleNeonOutlook.com · no official feed / staleOutlook.comRedis Cloud · no official feed / staleRedis CloudWalmart · no official feed / staleWalmartXbox Network · no official feed / staleXbox NetworkMicrosoft Azu…24 dependents

Center: Microsoft Azure. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. 1 are unwell in the same window: a lead, not proof of a cascade. Dependencies are inferred from public information.

3Blast map

No place names in the public text. Region tag: global/unspecified.

Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Config propagation“update”, “updates”
  • Dependency cascade1 dependent also unwell
  • Retry amplificationno sign
  • Control-plane couplingno sign
  • Capacity exhaustionno sign

Automated keyword read of the public updates. A hypothesis to test, never a root cause.

5Evidence matrix

Official statusOfficial status · Nov 18, 7:00 PM PT: 0 itemsOfficial status · Nov 18, 10:12 PM PT: 0 itemsOfficial status · Nov 19, 1:24 AM PT: 1 itemOfficial status · Nov 19, 4:37 AM PT: 1 itemOfficial status · Nov 19, 7:49 AM PT: 3 itemsOfficial status · Nov 19, 11:02 AM PT: 2 itemsOfficial status · Nov 19, 2:14 PM PT: 1 itemOfficial status · Nov 19, 5:27 PM PT: 3 itemsOfficial status · Nov 19, 8:39 PM PT: 3 itemsOfficial status · Nov 19, 11:52 PM PT: 4 itemsOfficial status · Nov 20, 3:04 AM PT: 2 itemsOfficial status · Nov 20, 6:17 AM PT: 4 itemsOfficial status · Nov 20, 9:29 AM PT: 1 itemOfficial status · Nov 20, 12:42 PM PT: 2 itemsOfficial status · Nov 20, 3:54 PM PT: 4 itemsOfficial status · Nov 20, 7:06 PM PT: 2 itemsOfficial status · Nov 20, 10:19 PM PT: 3 itemsOfficial status · Nov 21, 1:31 AM PT: 3 itemsOfficial status · Nov 21, 4:44 AM PT: 2 itemsOfficial status · Nov 21, 7:56 AM PT: 3 itemsOfficial status · Nov 21, 11:09 AM PT: 2 itemsOfficial status · Nov 21, 2:21 PM PT: 3 itemsOfficial status · Nov 21, 5:34 PM PT: 3 itemsOfficial status · Nov 21, 8:46 PM PT: 2 itemsNetwork & routingNetwork & routing · Nov 18, 7:00 PM PT: 0 itemsNetwork & routing · Nov 18, 10:12 PM PT: 0 itemsNetwork & routing · Nov 19, 1:24 AM PT: 0 itemsNetwork & routing · Nov 19, 4:37 AM PT: 0 itemsNetwork & routing · Nov 19, 7:49 AM PT: 0 itemsNetwork & routing · Nov 19, 11:02 AM PT: 0 itemsNetwork & routing · Nov 19, 2:14 PM PT: 0 itemsNetwork & routing · Nov 19, 5:27 PM PT: 0 itemsNetwork & routing · Nov 19, 8:39 PM PT: 0 itemsNetwork & routing · Nov 19, 11:52 PM PT: 0 itemsNetwork & routing · Nov 20, 3:04 AM PT: 0 itemsNetwork & routing · Nov 20, 6:17 AM PT: 0 itemsNetwork & routing · Nov 20, 9:29 AM PT: 0 itemsNetwork & routing · Nov 20, 12:42 PM PT: 0 itemsNetwork & routing · Nov 20, 3:54 PM PT: 0 itemsNetwork & routing · Nov 20, 7:06 PM PT: 0 itemsNetwork & routing · Nov 20, 10:19 PM PT: 0 itemsNetwork & routing · Nov 21, 1:31 AM PT: 0 itemsNetwork & routing · Nov 21, 4:44 AM PT: 0 itemsNetwork & routing · Nov 21, 7:56 AM PT: 0 itemsNetwork & routing · Nov 21, 11:09 AM PT: 0 itemsNetwork & routing · Nov 21, 2:21 PM PT: 0 itemsNetwork & routing · Nov 21, 5:34 PM PT: 0 itemsNetwork & routing · Nov 21, 8:46 PM PT: 0 itemsEarly signalsEarly signals · Nov 18, 7:00 PM PT: 0 itemsEarly signals · Nov 18, 10:12 PM PT: 0 itemsEarly signals · Nov 19, 1:24 AM PT: 0 itemsEarly signals · Nov 19, 4:37 AM PT: 0 itemsEarly signals · Nov 19, 7:49 AM PT: 0 itemsEarly signals · Nov 19, 11:02 AM PT: 0 itemsEarly signals · Nov 19, 2:14 PM PT: 0 itemsEarly signals · Nov 19, 5:27 PM PT: 0 itemsEarly signals · Nov 19, 8:39 PM PT: 0 itemsEarly signals · Nov 19, 11:52 PM PT: 0 itemsEarly signals · Nov 20, 3:04 AM PT: 0 itemsEarly signals · Nov 20, 6:17 AM PT: 0 itemsEarly signals · Nov 20, 9:29 AM PT: 0 itemsEarly signals · Nov 20, 12:42 PM PT: 0 itemsEarly signals · Nov 20, 3:54 PM PT: 0 itemsEarly signals · Nov 20, 7:06 PM PT: 0 itemsEarly signals · Nov 20, 10:19 PM PT: 0 itemsEarly signals · Nov 21, 1:31 AM PT: 0 itemsEarly signals · Nov 21, 4:44 AM PT: 0 itemsEarly signals · Nov 21, 7:56 AM PT: 0 itemsEarly signals · Nov 21, 11:09 AM PT: 0 itemsEarly signals · Nov 21, 2:21 PM PT: 0 itemsEarly signals · Nov 21, 5:34 PM PT: 0 itemsEarly signals · Nov 21, 8:46 PM PT: 0 itemsNews & chatterNews & chatter · Nov 18, 7:00 PM PT: 0 itemsNews & chatter · Nov 18, 10:12 PM PT: 0 itemsNews & chatter · Nov 19, 1:24 AM PT: 0 itemsNews & chatter · Nov 19, 4:37 AM PT: 0 itemsNews & chatter · Nov 19, 7:49 AM PT: 0 itemsNews & chatter · Nov 19, 11:02 AM PT: 0 itemsNews & chatter · Nov 19, 2:14 PM PT: 0 itemsNews & chatter · Nov 19, 5:27 PM PT: 0 itemsNews & chatter · Nov 19, 8:39 PM PT: 0 itemsNews & chatter · Nov 19, 11:52 PM PT: 0 itemsNews & chatter · Nov 20, 3:04 AM PT: 0 itemsNews & chatter · Nov 20, 6:17 AM PT: 0 itemsNews & chatter · Nov 20, 9:29 AM PT: 0 itemsNews & chatter · Nov 20, 12:42 PM PT: 0 itemsNews & chatter · Nov 20, 3:54 PM PT: 0 itemsNews & chatter · Nov 20, 7:06 PM PT: 0 itemsNews & chatter · Nov 20, 10:19 PM PT: 0 itemsNews & chatter · Nov 21, 1:31 AM PT: 0 itemsNews & chatter · Nov 21, 4:44 AM PT: 0 itemsNews & chatter · Nov 21, 7:56 AM PT: 0 itemsNews & chatter · Nov 21, 11:09 AM PT: 0 itemsNews & chatter · Nov 21, 2:21 PM PT: 0 itemsNews & chatter · Nov 21, 5:34 PM PT: 0 itemsNews & chatter · Nov 21, 8:46 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 18, 7:00 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 10:12 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 1:24 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:37 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:49 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 11:02 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 2:14 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 5:27 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 8:39 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 11:52 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 3:04 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 6:17 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 9:29 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:42 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 3:54 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:06 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 10:19 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 1:31 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 4:44 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 7:56 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 11:09 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 2:21 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 5:34 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 8:46 PM PT: 0 itemsNov 18, 7:00 PM PTnow

Correlation is not causation

Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.

6Four clocks

Source says it beganNov 19, 1:00 AM PTORBIT first saw itNov 19, 4:00 AM PTLatest source updateNov 21, 7:00 PM PTLast checkedNov 21, 11:30 PM PT

Detection gap: 3h 1m between the source's start time and ORBIT's first sighting.

Public status always trails reality. These are the times each public record states, in PT.

7Historical twins

Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.

Cloudy_Day take

  • Open 2d 22h. 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.

Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Microsoft Azure.

8Dissection capsule

Share card for this dissection

Everything above as one shareable, citable capsule with a content hash.

JSON capsuleMarkdownShare card (SVG)

Open Microsoft Azure in the War Room →NetWeather evidence page →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-58452ceaa55a2b36/"><img src="https://www.chyp.ai/dissect/event-nw-58452ceaa55a2b36/card.svg" alt="AS8075 (Microsoft Azure) BGP update churn -0.3σ vs 24h · ORBIT Outage Dissector" width="600"></a>

Sources & 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. Lanes are kept apart so overlap never reads as cause.
  • ORBIT is passive: it never contacts the provider or probes its systems. Independent researcher, not affiliated.