Microsoft outage blamed after 15 guests poisoned by chlorine at German hotel
A hotel safety system that warned staff by email reportedly went silent when Microsoft's services failed, and the guests paid for it.
By Mr Elite Published 7 min read
- Severity
- High
- Status
- Reported by outlets
- Sources
- 1
- Last checked
The short version
- Security Affairs reported on 15 November that 15 guests at a German theme park hotel were poisoned by chlorine, citing Notebookcheck and local media.
- The hotel's sauna-area safety system reportedly emailed operators when chlorine rose too high, and the emails could not go out during the Microsoft outage.
- German emergency services sent 40 first responders, local media reported; four victims went to hospital and one stayed for observation.
- The Microsoft outage ran from 12 to 14 November and affected Outlook and other services, Security Affairs said.
- The hotel's name, the exact date of the incident and Microsoft's own account have not been given.
What happened
Fifteen guests at a theme park hotel in Germany were poisoned by excessive chlorine during a Microsoft outage that ran from 12 to 14 November, Security Affairs reported on 15 November. The outlet was relaying a report from Notebookcheck, which in turn cited local media.
According to Security Affairs, the hotel had a maintenance safety system for its sauna area. If the chlorine level climbed too high, the system sent an email to the operators. When Microsoft's cloud services failed, those emails could not be sent, the chlorine kept rising, and guests were affected.
Notebookcheck said over a dozen guests were injured by excessive chlorine levels. Security Affairs uses the word poisoned and gives the figure of 15. Neither the hotel nor the authorities are quoted directly in the material available.
German emergency services sent 40 first responders, Security Affairs reported. Local media said four victims were taken to hospital and one stayed for further observation. Security Affairs also cited Tom's Hardware as saying the outcome could have been worse had the problem not been caught earlier.
The wider outage hit Outlook and other Microsoft services, according to Security Affairs. It said some Japanese workers went back to fax machines to keep businesses running, and that the disruption was smaller than the CrowdStrike failure of 2024.
Why it happened
The immediate cause, as Security Affairs and Notebookcheck describe it, was a dependency. The hotel's chlorine alert travelled by email, and email depended on Microsoft's cloud. When the cloud failed, the warning never reached anyone.
The sources differ slightly on what the email system did. Security Affairs describes it as an alert that told operators when chlorine was too high. The Notebookcheck quote describes an email-based system used to control chlorine dosing. It is not clear whether email carried only the warning or also took part in controlling the dosing.
Why the chlorine level rose in the first place has not been stated. Microsoft's explanation for the outage is also absent from the material, and Microsoft has not been quoted.
How this kind of failure works
Engineers call this a single point of failure: one component that, when it breaks, takes the whole function down with it. The chlorine monitor itself may have worked perfectly. If the only route from sensor to human is a service you do not control, the safety function is only as reliable as that service.
Picture a smoke alarm that does nothing except send a message to your phone. It works every day, so nobody questions it. On the day the mobile network is down, the smoke is real and the phone stays quiet. A siren in the hallway would not have this weakness.
Cloud services fail for many reasons, from faulty updates to network problems, and they fail for everyone using them at once. That is why a large provider's outage can reach a hotel sauna. The customer often does not know which of their systems quietly rely on that provider.
Security Affairs also points out that the fix has costs. Running servers and automation locally removes the cloud dependency, but it takes more work to build and maintain, and it does not protect against local problems such as power cuts.
Who is affected
The people directly affected were the 15 guests at the hotel, four of whom went to hospital according to local media. The hotel's name has not been published in the material available, so guests cannot yet check whether they were there.
Any organisation that routes safety alarms through email, chat or another cloud service is exposed to the same pattern. Examples in general terms include plant rooms, cold storage, pool treatment and server rooms. You can check your own exposure by tracing each alarm from sensor to person and noting every service it passes through.
The Microsoft outage itself was global and hit Outlook and other services from 12 to 14 November, Security Affairs said. The number of organisations affected has not been given.
How to defend against it
Tick each step as you check it. Your progress is saved on this device.
What to learn from this
The concept: Single point of failure in safety alerting
A single point of failure is any one thing whose loss stops a whole system. In alerting, the usual culprit is a shared service such as email, which feels dependable because it works every day.
The remedy is redundancy that is genuinely independent. Two alerts that both ride on the same provider count as one. The second path needs a different route, ideally one that works with no internet at all.
The same idea applies to backups stored in the same account as the original data, to staff who all rely on one chat app during an incident, and to door locks that need a cloud login.
A warning that depends on a service you do not control can fail at the moment you need it, so give it an independent second route.
Quick check
Sign in to earn 10 XP for a right answer
A factory sends its gas leak alarm by email and adds a second email to a different address on the same provider. Why is this weak?
Redundancy only helps when the paths are independent. Two emails through one provider share the same point of failure.
Timeline
- 12 November A global Microsoft outage begins, hitting Outlook and other services, according to Security Affairs.
- 12 to 14 November (exact time not given) At a theme park hotel in Germany, the email alert for high chlorine reportedly cannot be sent and 15 guests are poisoned.
- During the incident German emergency services send 40 first responders; local media report four people taken to hospital and one kept for observation.
- 14 November The Microsoft outage ends, per the dates Security Affairs gives.
- 15 November Security Affairs publishes its account, citing Notebookcheck and Tom's Hardware.
What is not known yet
- The name and location of the hotel, and the exact date and time of the incident.
- Whether email carried only the chlorine alert or also took part in controlling the dosing.
- Why the chlorine level rose in the first place.
- Microsoft's explanation for the outage and whether it has commented on the incident.
- The condition of the guests after treatment, beyond the four reported hospital admissions.
Questions people ask
Did a Microsoft outage really poison hotel guests in Germany?
That is what Security Affairs reported on 15 November, citing Notebookcheck and local media. The hotel's chlorine alert reportedly relied on email, which could not be sent during the outage. The hotel and Microsoft have not been quoted in the material available, so details remain unconfirmed.
How many people were hurt and how serious was it?
Security Affairs gives the figure of 15 guests poisoned. Local media reported that four were taken to hospital and one stayed for further observation. German emergency services sent 40 first responders.
When did the Microsoft outage happen?
Security Affairs said the global outage ran from 12 to 14 November and hit Outlook and other services. It described the disruption as smaller than the 2024 CrowdStrike failure. The exact time of the hotel incident has not been given.
How can safety systems be protected from cloud outages?
Security Affairs, quoting Notebookcheck, says such systems should have a physical or analog backup that works when everything else is offline. General good practice adds a second alert route that does not share a provider, and regular drills so staff know the manual steps.
Sources
- Security Affairs: The Microsoft Outage Left 15 Hotel Guests Poisoned by Chlorine