CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

Microsoft 365 outage forces Japanese workers back to fax machines

Microsoft 365 active M4.0 Squall since Nov 18, 12:10 AM PT

Microsoft 365 reported “Microsoft 365 outage forces Japanese workers back to fax machines” starting Nov 18, 12:10 AM PT.

  • 3d 4hDurationand counting
  • —Systems namedfrom the source
  • 1Places named1 on the map
  • 0Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 1Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 18, 2 AMNov 18, 5 PMNov 19, 7 AMNov 19, 9 PMNov 20, 11 AMNov 21, 2 AM Official statusNov 19, 2:20 AM PT · Microsoft 365 outage forces Japanese workers back to fax machinesNetwork & routingNov 18, 1:31 AM PT · Akamai: Customer Security Advisory: CVE-2026-114938Nov 21, 1:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.2σ vs 24hEarly 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 365 reported “Microsoft 365 outage forces Japanese workers back to fax machines” starting Nov 18, 12:10 AM PT.

What broke

The official source does not list components.

Who was hit

Hit: 1 named location (Asia). No catalogued services depend on Microsoft 365.

How it recovered

Still open after 3d 4h.

2Blast radius

Microsoft Azure · OperationalMicrosoft AzureMicrosoft 3650 dependents

Center: Microsoft 365. 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

Asia
  1. Asia

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

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Control-plane coupling“workers”
  • Retry amplificationno sign
  • Config propagationno sign
  • Dependency cascadeno 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 17, 6:10 PM PT: 0 itemsOfficial status · Nov 17, 9:37 PM PT: 0 itemsOfficial status · Nov 18, 1:03 AM PT: 0 itemsOfficial status · Nov 18, 4:29 AM PT: 0 itemsOfficial status · Nov 18, 7:56 AM PT: 0 itemsOfficial status · Nov 18, 11:22 AM PT: 0 itemsOfficial status · Nov 18, 2:48 PM PT: 0 itemsOfficial status · Nov 18, 6:15 PM PT: 0 itemsOfficial status · Nov 18, 9:41 PM PT: 0 itemsOfficial status · Nov 19, 1:07 AM PT: 1 itemOfficial status · Nov 19, 4:34 AM PT: 0 itemsOfficial status · Nov 19, 8:00 AM PT: 0 itemsOfficial status · Nov 19, 11:26 AM PT: 0 itemsOfficial status · Nov 19, 2:53 PM PT: 0 itemsOfficial status · Nov 19, 6:19 PM PT: 0 itemsOfficial status · Nov 19, 9:45 PM PT: 0 itemsOfficial status · Nov 20, 1:12 AM PT: 0 itemsOfficial status · Nov 20, 4:38 AM PT: 0 itemsOfficial status · Nov 20, 8:04 AM PT: 0 itemsOfficial status · Nov 20, 11:31 AM PT: 0 itemsOfficial status · Nov 20, 2:57 PM PT: 0 itemsOfficial status · Nov 20, 6:23 PM PT: 0 itemsOfficial status · Nov 20, 9:50 PM PT: 0 itemsOfficial status · Nov 21, 1:16 AM PT: 0 itemsNetwork & routingNetwork & routing · Nov 17, 6:10 PM PT: 0 itemsNetwork & routing · Nov 17, 9:37 PM PT: 0 itemsNetwork & routing · Nov 18, 1:03 AM PT: 1 itemNetwork & routing · Nov 18, 4:29 AM PT: 0 itemsNetwork & routing · Nov 18, 7:56 AM PT: 0 itemsNetwork & routing · Nov 18, 11:22 AM PT: 0 itemsNetwork & routing · Nov 18, 2:48 PM PT: 0 itemsNetwork & routing · Nov 18, 6:15 PM PT: 0 itemsNetwork & routing · Nov 18, 9:41 PM PT: 0 itemsNetwork & routing · Nov 19, 1:07 AM PT: 0 itemsNetwork & routing · Nov 19, 4:34 AM PT: 0 itemsNetwork & routing · Nov 19, 8:00 AM PT: 0 itemsNetwork & routing · Nov 19, 11:26 AM PT: 0 itemsNetwork & routing · Nov 19, 2:53 PM PT: 0 itemsNetwork & routing · Nov 19, 6:19 PM PT: 0 itemsNetwork & routing · Nov 19, 9:45 PM PT: 0 itemsNetwork & routing · Nov 20, 1:12 AM PT: 0 itemsNetwork & routing · Nov 20, 4:38 AM PT: 0 itemsNetwork & routing · Nov 20, 8:04 AM PT: 0 itemsNetwork & routing · Nov 20, 11:31 AM PT: 0 itemsNetwork & routing · Nov 20, 2:57 PM PT: 0 itemsNetwork & routing · Nov 20, 6:23 PM PT: 0 itemsNetwork & routing · Nov 20, 9:50 PM PT: 1 itemNetwork & routing · Nov 21, 1:16 AM PT: 0 itemsEarly signalsEarly signals · Nov 17, 6:10 PM PT: 0 itemsEarly signals · Nov 17, 9:37 PM PT: 0 itemsEarly signals · Nov 18, 1:03 AM PT: 0 itemsEarly signals · Nov 18, 4:29 AM PT: 0 itemsEarly signals · Nov 18, 7:56 AM PT: 0 itemsEarly signals · Nov 18, 11:22 AM PT: 0 itemsEarly signals · Nov 18, 2:48 PM PT: 0 itemsEarly signals · Nov 18, 6:15 PM PT: 0 itemsEarly signals · Nov 18, 9:41 PM PT: 0 itemsEarly signals · Nov 19, 1:07 AM PT: 0 itemsEarly signals · Nov 19, 4:34 AM PT: 0 itemsEarly signals · Nov 19, 8:00 AM PT: 0 itemsEarly signals · Nov 19, 11:26 AM PT: 0 itemsEarly signals · Nov 19, 2:53 PM PT: 0 itemsEarly signals · Nov 19, 6:19 PM PT: 0 itemsEarly signals · Nov 19, 9:45 PM PT: 0 itemsEarly signals · Nov 20, 1:12 AM PT: 0 itemsEarly signals · Nov 20, 4:38 AM PT: 0 itemsEarly signals · Nov 20, 8:04 AM PT: 0 itemsEarly signals · Nov 20, 11:31 AM PT: 0 itemsEarly signals · Nov 20, 2:57 PM PT: 0 itemsEarly signals · Nov 20, 6:23 PM PT: 0 itemsEarly signals · Nov 20, 9:50 PM PT: 0 itemsEarly signals · Nov 21, 1:16 AM PT: 0 itemsNews & chatterNews & chatter · Nov 17, 6:10 PM PT: 0 itemsNews & chatter · Nov 17, 9:37 PM PT: 0 itemsNews & chatter · Nov 18, 1:03 AM PT: 0 itemsNews & chatter · Nov 18, 4:29 AM PT: 0 itemsNews & chatter · Nov 18, 7:56 AM PT: 0 itemsNews & chatter · Nov 18, 11:22 AM PT: 0 itemsNews & chatter · Nov 18, 2:48 PM PT: 0 itemsNews & chatter · Nov 18, 6:15 PM PT: 0 itemsNews & chatter · Nov 18, 9:41 PM PT: 0 itemsNews & chatter · Nov 19, 1:07 AM PT: 0 itemsNews & chatter · Nov 19, 4:34 AM PT: 0 itemsNews & chatter · Nov 19, 8:00 AM PT: 0 itemsNews & chatter · Nov 19, 11:26 AM PT: 0 itemsNews & chatter · Nov 19, 2:53 PM PT: 0 itemsNews & chatter · Nov 19, 6:19 PM PT: 0 itemsNews & chatter · Nov 19, 9:45 PM PT: 0 itemsNews & chatter · Nov 20, 1:12 AM PT: 0 itemsNews & chatter · Nov 20, 4:38 AM PT: 0 itemsNews & chatter · Nov 20, 8:04 AM PT: 0 itemsNews & chatter · Nov 20, 11:31 AM PT: 0 itemsNews & chatter · Nov 20, 2:57 PM PT: 0 itemsNews & chatter · Nov 20, 6:23 PM PT: 0 itemsNews & chatter · Nov 20, 9:50 PM PT: 0 itemsNews & chatter · Nov 21, 1:16 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 17, 6:10 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 9:37 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 1:03 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 4:29 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 7:56 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 11:22 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 2:48 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 6:15 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 9:41 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 1:07 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 4:34 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 8:00 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 11:26 AM PT: 0 itemsCoincidence (KEV) · Nov 19, 2:53 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 6:19 PM PT: 0 itemsCoincidence (KEV) · Nov 19, 9:45 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 1:12 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 4:38 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 8:04 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 11:31 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 2:57 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 6:23 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 9:50 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 1:16 AM PT: 0 itemsNov 17, 6:10 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 18, 12:10 AM PTORBIT first saw itNov 19, 2:20 AM PTLatest source updateNov 18, 12:10 AM PTLast checkedNov 21, 4:40 AM PT

Detection gap: 26h 10m 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 3d 4h. At that age this is a standing condition, not an incident. It deserves its own runbook and its own SLO conversation.
  • 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 26h 10m 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 365.

8Dissection capsule

Share card for this dissection

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

JSON capsuleMarkdownShare card (SVG)

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

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-11f9df5ec4bcdbf4/"><img src="https://www.chyp.ai/dissect/event-nw-11f9df5ec4bcdbf4/card.svg" alt="Microsoft 365 outage forces Japanese workers back to fax ma… · ORBIT Outage Dissector" width="600"></a>

Sources & limits

  • Media or community attention. It is reporting evidence, not network telemetry, and is excluded from the v2 Network Signals index.
  • 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.