1. Home
  2. Outages
  3. Microsoft Store
  4. 16 Nov 2026

OutageMonday 16 November 2026Ended 17 Nov, 07:06

Microsoft Store outage on 16 November 2026

Problem reports about Microsoft Store rose to outage level at 12:06 Central European time on Monday 16 November 2026 and stayed there for 19 h.

They peaked at 235 reports in 15 minutes at 21:52, about 39 times the usual level for that time of day, and 5,661 reports came in while the outage lasted.

Reports reached outage level in 5 countries, the US, the Netherlands, the UK, Poland and more.

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

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

Started
12:06
Mon 16 Nov, Central European time
At outage level
19 h
Ended 07:06 on 17 Nov
Busiest 15 minutes
235
reports, at 21:52
Reports during the outage
5,661
Peak about 39× the usual level
Timeline

Reports from Mon 06:00 to Tue 09: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 Store rose to outage level at 12:06 Central European time on Monday 16 November 2026 and stayed there for 19 h. They peaked at 235 reports in 15 minutes at 21:52, about 39 times the usual level for that time of day, and 5,661 reports came in while the outage lasted. Reports reached outage level in 5 countries, the US, the Netherlands, the UK, Poland 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 16 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 USOutage5,364
The NetherlandsOutage1,366
The UKOutage805
PolandOutage579
BrazilOutage544
CanadaAbove usual328
GermanyNormal202
FranceNormal194
SpainNormal190
IndiaNormal177
ItalyNormal149
BelgiumNormal124
Same time

Other services with an outage at the same time

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

Check whether Microsoft Store 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 Store'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 Store outage on 16 November 2026: problem reports over time

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