Connect with us

NEWS

Microsoft 365 Outage Left Hospitals and Courts Without Mail

Microsoft 365 dropped Exchange traffic 85% for nearly 18 hours, leaving hospitals, police, courts, and a hotel alarm without email.

Published

on

A Microsoft 365 outage that began around 12:30 p.m. EST on Thursday, November 12, cut Exchange Online traffic by about 85% for nearly 18 hours. Hospitals, police desks, courts, and a German hotel whose chlorine alarm sent only email had no second path.

Office teams that could pick up a phone had an odd, quiet afternoon. The people whose work only moves when Outlook moves did not.

Exchange Online Ran 85% Below Normal for Nearly 18 Hours

Ookla, which runs Downdetector, counted more than 7 million reports about Microsoft services by 16:00 UTC on November 13, about two and a half times the load from YouTube’s February 2026 outage, the next largest in the past 12 months. Reports stayed high for about 20 hours, roughly twice as long as other large outages in that window, and more than 90 countries or territories logged at least 1,000 reports.

Independent network data from Kentik put a harder number on the mail itself. Doug Madory, director of internet analysis at Kentik, tracked traffic to Exchange Online, the cloud service behind Outlook for business, at about 85% below expected levels from around 17:35 UTC on November 12. Recovery began at 11:20 UTC on November 13. By 13:25 UTC the same service was running about 19% above expected as queued mail and mailbox syncs landed.

HOW THE BLACKOUT WAS COUNTED

MeasureFigureWho measured it
User reports by 16:00 UTC, November 13More than 7 millionOokla / Downdetector
Time reports stayed highAbout 20 hoursOokla
Countries or territories with 1,000+ reportsMore than 90Ookla
Outlook peak on DowndetectorMore than 130,000 reportsDowndetector
Exchange traffic vs expectedAbout 85% below for nearly 18 hoursKentik
Exchange traffic after the queue drainedAbout 19% above expectedKentik

Microsoft 365 has more than 450 million paid commercial seats, the last headcount Microsoft published for the quarter ended December 31, 2025. That is the pool the outage sat in. GoDaddy, which resells Microsoft 365 mail to small firms, drew more than 60 times its usual outage reports. Zoom reports rose more than 50 times, and Gmail more than 40 times, as senders hit dead inboxes and looked for another way through.

Microsoft first said publicly at 17:54 UTC that it was investigating mailbox access in the Americas under incident EX1550543. Thirteen minutes later it warned that Microsoft 365 connectivity could fail in any region. A wider advisory, MO1550821, followed for the services that depend on Exchange Online, including Teams calendars, SharePoint Online, Microsoft 365 Copilot, Intune, Defender XDR, Planner, To Do, and Purview.

The People Who Could Not Take a Snow Day

On Friday, November 13, 15 guests at Hotel Ling Bao, the Phantasialand park hotel in Brühl, Germany, were treated after chlorine in the pool rose too far. Phantasialand said a defect in the automatic dosing system produced the extra chlorine, and that its maintenance safety system generated warning emails that did not arrive because Outlook was down. Matthias Stupp, a Brühl fire official, said responders assessed 15 people, 14 with minor injuries and one with a moderately serious injury. Four were taken to hospital. About 40 responders went to the site. The dosing fault put the chemical in the water. The mail outage hid the alarm.

That is the pattern that repeats when a safety or public-service workflow has only one mouth. Rachel Harrison, GMB national secretary for public services, said 111 and 999 staff in the UK could not refer patient details in the normal way, which was creating a backlog, while emergency call-outs appeared unaffected. NHS England said local services were using other systems or paper records so appointments could continue. The National Pharmacy Association warned of delays to some NHS prescriptions because NHS email was hit.

WHO LOST THE INBOX

  • UK police: Forces asked the public to call 101, because online crime reports were not landing.
  • Maine courts: The judicial branch warned that protection-order requests sent by email after 12:30 p.m. on Thursday might never have reached the courts.
  • New York City: The Department of Investigation suspended Friday evictions after systems tied to the outage failed.
  • Arapahoe County, Colorado: The sheriff’s office said jail staff were not getting the email notices needed to process online bond payments, so bonds had to be posted in person.
  • Japan and New Zealand: Japan’s Digital Agency could not receive email, and Immigration New Zealand paused visa processing.
  • Markets and ships: Euronext reported email trouble, and Maersk warned customers of delayed updates.

Staff in the US House of Representatives said work had stopped. Municipal offices in Austin, Jacksonville, and Baltimore said they relied on Microsoft for email, while emergency lines stayed up. Toronto’s St. Michael’s Hospital declared a code grey, the alert used when critical infrastructure fails. The Hospital for Sick Children told people trying to reach staff about an emergency to go to the nearest emergency department. Firms that still run Microsoft software on their own servers were somewhat spared. So were the EU’s own institutions, which reported almost no impact.

How UK Hospitals and Police Lost Their Inbox

The UK felt the outage as a public-service event because so much of the state already routes mail and identity through the same cloud tenant. Computer Weekly’s public DNS mapping, run across NHS trusts, police forces, councils, and central government from August to November 2026, found Microsoft as the default in every sector.

UK PUBLIC-SECTOR MAIL ON MICROSOFT 365

SectorMicrosoft 365 shareHyperscaler share
Police forces46 of 48 (95.8%) route email through Microsoft 36547 of 48 (97.9%) connect to at least one US hyperscaler
NHS trusts132 of 213 (62%) route email and identity through Microsoft 365165 of 213 (77%) connect to a hyperscaler
Councils338 of 382 lean primarily on MicrosoftMicrosoft holds 13,473 of 19,407 hyperscaler DNS records

Downing Street, the Department for Transport, the Ministry of Justice, and the Department for Energy Security and Net Zero were among the Whitehall offices hampered. UK Parliament told constituents with urgent issues to call. Some court judgments due Friday were lined up for delay into Monday. National Rail, Chiltern Railways, and Great Western Railway warned that tickets sent by email might not arrive.

Baroness Lloyd of Effra, the UK cyber minister, said the issue mainly hit back-office functions, with limited reports of impact on frontline delivery, and called it inconvenient and disruptive. Nicky Stewart, senior advisor to the Open Cloud Coalition, said over-reliance on a single provider leaves businesses and public services open to disruption and creates wider economic risk. The UK Treasury had already built new safeguards for major technology providers in July 2026, after EU financial regulators in November 2025 put Microsoft on the list of designated critical providers to banks and insurers. The designation did not give hospitals a second inbox on Friday morning.

Why the First Fixes Would Not Stick

Microsoft first blamed elevated load, then reversed itself. The load, it said, was not from more traffic. Servers had dropped out, and the machines still standing were carrying their mailboxes plus everyone else’s.

We determined the elevated load isn’t driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure.

Microsoft 365 Status, on X

Failed automated health checks pulled servers out of rotation. Microsoft said a process that sets up secure connections was becoming overwhelmed, so those servers stopped handling requests. Engineers paused all deployments, redistributed traffic, restarted machines, and tried an alternative health-check method. Servers that looked healthy while idle went unresponsive again once traffic returned. Kentik’s connection data showed why. Devices opened up to 70% more connections to Exchange than expected, while connections carrying responses from Microsoft fell to about 27% of normal. Cloudflare Radar saw Exchange requests triple as clients retried, and about one in three requests to Entra ID, the sign-in service, failed.

FROM FIRST ALERT TO A WORKING QUEUE

  1. November 12, 2026, 12:30 p.m. EST: Outage reports surge as Outlook fails across the Americas.
  2. 17:54 UTC: Microsoft opens EX1550543 for mailbox access in the Americas.
  3. 18:07 UTC: The warning widens to Microsoft 365 connectivity in any region.
  4. Overnight into November 13: Servers return to service, then fail again under retry load; an authentication and routing patch is applied.
  5. November 13, 11:20 UTC: Kentik sees Exchange traffic recovering; by 13:25 UTC it runs about 19% above expected as queued mail lands.
  6. November 14, 2026: Microsoft says it has restored service to remaining customers and regions.

Microsoft extended its email delivery timeout to 48 hours so delayed messages would not be dropped while the queue drained. That is also why inboxes did not come back empty. They came back loud. This failure sat inside Exchange Online, Microsoft’s hosted mail, not on the Azure status page, which showed no active events. It is a different class of fault from the October 2025 Azure Front Door post-incident review, when an edge-network bug took Microsoft 365 down with it.

Phishing Wore the Real Incident Number

On November 13, while queues were still catching up, Microsoft detected phishing mail that impersonated Microsoft 365 service-health notices and cited the genuine Exchange Online incident EX1550543. Some messages claimed held mail would be deleted within 24 hours unless the recipient clicked to restore it. That deletion threat was false. Microsoft Threat Intelligence disclosed the campaign on November 14 and said similar messages targeted organizations across multiple US sectors. The activity matched credential phishing, though credential collection and malware delivery were not confirmed.

HOW THE FAKE NOTICES LOOKED

  • Subject line: Outage, then a six-character code.
  • Display name: An organization-specific prefix plus Outage Notification or Service Health.
  • Sender domains: moments-notice.com, planetmaison.com, and newbooker.com.
  • Click path: SendGrid tracking links that redirected to reallifeaccounting.com, including /themelist0.html.

A real incident number does not make an email real. The practical check is the Microsoft 365 admin center, or the public page at status.cloud.microsoft, not a restore button in the message. In the thread under its warning, Microsoft Threat Intelligence said Defender blocks the campaign’s domains and that Defender for Office 365 quarantines the mail. Those same Defender tools were on the degraded-services list during the outage. The second blow arrived while the first one was still being cleared.

Customers who could change their mail-exchange records, and point the same domain at another host, got a path around Exchange Online. Most public bodies could not do that in an afternoon, because identity, calendars, and records sat in the same tenant as the dead mailbox.

Microsoft’s Network Upgrade Left a Fault Behind

On November 13 Microsoft said it was deeply sorry, called the event a technical issue not related to cyber activity or AI agents, and traced it to an issue introduced during an earlier network capacity upgrade that surfaced after a recent network change. It restored traffic in stages, checking stability at each step, which it said took longer and kept the service from falling over again.

We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously.

Microsoft, on X, November 13, 2026

On Saturday, November 14, Microsoft 365 Status said the company had completed work on the underlying issue and restored service to remaining customers and regions. It promised a full post-incident report once the review is complete. That report has not been posted.

The paper will matter for engineers. It will not rewrite Friday in Brühl, or the protection orders that may never have reached a court in Maine, or the 111 referrals that sat in a queue because the only channel was Outlook. Microsoft has promised a full post-incident report once its review is complete. The warning mail from the pool alarm never did arrive.

Harry is the editor of NEWS ANALYSIS. He writes across the publication's ten desks, with most of his time going to the stories where a number, a filing or a study decides the argument. His working rule is simple: read the source document before writing about it, and tell the reader plainly which parts are established and which are somebody's claim. He is responsible for the standards set out on this site's Editorial Standards and Fact Checking pages, and for correcting the record openly when the publication gets something wrong.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending