# Microsoft 365 outage forces Japanese workers back to fax machines · ORBIT Outage Dissector

- Provider: Microsoft 365 · state: active · duration: 3d 4h
- CHYP Magnitude: **M4.0 Squall** (severity 0.45, breadth 0.37, duration 0.91, reach 0, corroboration 0.5)
- Content SHA-256: 0fa5b362f3dbc4afc34243fcf8c9b5fd220c7ffe83864c22bc560787fca8f42f

## Story

- **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.

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

- Control-plane coupling: 30% (“workers”)

## Timeline (PT)

### Official status
- Nov 19, 2:20 AM PT · Microsoft 365 outage forces Japanese workers back to fax machines

### Network & routing
- Nov 18, 1:31 AM PT · Akamai: Customer Security Advisory: CVE-2026-114938 (https://www.chyp.ai/dissect/event-nw-0e2462a31b8725c5/)
- Nov 21, 1:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.2σ vs 24h (https://www.chyp.ai/incident/event-nw-58452ceaa55a2b36)

### Early signals

### News

### Coincidence (KEV)

## Historical twins

- 43% · 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/
- 43% · 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/
- 35% · 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 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.

## Sources

- Microsoft 365 official status page: https://www.techradar.com/pro/microsoft-365-outage-saw-japanese-workers-fire-up-their-fax-machines
- NetWeather evidence page: https://www.chyp.ai/incident/event-nw-11f9df5ec4bcdbf4

## 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.

> Cite: ORBIT by Cloudy_Day, Outage Dissector, https://www.chyp.ai/dissect/event-nw-11f9df5ec4bcdbf4/
> 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.
