News for hackers. Stuff that matters.
Re:AWS status updates not working due to S3 by joshuak on Tuesday February 28, 2017 @03:00PM (#13757292)
So now you know that a deadman switch is the better way to report availability. The logic was backwards for this signal. The default condition is failed. Not failed requires proof.

It's interesting how easy it is to accidentally invert logical operations. I see it in code all the time. A condition will test that A is true when what they really need to know is if B and C are both false. It's like some kind of cognitive tick.

Re:AWS status updates not working due to S3 by ryanbrunner on Tuesday February 28, 2017 @03:57PM (#13757745)
That's good practice, sure, but their problem was even more fundamental than that. Their status page was dependent on the service it was reporting on being up. That fails the most basic requirement of a status page.