5 ms·
You don’t even know what the problem is yet. Stop shouting solutions.
by boopboopbadoop 5y ago
You don’t even know what the problem is yet. Stop shouting solutions.
- slig 5y agoThe problem is very clear: the status page is not working as it should.
- mark-r 5y agoGiven the legal liabilities Amazon has with their SLAs, it may be working exactly as Amazon thinks it should. Whether anybody would agree with that assessment should be obvious.
- boopboopbadoop 5y agoWhat if the problem is not an AWS problem? My point is that you don’t know what the problem is, you’re assuming.
- yunwal 5y agoThe problem is that AWS can't update their status page to reflect that there's a problem. This happens during every AWS incident without fail.
- hatware 5y agoStatus page looks like it was updated. Seems more like we have a lot of impatience on this board.
- twistedpair 5y ago"Can't" and "won't" are different things. See discussions from the last outage about the VP signoff needed to admit, I mean announce, an outage.
- boopboopbadoop 5y agoMy point is that you’re not even sure that it’s AWS’s problem. I heard that other providers might be affected, perhaps meaning it’s a network issue.
- OneLeggedCat 5y agoI kind of think everyone else here understands this very particular problem of a status page running on the same equipment that it's supposed to be monitoring if that equipment goes down, and for whatever reason, you don't.
- boopboopbadoop 5y agoI understand that. What I’m questioning is whether that is the problem here. Is it? Do you know? I heard it might be an internet provider issue, in which case the status page is not the problem here.