The Jerusalem PostBlast from the past: Century-old British missile fragment found near resilience farm in BinyaminDaily MaverickTRANSNATIONAL TRAFFICKING: Tik hidden in bran flakes from SA seized in Nigeria after cartels alertZDF heuteAktuelle Pressemitteilungen des ZDFStraits Times SportTon-up Ackerman sees chance for S.Africa to pass Bangladesh's first innings 400kickerNeuzugänge Ezeh und Raschl fehlen Dresden in den kommenden WochenHipertextualGoogle enciende las alarmas: la IA podría lanzar ciberataques sin ayuda humanaSRF NewsQ&A Fragen und Antworten – Chat zum Thema «Reflux und Sodbrennen»OnetDo kiedy policja zostanie przed TK? Marcin Kierwiński zapowiadaBillboardC. Tangana & Spanish Rap Collective Agorazein Move Madrid 10 Years Later With Its Return: ‘This Is Our Legacy’n-tvBlitz-Verabschiedung in Berlin: "Ein Held": Für Antonio Rüdiger schließt sich ein KreisABC News (Australia)Arrest over Melbourne Cup theft but trophies still missingFootball ItaliaLazio give injury updates for Frattesi, Zaccagni and Nuno Tavares
The Daily Newsstand · Free, Always
Monday, November 16, 2026

15 hotel guests were injured by chlorine poisoning due to Microsoft’s global email outage

Translate

Emma Roth

is a news writer who covers the streaming wars, consumer tech, crypto, social media, and much more. Previously, she was a writer and editor at MUO.

Microsoft’s worldwide 365 and Outlook outage had real-world consequences after it cut off email alerts for a German hotel’s pool safety system. The German outlet Westdeutscher Rundfunk (WDR) said several people were injured at a Phantasialand hotel on Friday after its email system failed to deliver a safety alert about elevated chlorine levels in the pool, as spotted earlier by NotebookCheck and TechRadar.

A machine-translated Facebook post from a German fire department said it responded to a Phantasialand hotel after a “technical malfunction” caused an excessive amount of chlorine to enter a swimming pool, resulting in chlorine gas leaking into the surrounding area. As reported by WDR, 15 people were affected by the incident, including four who were transported to the hospital.

Microsoft has since published a post-incident report about the outage, and EVP Charles Lamanna posted an abridged version last night on X. The company says three factors contributed significantly to the incident, including a bug introduced in a previous update in July. This, coupled with a surge in load following an earlier Teams outage and an “unrelated issue” from the previous day that knocked out nearly 14 percent of its server capacity, activated the conditions for the “latent” bug in the July update to rear its head, which “caused requests to build up until servers ultimately stopped responding” during the peak traffic window in the US on Thursday.

The outage lasted from Thursday afternoon and well into Friday morning for many businesses on the East Coast, before Microsoft said service was fully restored on Sunday. “Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again,” Microsoft says. “Our normally automated recovery processes were not designed to restore service from this broad unresponsive state.” Microsoft adds that it couldn’t “quickly revert the change” because the defect was a latent bug from several months ago.

Follow topics and authors from this story to see more like this in your personalized homepage feed and to receive email updates.

View the original on The Verge →

KioskNews shows a cleaned-up reading view extracted from the publisher’s page — the original always lives on their site, not ours.