Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You don’t even know what the problem is yet. Stop shouting solutions.


The 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.


"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.


My 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.


Status page looks like it was updated. Seems more like we have a lot of impatience on this board.


The problem is very clear: the status page is not working as it should.


Given 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.


What if the problem is not an AWS problem? My point is that you don’t know what the problem is, you’re assuming.


I 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.


I 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.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: