# Canadians impacted by Microsoft outage could soon join new class-action lawsuit · ORBIT Outage Dissector

- Provider: Microsoft 365 · state: active · duration: 2d 19h
- CHYP Magnitude: **M4.0 Squall** (severity 0.45, breadth 0.37, duration 0.9, reach 0, corroboration 0.5)
- Content SHA-256: ea6832c31f1f0b1ff06ae62ac1d74cb99638deec5b5524fa9c4cc5c415764702

## Story

- **What happened:** Microsoft 365 reported “Canadians impacted by Microsoft outage could soon join new class-action lawsuit” starting Nov 18, 1:36 PM PT.
- **What broke:** The official source does not list components.
- **Who was hit:** Hit: 1 named location (North America). No catalogued services depend on Microsoft 365.
- **How it recovered:** Still open after 2d 19h.

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


## Timeline (PT)

### Official status
- Nov 19, 2:20 AM PT · Canadians impacted by Microsoft outage could soon join new class-action lawsuit

### Network & routing
- Nov 21, 5:00 AM PT · AS8075 (Microsoft Azure) BGP update churn -0.2σ vs 24h (https://www.chyp.ai/incident/event-nw-58452ceaa55a2b36)

### Early signals
- Nov 21, 7:00 AM PT · Microsoft 365 outage of 12 Nov 2026: Post Incident Report [pdf] (https://www.chyp.ai/signals/)

### News

### Coincidence (KEV)

## Historical twins

- 20% · 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/
- 20% · 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/
- 20% · Amazon Web Services 2024-07-30: Kinesis cell-management misidentified healthy hosts during a deployment (6h 52m) https://www.chyp.ai/dissect/m/aws-kinesis-2024-07-30/

## Cloudy_Day take (automated)

- Open 2d 19h. 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 12h 44m 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.blogto.com/city/2026/11/microsoft-outage-class-action-lawsuit-canada/
- NetWeather evidence page: https://www.chyp.ai/incident/event-nw-c6f61d14aaa1e12e

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