1. Home
  2. Outages
  3. Microsoft 365
  4. 19 Nov 2026

OutageThursday 19 November 2026Ended 20 Nov, 08:44

Microsoft 365 outage on 19 November 2026

Problem reports about Microsoft 365 rose to outage level at 11:52 Central European time on Thursday 19 November 2026 and stayed there for 20 h 51 min.

They peaked at 246 reports in 15 minutes at 13:26, about 21 times the usual level for that time of day, and 7,932 reports came in while the outage lasted.

Reports reached outage level in 9 countries, the UK, Germany, Canada, Japan and more.

12 other services had an outage spike at the same time.

Is Microsoft 365 down right now? 2 outages of Microsoft 365

Started
11:52
Thu 19 Nov, Central European time
At outage level
20 h 51 min
Ended 08:44 on 20 Nov
Busiest 15 minutes
246
reports, at 13:26
Reports during the outage
7,932
Peak about 21× the usual level
Timeline

Reports from Thu 05:45 to Fri 14:45

One bar per 15 minutes, Central European time. Red bars are the outage; the dashed line is what a usual day sees at that time.

Problem reports about Microsoft 365 rose to outage level at 11:52 Central European time on Thursday 19 November 2026 and stayed there for 20 h 51 min. They peaked at 246 reports in 15 minutes at 13:26, about 21 times the usual level for that time of day, and 7,932 reports came in while the outage lasted. Reports reached outage level in 9 countries, the UK, Germany, Canada, Japan and more. 12 other services had an outage spike at the same time.
Around the world

Where people reported it that day

Each country's reports on 19 November, against the usual level there. Outage means reports stayed at outage level for half an hour or more; above usual, for an hour or more.

CountryThat dayReports
The USAbove usual8,409
The UKOutage1,950
GermanyOutage1,650
CanadaOutage847
JapanOutage776
AustraliaOutage416
BrazilOutage402
ItalyAbove usual291
The NetherlandsOutage288
IndiaNormal277
PolandNormal243
AustriaOutage207
Same time

Other services with an outage at the same time

Their reports also reached outage level while Microsoft 365's did. Many services failing together can point to a shared cause, such as a network or cloud provider, but reports alone cannot show it.

More

Microsoft 365: live status and other outages

Check whether Microsoft 365 is down right now: the live page shows the last 24 hours and fixes to try. This site keeps a page for each of Microsoft 365's 2 outages since the archive began.

Earlier: 12 Nov 2026 November 2026 outage report All recent outages

Embed

Put this outage in an article

Copy a frame with the chart and numbers above, or an image of the same card for places that do not allow frames, such as newsletters. Both link back to this page. More for journalists.

Microsoft 365 outage on 19 November 2026: problem reports over time

<iframe src="https://isitdownrightnow.app/embed/microsoft-365/2026-11-19/" title="Microsoft 365 outage on 19 November 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/microsoft-365/outages/2026-11-19/">Microsoft 365 outage on 19 November 2026</a> from IsItDownRightNow.app</p>Frame: the chart and numbers, as a small card
<a href="https://isitdownrightnow.app/services/microsoft-365/outages/2026-11-19/"><img src="https://isitdownrightnow.app/share/microsoft-365/2026-11-19.png" alt="Microsoft 365 outage on 19 November 2026: problem reports over time" width="600" height="315" loading="lazy"></a>Image: the same card as a picture
[![Microsoft 365 outage on 19 November 2026](https://isitdownrightnow.app/share/microsoft-365/2026-11-19.png)](https://isitdownrightnow.app/services/microsoft-365/outages/2026-11-19/)Markdown: the image, for README files and forums

Where these numbers come from

The numbers are problem reports that users sent to a public outage-reporting service, counted in 15-minute windows and kept as this site's live page showed them. A spike counts as an outage when reports are more than twice the usual level and far above the day's average. Reports show that many people had trouble at the same time, not what caused it; the service's own status page is the place for that.