Hacker News Reader

Comment by bootloop | Hacker News Reader

If there is a SLA with consequences associated with it every status page is going to be a lie.

Well, it sucks to catch fire and I care for the employees and the firemen, but if their status page is a lie then I have a whole lot less sympathy for the business. That's shady business and they should feel bad.

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.

Is the status page relevant though? At the very least, OVH immediately made a status announcement on their support page and they've been active on Twitter. I don't see anything shady here. From their support page:

> 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?

> Is the status page relevant though?

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.

Still better than Amazon where their status page describes little and fat chance of anyone official sharing anything on social media either.

I wonder if a server fire would cause Amazon to go to status red. So far anything and everything has fallen under yellow.

To have a status page that reflects actual statuses? To know that I'm not being lied to or taken advantage of? To know that my SLA is being honored?

Reply on news.ycombinator.com