Microsoft 365 Outage Statistics 2026 | Global Disruption, Services Affected, Countries, Downtime & Key Facts

The Microsoft 365 outage started on November 12, 2026 at 16:17 UTC, disrupted 10 services including Exchange Online, Teams and Copilot, and produced a peak of about 130,000 Downdetector reports, with reports from 74 countries and territories inside roughly one hour. Recovery ran into November 13, 2026, and Microsoft said it had no indication of malicious activity.

Microsoft 365 Outage 2026 – Introduction

The Microsoft 365 outage of November 2026 hit email, chat, file sharing and security tools at the same moment. Office workers in the US lost Outlook access around 11:17 AM ET. Within about an hour, people in 74 countries and territories were filing problem reports. Government agencies, businesses and public services across North America, Europe and Asia-Pacific reported trouble. Many staff could not send a message, join a meeting or open a shared file, so work slowed or stopped in whole departments. Recovery then stretched into a second day. Microsoft’s service health page tracked the incident, and news outlets and Downdetector filled in the public picture.

This report collects the confirmed numbers in one place. It covers the services affected, the regions involved, the timeline, the business and consumer split, and the cause. It also flags what nobody has verified yet. No public figure exists for total affected users, businesses or financial losses, and the 130,000 number counts outage reports, not people.

Microsoft 365 Outage 2026 Interesting Facts

Peak Downdetector reports (reported figures)
Reuters-cited peak     | ████████████████████ 130,000+
Early-afternoon count  | ██████████████████░░ 120,000+

Source: Microsoft 365 Service Health incident record; Reuters; Downdetector by Ookla.

Every row comes from Microsoft’s own incident record or from outlets citing Downdetector. The 16:17 UTC start equals 11:17 AM ET, so most US offices felt the Microsoft 365 outage before lunch. East Coast staff were mid-morning into their workday, and West Coast staff had barely logged on. That timing made the disruption hard to miss for US business users. The 10-service count matches the services Microsoft and the press named as disrupted.

The 130,000 figure needs care. Downdetector counts submitted reports, and one person can file several. Another tally put the early-afternoon count at more than 120,000, so the two numbers sit close together. Treat them as a measure of attention, not a headcount. The recovery period of 2 days also matters. It shows the fix did not land in one step, and that teams should plan for outages that outlast a single workday.

Which Microsoft 365 Services Were Affected by the Outage in 2026?

Services by reported disruption type
Access problems      | ████████ 4
Connectivity         | ████     2
Security/compliance  | ████     2
Mailbox and email    | ██       1
Service disruption   | ██       1

Source: Microsoft 365 Service Health; Reuters; SecurityWeek.

Exchange Online sits at the center. It powers Outlook mailboxes and mail delivery, and Teams calendars lean on it too. When Exchange Online failed, the Microsoft 365 outage spread outward. Teams and Planner showed connectivity problems. SharePoint Online, To Do, OneDrive and OneNote showed access problems, which makes 4 services in that group. The pattern shows one shared dependency feeding many tools. Users saw different error messages, but the trigger sat in the same place.

Two services carry a different risk. Defender XDR lost some security features, and Purview lost multiple compliance and data-protection functions. Copilot suffered a plain service disruption. Status pages also listed Intune, Windows 365, cloud printing and device management, which pushed the wider count past a dozen. Security teams care most about those last three, because a blind spot in monitoring or compliance can outlast the email problem itself. Admins should review logs for the gap after any Microsoft 365 outage of this size, and confirm that alerts and retention rules ran as expected.

Which Countries Reported the Microsoft 365 Outage in 2026?

Reach of the Microsoft 365 outage
Countries/territories | ██████████████████████ 74
Regions named         | ███ 3
National examples     | ██ 2 (US, Australia)

Source: Downdetector by Ookla; Reuters; CNN.

The 74 figure counts places where Downdetector received at least one report. It does not mean every country lost service. It does show how fast the problem traveled: about 1 hour from the first spike to a near-global footprint. Microsoft runs shared cloud infrastructure, so a fault in one layer reaches many regions at once. Local data center health matters less when the failing layer is shared.

The three regions named are North America, Europe and Asia-Pacific. US users filed the first large wave, then Australia reported disruption to businesses, schools and government services. No verified country-by-country ranking exists yet. Any table that claims one is guessing. For a US audience, the key point is simple: the US was an early and heavy source of reports, and the problem did not stay local. Microsoft 365 serves millions of paying organizations, so a regional fault can quickly become a global story.

Microsoft 365 Outage Downdetector Reports in 2026: What the Numbers Show

Downdetector milestones (UTC)
Start of Outlook climb  | █ 17:25
Rate at 19:38           | ███████████ 11,000+ reports per minute

Source: Downdetector by Ookla; Reuters.

Reports began rising at 17:25 UTC, 68 minutes after Microsoft’s 16:17 UTC incident start. That gap shows how long users tolerated slow mail before complaining. By 19:38 UTC, the rate still topped 11,000 reports every minute, which means the Microsoft 365 outage was far from over at that point. That is about 183 reports every second. A rate that high, more than 3 hours after the incident began, points to a problem that was still spreading or still unresolved.

No hour-by-hour history is public yet, so this table lists only the checkpoints that Downdetector and Reuters released. The 130,000 peak and the 120,000+ early-afternoon count do not conflict. They describe different moments. By about 6:05 PM ET, reports had fallen to more than 40,000, a sign that recovery was starting. Neither equals unique affected users. Reports also depend on how many people know about Downdetector and choose to use it, which skews toward heavy US and UK traffic. Expect the final tallies to vary by source.

Microsoft 365 Outage Timeline From November 12, 2026 to Recovery

Minutes after incident start (16:17 UTC)
Incident start      | ░ 0
Reports rising      | ███████ 68
Peak report rate    | ████████████████████ 201

Source: Microsoft 365 Service Health incident record; Downdetector by Ookla; Reuters.

The chart measures elapsed time. Reports climbed 68 minutes after the start and were still heavy 201 minutes in. That is 3 hours and 21 minutes of sustained user pain on day one alone. Microsoft began returning servers to service that evening and said they held stable. That staged approach lets engineers confirm each batch before adding load.

Overnight, Microsoft said one attempt to improve serviceability was not working as expected, and partial recovery did not hold. By morning on November 13, updates described phased recovery: broader gains in North America, sustained gains across much of Europe and early signs in Asia-Pacific. Microsoft said email backlogs were close to cleared. Users may still see some delayed messages as queues drain now. The disruption spans 2 days. Any exact total downtime figure would be an estimate, since service returned in stages and not all at once. Individual tenants may have recovered at different times, so your own admin center is the best guide to your downtime.

Microsoft 365 Outage Business vs Consumer Impact in 2026

Services by audience
Business and enterprise | ████████████████ 8
Consumer-reported       | ████ 2

Source: Microsoft 365 Service Health; Reuters.

Eight of the 10 services serve mainly business and enterprise users. Those teams depend on shared mailboxes, meetings and compliance tools, so one failure stalls whole departments. The Microsoft 365 outage hurt most where work flows through email and Teams. Copilot users lost AI features, and Defender and Purview customers lost parts of their security and compliance stack.

Consumers felt it too. OneDrive and OneNote users reported access problems, which accounts for 2 services. Outlook straddles both groups. Microsoft has not released user counts by segment, so the 8 to 2 split measures services, not people. Business impact is larger in practice, because one enterprise tenant can hold thousands of staff.

Government Agencies and Businesses Hit by the Microsoft 365 Outage in 2026

Verified named examples
Business with date shift | █ 1 (Workhorse Group)
Sector-level reports     | ███ 3 (government, schools, public services)

Source: CNN; The Guardian; Reuters; company disclosures.

Workhorse Group gives the clearest named case. The electric truck maker moved its third-quarter results announcement by 4 days, citing business disruption from the Microsoft 365 outage. A public company delaying earnings is a hard, documented cost. It also shows the outage reached finance and investor communications, not only inboxes.

The other rows are sector-level reports, not audited cases. Government agencies, schools and public services saw trouble, but few have named the exact systems or hours lost. Expect more named disclosures in coming filings. Quarterly reports and incident notices often reveal costs weeks later. Until then, treat sector-level claims as directional.

Microsoft 365 Outage vs 2024 CrowdStrike Incident: 2026 Comparison

Verified direct loss estimates (USD billions)
CrowdStrike 2024 | ██████████████████████ 5.4
Microsoft 365    | ░ not yet verified

Source: Microsoft; Parametrix Insurance; Downdetector by Ookla.

The 2024 numbers are an estimate set. Microsoft put the CrowdStrike impact at 8.5 million Windows devices, and Parametrix estimated $5.4 billion in direct losses for Fortune 500 companies. The 2026 Microsoft 365 outage has no equivalent figures yet.

The two events differ in kind. CrowdStrike broke endpoints through a bad update. This outage hit cloud services from the inside. Comparing size today would mislead readers, so wait for verified user and loss data before ranking them. Both events prove one point: a single failure inside a widely used platform can disrupt work across the globe.

Microsoft 365 Outage Cause and Recovery Measures in 2026

Findings status
Failure symptoms identified | ███ 3
Malicious indicators        | ░ 0
Confirmed root cause        | ░ 0

Source: Microsoft 365 Service Health incident record; SecurityWeek.

Microsoft named 3 failure symptoms: health-check failures, overloaded core processes and infrastructure stability problems. Together they describe servers that could not prove they were healthy and then buckled under load. That explains why recovery came in stages as servers returned one group at a time. Health checks decide whether a server may take traffic, so repeated failures can drag the whole pool down. Engineers call this a cascading failure. One group of struggling servers pushes work onto the rest, which then struggle as well, and the cycle repeats until someone breaks it.

The chart shows 0 confirmed root causes. Microsoft said the precise cause remained under investigation and that it had no evidence of malicious activity. One report links the outage to Azure network configuration changes, but Microsoft has not confirmed that. Traffic optimization and an automated restart process improved stability by November 13, 2026. A post-incident review should answer why the faults spread across so many regions. It should also explain why overloaded core processes were not contained sooner. US admins should watch Microsoft’s post-incident report for the final cause and the fixes promised.

Microsoft 365 Outage 2026 FAQ

Is the Microsoft 365 outage still happening?

Recovery was progressing on November 13, 2026. Microsoft reported phased restoration and improving stability. Check the Microsoft 365 Service Health page for your tenant.

When did the Microsoft 365 outage start?

Microsoft’s Exchange Online record shows a start of 16:17 UTC on November 12, 2026, which is 11:17 AM ET.

What caused the Microsoft 365 outage?

Microsoft cited server health-check failures, overloaded core processes and infrastructure stability problems. The precise root cause was still under investigation.

Was the Microsoft 365 outage a cyberattack?

No. Microsoft said it had no indication that malicious activity caused the incident.

Which Microsoft 365 services went down?

Outlook and Exchange Online, Teams, SharePoint Online, Copilot, Defender XDR, Planner, To Do, Purview, OneDrive and OneNote.

How many people were affected by the Microsoft 365 outage?

Nobody knows yet. Downdetector logged about 130,000 reports at the peak, but reports are not unique users.

How many countries had a Microsoft 365 outage?

Downdetector received reports from 74 countries and territories within about 1 hour.

How long did the Microsoft 365 outage last?

It lasted 2 days, running into November 13, 2026. Service returned in stages, so your own experience may differ from the headline figure.

Why was Outlook down during the Microsoft 365 outage?

Outlook relies on Exchange Online, which carried the failing incident. Mailbox access and email delivery both suffered.

How can businesses prepare for the next Microsoft 365 outage?

Set up a backup communication channel, keep a status-page subscription, and write an outage playbook for email and meetings. Test it twice a year. Name an owner for each step, and list the phone numbers staff will need when email is down.

Did the Microsoft 365 outage affect Copilot?

Yes. Microsoft listed Microsoft 365 Copilot among the affected services, and users reported a service disruption. Copilot features that depend on Exchange Online and SharePoint data may have failed with them.

Where can I check Microsoft 365 outage status?

Use the Microsoft 365 Service Health page and the admin center. Downdetector shows user-submitted reports, which helps confirm whether the problem is widespread or limited to your account.

What should I do during a Microsoft 365 outage?

Do not keep retrying logins. Switch to your backup channel, tell staff what you know, and watch the service health page. Save any urgent drafts locally until mail returns.

Will Microsoft give refunds or credits for the Microsoft 365 outage?

Some business customers may qualify for service credits under their agreement. Terms vary by contract, so review your service level agreement and ask your account team. Microsoft has not announced a blanket credit.

Is the Microsoft 365 outage fixed?

Recovery was well advanced on November 13, 2026. Microsoft reported phased restoration, with email backlogs close to cleared, but some users may see intermittent issues. Check the service health page for the latest status.

Disclaimer: This research report is compiled from publicly available sources. While reasonable efforts have been made to ensure accuracy, no representation or warranty, express or implied, is given as to the completeness or reliability of the information. We accept no liability for any errors, omissions, losses, or damages of any kind arising from the use of this report.