A German hotel's chlorine alarm reportedly went quiet during the November Microsoft outage, and 15 guests were poisoned by the gas.
According to Notebookcheck, the hotel's sauna area had a maintenance safety system that warned operators about high chlorine levels by sending emails. When Microsoft's cloud services went down, those messages could not be sent, and the levels kept climbing until people were hurt. Emergency services deployed 40 first responders. Local media reported that four victims went to the hospital, with one staying for further observation.
The outage ran from November 12 to 14 and hit Outlook and other Microsoft services. It also sent some Japanese workers back to their fax machines. The hotel's name, its location within Germany, and the precise technical cause of the gas release are not given in the material we have, so the link between the outage and the injuries rests on Notebookcheck's account.
The design lesson holds even with that caveat. An alarm that works by sending a message can fail silently, because no message looks exactly like no problem. Safety systems are usually built to fail loudly, with a local siren, a warning light, or an automatic shutoff that needs no network. The source's advice is similar: build a physical or analog backup, and make sure staff know it exists and how it works. Self-hosting the automation is another route, though a local power cut would still be a risk.
This was far smaller than the 2024 CrowdStrike failure, which disrupted a large number of corporate systems worldwide. It differs in kind, too. Most big cloud outages cost money and time, while this one allegedly cost people their health. It also shows how many businesses lean on a few providers such as Microsoft, Google, and AWS, which are cheap and reliable until they are not.
The open question is how many other building systems quietly route their alerts through a cloud mailbox, and whether anyone has tested what happens when it goes dark.