At best you might be missing out on some SLA refunds, but at worst it could be disasterous for a business. I've been on the wrong side of a update-by-hand status system from a hosting provider before and it wasn't fun.
Agreed, though. A fake status page is worse than no status page. I don't mind if the status page states that it's manually updated every few hours as long as it's honest. But don't make it look like it's automated when it's not.
> Unable to display this content to due missing consent. By law, we are required to ask your consent to show the content that is normally displayed here.
I've usually seen this with embedded videos rather than comments.
My gut says yes.
https://news.ycombinator.com/item?id=15661218
They are not the only ones though. All too common. Well, it's tricky to set this up properly. The only proper way would be to use external infra for the status page.
So nobody chooses to make an honest status page.
But, they're usually manual affairs because sometimes the system is broken even when the healthcheck looks ok, and sometimes writing the healthcheck is tricky, and always you want the status page disconnected from the rest of the system as much as possible.
It is a challenge to get 'update the status page' into the runbook. Especially for runbooks you don't review often (like the one for the building is on fire, probably).
Luckily my status page was not quite public; we could show a note when people were trying to write a customer service email in the app; if you forget to update that, you get more email, but nobody posts the system is down and the status page says everything is ok.
I can appreciate an honest mistake though, like the status page server cron is hosted in the same cluster that caught fire and hence it burnt down and can't update the page anymore.
> The whole site has been isolated, which impacts all our services on SBG1, SBG2, SBG3 and SBG4. If your production is in Strasbourg, we recommend to activate your Disaster Recovery Plan
What more could you want?
What's the point of a status page then if it does not show you the status? I don't want to be chasing down twitter handles and support pages during an outage.
I wonder if a server fire would cause Amazon to go to status red. So far anything and everything has fallen under yellow.
No traffic whatsoever between sbg-g1 and sbg-g2 ant their peers.
I think this is probably linked to a manual reporting system and they got bigger fish to fry at the moment than updating this status page.
If they don't have any servers anymore, how can they be down ;)
Probably the best they could do at the moment.