rewindex

RewindexOutage eventsNov 13, 2026

Microsoft 365 outage, Nov 13, 2026

5 linked vendors posted 5 incidents between and . 5 vendors named Microsoft 365 in 5 incidents (5 of them blamed it). Microsoft 365 posted “Users may be unable to connect to multiple Microsoft 365 services” at 07:29 UTC. 4 other vendors had incidents in the same window; nothing links them to Microsoft 365 (listed below).

Observed, not verified. A line means a vendor’s incident named another vendor, or a known dependency (declared by the vendor and named as a cause before). It is not a proven cause. Incidents that only share the time window are listed apart.

Times are in UTC; lags are from when Microsoft 365 posted ().

  1. Microsoft 365 posted
Named Microsoft 365Named another vendor or depends on oneEach column is 30 minutes

How it spread

Vendors that named Microsoft 365, grouped by when they posted, and vendors that blamed one of the vendors Microsoft 365 took down. Solid lines: the vendor named the other. Dashed: a known dependency, not named in the incident.

Swipe sideways to see the whole diagram.

Microsoft 365posted 07:29 UTC1 to 4 hours later4 vendors, 4 blamed Microsoft 365Help Scout, Asana, Dynatrace, NetlifyLater1 vendor, 1 blamed Microsoft 365Mailchimp
Microsoft 365posted 07:29 UTC1 to 4 hours later4 vendors, 4 blamed Microsoft365Help Scout, Asana, Dynatrace,NetlifyLater1 vendor, 1 blamed Microsoft365Mailchimp
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
Mermaid source
flowchart LR
  root["Microsoft 365<br/>posted 07:29 UTC"]:::root
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed Microsoft 365<br/>Help Scout, Asana, Dynatrace, Netlify"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed Microsoft 365<br/>Mailchimp"]:::blames
  root --> later

Vendors that named Microsoft 365

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

1 to 4 hours later

4 vendors

Later

1 vendor

Also happening at the same time (not linked)

4 incidents from 4 vendors started in this window without naming Microsoft 365 or a linked vendor, and with no known dependency on them. Listed for context only; they are not counted as part of the event (an ordinary week has about 53 incidents in these hours).

Show all 4

Detected automatically from 9 status pages opening incidents in the peak hour (normally at most 9). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.