News for hackers. Stuff that matters.
Re:Microsoft 365 outage leads to chlorine gas poisoning of 1... by buran77 on Sunday November 15, 2026 @02:51PM (#50510060)
> It's the fault of the company that designed the automatic alarm. Not the hotel.

The hotel picked a monitoring solution which relies exclusively on email, or configured it like that. If anything they are absolutely both to blame but for different things. The company for designing a safety related system like this, the hotel for selecting an inadequate solution/configuration thus allowing their guests to be harmed.

> But it is accurate to say that the cause of the issue was the outage

The cause of the issue is the more immediate one - the configuration of the monitoring system. This avoids going up the causality chain to far - shitty coffee caused engineer to take down email system, and such.

Re:Microsoft 365 outage leads to chlorine gas poisoning of 1... by zardo on Sunday November 15, 2026 @02:57PM (#50510107)
Email going down is the proximate cause. A system configuration relying on a single unreliable communications route is further up the causal chain.
Re:Microsoft 365 outage leads to chlorine gas poisoning of 1... by buran77 on Sunday November 15, 2026 @05:56PM (#50511778)
Let's not forget that we're talking about people getting hurt in a hotel which has a responsibility towards their guests, that's the core topic here, yes? The most reasonable proximal cause for the people getting hurt is that there was too much chlorine in the water. Because the monitoring system didn't work properly. Because the email failed. Because someone deployed a wrong config on MS's cloud infra. And so on.

As I said, there's plenty of blame to go around as a matter of general principle. But for what happened here the hotel bears the responsibility towards their guests, not the monitoring system developers, not Microsoft.