CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report

Exchange / Microsoft 365: servers unexpectedly unavailable, core process overwhelmed

Microsoft Azure ongoing at capture M8.8 Meltdown 2026-11-12

Microsoft Azure: Exchange / Microsoft 365: servers unexpectedly unavailable, core process overwhelmed. Scope: Global.

  • 8d 19hDurationand counting
  • 13Systems namedfrom the source
  • 7Places named7 on the map
  • 24Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 1Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 12, 5 PMNov 14, 8 AMNov 15, 11 PMNov 17, 3 PMNov 19, 6 AMNov 20, 9 PM Official statusNov 12, 9:30 AM PT · Impact begins (vendor-stated)Network & 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: Exchange / Microsoft 365: servers unexpectedly unavailable, core process overwhelmed. Scope: Global.

What broke

Exchange Online, Outlook, Microsoft Teams, SharePoint Online and 9 more.

Who was hit

24 catalogued services run on Microsoft Azure (inferred). Hit: Global.

How it recovered

Mitigated after 8d 19h (vendor wording: Ongoing as of 3:19 PM PT (no official full-restore time in the sourced notes)).

2Blast radius

Elastic Cloud · Degraded / minor incidentElastic 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. Dependencies are inferred from public information.

3Blast map

North America · vendor-stated scope: globalSouth America · vendor-stated scope: globalEurope · vendor-stated scope: globalAfrica · vendor-stated scope: globalMiddle East · vendor-stated scope: globalAsia · vendor-stated scope: globalOceania · vendor-stated scope: global
  1. North America
  2. South America
  3. Europe
  4. Africa
  5. Middle East
  6. Asia
  7. Oceania

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

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Capacity exhaustionvendor post-incident report (Meltdown Index)
  • Dependency cascadevendor post-incident report (Meltdown Index)
  • Retry amplificationno sign
  • Control-plane couplingno sign
  • Config propagationno sign

Failure modes as stated in the vendor's own post-incident report (Meltdown Index).

5Evidence matrix

Official statusOfficial status · Nov 12, 3:30 AM PT: 1 itemOfficial status · Nov 12, 12:33 PM PT: 0 itemsOfficial status · Nov 12, 9:36 PM PT: 0 itemsOfficial status · Nov 13, 6:39 AM PT: 0 itemsOfficial status · Nov 13, 3:42 PM PT: 0 itemsOfficial status · Nov 14, 12:45 AM PT: 0 itemsOfficial status · Nov 14, 9:48 AM PT: 0 itemsOfficial status · Nov 14, 6:52 PM PT: 0 itemsOfficial status · Nov 15, 3:55 AM PT: 0 itemsOfficial status · Nov 15, 12:58 PM PT: 0 itemsOfficial status · Nov 15, 10:01 PM PT: 0 itemsOfficial status · Nov 16, 7:04 AM PT: 0 itemsOfficial status · Nov 16, 4:07 PM PT: 0 itemsOfficial status · Nov 17, 1:11 AM PT: 0 itemsOfficial status · Nov 17, 10:14 AM PT: 0 itemsOfficial status · Nov 17, 7:17 PM PT: 0 itemsOfficial status · Nov 18, 4:20 AM PT: 0 itemsOfficial status · Nov 18, 1:23 PM PT: 0 itemsOfficial status · Nov 18, 10:26 PM PT: 0 itemsOfficial status · Nov 19, 7:30 AM PT: 0 itemsOfficial status · Nov 19, 4:33 PM PT: 0 itemsOfficial status · Nov 20, 1:36 AM PT: 0 itemsOfficial status · Nov 20, 10:39 AM PT: 0 itemsOfficial status · Nov 20, 7:42 PM PT: 0 itemsNetwork & routingNetwork & routing · Nov 12, 3:30 AM PT: 0 itemsNetwork & routing · Nov 12, 12:33 PM PT: 0 itemsNetwork & routing · Nov 12, 9:36 PM PT: 0 itemsNetwork & routing · Nov 13, 6:39 AM PT: 0 itemsNetwork & routing · Nov 13, 3:42 PM PT: 0 itemsNetwork & routing · Nov 14, 12:45 AM PT: 0 itemsNetwork & routing · Nov 14, 9:48 AM PT: 0 itemsNetwork & routing · Nov 14, 6:52 PM PT: 0 itemsNetwork & routing · Nov 15, 3:55 AM PT: 0 itemsNetwork & routing · Nov 15, 12:58 PM PT: 0 itemsNetwork & routing · Nov 15, 10:01 PM PT: 0 itemsNetwork & routing · Nov 16, 7:04 AM PT: 0 itemsNetwork & routing · Nov 16, 4:07 PM PT: 0 itemsNetwork & routing · Nov 17, 1:11 AM PT: 0 itemsNetwork & routing · Nov 17, 10:14 AM PT: 0 itemsNetwork & routing · Nov 17, 7:17 PM PT: 0 itemsNetwork & routing · Nov 18, 4:20 AM PT: 0 itemsNetwork & routing · Nov 18, 1:23 PM PT: 0 itemsNetwork & routing · Nov 18, 10:26 PM PT: 0 itemsNetwork & routing · Nov 19, 7:30 AM PT: 0 itemsNetwork & routing · Nov 19, 4:33 PM PT: 0 itemsNetwork & routing · Nov 20, 1:36 AM PT: 0 itemsNetwork & routing · Nov 20, 10:39 AM PT: 0 itemsNetwork & routing · Nov 20, 7:42 PM PT: 0 itemsEarly signalsEarly signals · Nov 12, 3:30 AM PT: 0 itemsEarly signals · Nov 12, 12:33 PM PT: 0 itemsEarly signals · Nov 12, 9:36 PM PT: 0 itemsEarly signals · Nov 13, 6:39 AM PT: 0 itemsEarly signals · Nov 13, 3:42 PM PT: 0 itemsEarly signals · Nov 14, 12:45 AM PT: 0 itemsEarly signals · Nov 14, 9:48 AM PT: 0 itemsEarly signals · Nov 14, 6:52 PM PT: 0 itemsEarly signals · Nov 15, 3:55 AM PT: 0 itemsEarly signals · Nov 15, 12:58 PM PT: 0 itemsEarly signals · Nov 15, 10:01 PM PT: 0 itemsEarly signals · Nov 16, 7:04 AM PT: 0 itemsEarly signals · Nov 16, 4:07 PM PT: 0 itemsEarly signals · Nov 17, 1:11 AM PT: 0 itemsEarly signals · Nov 17, 10:14 AM PT: 0 itemsEarly signals · Nov 17, 7:17 PM PT: 0 itemsEarly signals · Nov 18, 4:20 AM PT: 0 itemsEarly signals · Nov 18, 1:23 PM PT: 0 itemsEarly signals · Nov 18, 10:26 PM PT: 0 itemsEarly signals · Nov 19, 7:30 AM PT: 0 itemsEarly signals · Nov 19, 4:33 PM PT: 0 itemsEarly signals · Nov 20, 1:36 AM PT: 0 itemsEarly signals · Nov 20, 10:39 AM PT: 0 itemsEarly signals · Nov 20, 7:42 PM PT: 0 itemsNews & chatterNews & chatter · Nov 12, 3:30 AM PT: 0 itemsNews & chatter · Nov 12, 12:33 PM PT: 0 itemsNews & chatter · Nov 12, 9:36 PM PT: 0 itemsNews & chatter · Nov 13, 6:39 AM PT: 0 itemsNews & chatter · Nov 13, 3:42 PM PT: 0 itemsNews & chatter · Nov 14, 12:45 AM PT: 0 itemsNews & chatter · Nov 14, 9:48 AM PT: 0 itemsNews & chatter · Nov 14, 6:52 PM PT: 0 itemsNews & chatter · Nov 15, 3:55 AM PT: 0 itemsNews & chatter · Nov 15, 12:58 PM PT: 0 itemsNews & chatter · Nov 15, 10:01 PM PT: 0 itemsNews & chatter · Nov 16, 7:04 AM PT: 0 itemsNews & chatter · Nov 16, 4:07 PM PT: 0 itemsNews & chatter · Nov 17, 1:11 AM PT: 0 itemsNews & chatter · Nov 17, 10:14 AM PT: 0 itemsNews & chatter · Nov 17, 7:17 PM PT: 0 itemsNews & chatter · Nov 18, 4:20 AM PT: 0 itemsNews & chatter · Nov 18, 1:23 PM PT: 0 itemsNews & chatter · Nov 18, 10:26 PM PT: 0 itemsNews & chatter · Nov 19, 7:30 AM PT: 0 itemsNews & chatter · Nov 19, 4:33 PM PT: 0 itemsNews & chatter · Nov 20, 1:36 AM PT: 0 itemsNews & chatter · Nov 20, 10:39 AM PT: 0 itemsNews & chatter · Nov 20, 7:42 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 12, 3:30 AM PT: 0 itemsCoincidence (KEV) · Nov 12, 12:33 PM PT: 0 itemsCoincidence (KEV) · Nov 12, 9:36 PM PT: 0 itemsCoincidence (KEV) · Nov 13, 6:39 AM PT: 0 itemsCoincidence (KEV) · Nov 13, 3:42 PM PT: 0 itemsCoincidence (KEV) · Nov 14, 12:45 AM PT: 0 itemsCoincidence (KEV) · Nov 14, 9:48 AM PT: 0 itemsCoincidence (KEV) · Nov 14, 6:52 PM PT: 0 itemsCoincidence (KEV) · Nov 15, 3:55 AM PT: 0 itemsCoincidence (KEV) · Nov 15, 12:58 PM PT: 0 itemsCoincidence (KEV) · Nov 15, 10:01 PM PT: 0 itemsCoincidence (KEV) · Nov 16, 7:04 AM PT: 0 itemsCoincidence (KEV) · Nov 16, 4:07 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 1:11 AM PT: 0 itemsCoincidence (KEV) · Nov 17, 10:14 AM PT: 0 itemsCoincidence (KEV) · Nov 17, 7:17 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 4:20 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 1:23 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 10:26 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 7:30 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:33 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 1:36 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 10:39 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:42 PM PT: 0 itemsNov 12, 3:30 AM 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.

6In the vendor's words

We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure.

Start about 9:30 AM PT (ThousandEyes public analysis cited ~17:30 UTC); the campus StatusHub incident was created at 10:24 AM PT. Official wording is Microsoft’s, republished on the StatusHub mirror (update 4 at 11:53 AM PT; update 8 at 2:21 PM PT). A StatusHub update 9 around 3:19 PM PT had not declared a full restore. Microsoft’s public status.cloud.microsoft page, captured around 4:07 PM PT the same day, no longer showed a live incident banner. No confirmed official end time is recorded.

Verbatim excerpt from University of Illinois StatusHub incident 982055 (Microsoft service-health notes, 12 Nov 2026).

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 8d 19h. At that age this is a standing condition, not an incident. It deserves its own runbook and its own SLO conversation.
  • Longer than 19 of 19 indexed control-plane meltdowns with a stated duration.

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 →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/m/ms365-2026-11-12/"><img src="https://www.chyp.ai/dissect/m/ms365-2026-11-12/card.svg" alt="Exchange / Microsoft 365: servers unexpectedly unavailable,… · ORBIT Outage Dissector" width="600"></a>

Sources & limits

  • Taken from the vendor's own post-incident report; quotes are verbatim excerpts.
  • Dependents are today's inferred catalogue, not who was affected on the day.
  • 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.