Re:Microsoft 365 outage leads to chlorine gas poisoning of 1...
by luxuryballs on Sunday November 15, 2026 @03:47PM
(#50510564)
They should have closed the pool.
Re:Microsoft 365 outage leads to chlorine gas poisoning of 1...
by cwillu on Sunday November 15, 2026 @03:50PM
(#50510595)
Email as the sole notification source for a safety critical situation is criminal, in the literal “the responsible engineer or coder masquerading as an engineer should be in jail” sense of the term.
Re:Microsoft 365 outage leads to chlorine gas poisoning of 1...
by ThrowawayTestr on Sunday November 15, 2026 @03:55PM
(#50510643)
More people need to get arrested for shitty engineering
Re:Microsoft 365 outage leads to chlorine gas poisoning of 1...
by tgv on Sunday November 15, 2026 @03:55PM
(#50510639)
We all know that services can fail, and consequently will fail at some moment. It is therefore primarily the responsibility of the designers of this system.
Re:Microsoft 365 outage leads to chlorine gas poisoning of 1...
by trollbridge on Sunday November 15, 2026 @05:59PM
(#50511803)
Because Office 365 is specifically marketed and contracted to customers as something not to be relied upon for critical real time controls when life or death matter.
Microsoft has many other offerings for such things, ranging from some services inside Azure to software (like operating systems) intended for real-time use on on-premises hardware.
Why does it matter that the service someone is paying for is an api or something else versus email? The email service failed. First and foremost Microsoft’s service failed. It doesn’t matter HOW it should be engineered.