Affiliate links on Android Authority may earn us a commission. Learn more.
Last week's Microsoft Outlook outage turned a hotel pool fault into a hospital trip for 15 guests
Nov 16, 2026 — 7:02 AM ET

- Fifteen guests at a hotel in Germany were reportedly hurt after a faulty dosing system pumped too much chlorine into the hotel pool.
- The pool’s safety system sent a warning by email, but staff never received it because of last week’s global Microsoft 365 outage.
- Microsoft says the outage was caused by a problem from an earlier network capacity upgrade, and it has promised a full post-incident report.
Last week’s Microsoft 365 outage did more than keep people out of their inboxes. In Germany it played a part in a chemical incident that sent hotel guests to the hospital.
German public broadcaster WDR reported that on Friday, November 13, a fault in the automatic chlorine dosing system at Hotel Ling Bao pushed far too much chlorine into the hotel’s pool. The hotel belongs to the Phantasialand theme park in Brühl, near Cologne.
Its maintenance safety system detected the problem and sent an alarm, but the alarm went out by email. Because Microsoft’s Outlook and Exchange Online services were down at the time, the message never reached staff. Nobody knew anything was wrong until guests in the pool area started having trouble breathing.
Around 40 emergency responders were reportedly sent to the hotel. Fifteen people needed triage, most of them for irritation of the airways. Four were taken to the hospital, down from an initially reported five, and one person stayed in for observation. Firefighters closed the pool and tested the water. The water was then replaced, and the pool was later cleared to reopen. Phantasialand told WDR that the Outlook outage was why the chlorine warning emails never arrived.
The outage hit far more than email
The outage began on Thursday, November 12, with users in every region losing access to their Exchange Online mailboxes. The failure also broke features that depend on email in Teams, Copilot, Defender, Purview, Planner, Intune, and other Microsoft 365 services. Downdetector logged more than 100,000 reports within an hour of Microsoft acknowledging the problem. ABC News later put the global total at more than 7.4 million reports.
Here are some of the other real-world disruptions reported while the outage lasted:
- Healthcare: The GMB union said NHS staff taking emergency calls in the UK couldn’t pass on patient details the usual way, which built up a large backlog.
- Courts: At Manchester’s Minshull Street Crown Court, some juries were sent home early and some prisoners weren’t brought to court. CNN reported that courts in the Philippines were also held up.
- Government: Immigration New Zealand stopped processing all visa applications. In Australia, the Australian Federal Police and ASIO were affected, and Service NSW had widespread problems. Some government staff in Japan switched to paper copies and text messages. New York City Emergency Management warned residents about delayed emails and online services and told them to call 311 or 911 instead.
- Schools: Some Australian schools couldn’t run online classes and texted parents to phone in absences.
- Transport: Germany’s Deutsche Bahn reported significant delays to its internal communications. VIA Rail Canada warned passengers that they might not get trip emails, and Britain’s National Rail had problems with ticket emails. In India, IndiGo and Akasa Air said their email support was affected.
- Business: Workhorse Group postponed its Q3 earnings release, Maersk warned customers that updates could be delayed, and bank workers in Hong Kong were disrupted.
What Microsoft has said
On Thursday night, Microsoft EVP Charles Lamanna said the company regretted the disruption. On Friday, Microsoft apologized and named a preliminary cause. It said the incident “was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change.” The company also described it as a technical issue unrelated to “cyber or AI / agents” and said it was “deeply sorry” for the disruption.
The company’s most recent update came on Saturday, November 14, in a post from its Microsoft 365 Status account on X. In it, Microsoft said it had “completed our efforts to address the underlying issue of the incident” and “restored service to the remaining impacted customers and regions.” The company has said it will publish a full post-incident report once its review is complete.
Conversation
Read what readers said or add your take.