1. Home
  2. Outages
  3. Microsoft Teams
  4. 17 Nov 2026

OutageTuesday 17 November 2026Ended 18 Nov, 03:21

Microsoft Teams outage on 17 November 2026

Problem reports about Microsoft Teams rose to outage level at 12:36 Central European time on Tuesday 17 November 2026 and stayed there for 14 h 45 min.

They peaked at 236 reports in 15 minutes at 15:11, about 14 times the usual level for that time of day, and 4,678 reports came in while the outage lasted.

Reports reached outage level in 10 countries, the US, the UK, Brazil, Germany and more.

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

Is Microsoft Teams down right now? 4 outages of Microsoft Teams

Started
12:36
Tue 17 Nov, Central European time
At outage level
14 h 45 min
Ended 03:21 on 18 Nov
Busiest 15 minutes
236
reports, at 15:11
Reports during the outage
4,678
Peak about 14× the usual level
Timeline

Reports from Tue 06:30 to Wed 06: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 Teams rose to outage level at 12:36 Central European time on Tuesday 17 November 2026 and stayed there for 14 h 45 min. They peaked at 236 reports in 15 minutes at 15:11, about 14 times the usual level for that time of day, and 4,678 reports came in while the outage lasted. Reports reached outage level in 10 countries, the US, the UK, Brazil, Germany 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 17 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 USOutage4,930
The UKOutage1,347
BrazilOutage460
GermanyOutage444
CanadaOutage430
IndiaOutage416
JapanOutage414
AustraliaOutage323
PolandOutage317
The NetherlandsOutage254
SpainNormal151
FranceNormal142
Same time

Other services with an outage at the same time

Their reports also reached outage level while Microsoft Teams'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 Teams: live status and other outages

Check whether Microsoft Teams 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 Teams's 4 outages since the archive began.

Earlier: 16 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 Teams outage on 17 November 2026: problem reports over time

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