Hacker News Reader

Comment by MaxfordAndSons | Hacker News Reader

It's unbelievable that the status page is still showing green checkmarks, almost what, 2 hours into the outage?

edit: oh, it is actually because of the outage! So if they can't get a fresh read on the service status from s3, they just optimistically assume it's green... even though the service failing to provide said read... is one of the services they're optimistically showing as green XD

View on HN

Hey can't change it due to the S3 issue. See their twitter post: https://twitter.com/awscloud/status/836656664635846656

It seems status pages should be on entirely independent infrastructure, give the criticality of the information they provide. Perhaps even a separate domain.

Wow so they can't update the S3 status page currently due to S3 issues, including the status page processing to update it, which runs upon S3.

That raises many more questions about how well accounted outages have been in the past and equally reported. Then the design aspect that in itself highlights if you run things in the cloud, what fallback do you have if that goes wrong. So certainly the impact from this outage is going to echo for a while, with many questions being asked.

Smells BS. As pointed out in https://news.ycombinator.com/item?id=13757284, text should have reflected the real situation. So the icons are either not the only problem or just an excuse.

Same related flaw as Three Mile Island. Fail closed and measure the output, not the intent.

Reply on news.ycombinator.com