zlacker

Pretty much every company has been shown to have fake status pages at this point.

>>Shekel+(OP)
Pretty much. They want the burden of proof for SLAs to fall on the customer, not on themselves. If a customer has to prove that an outage specifically affected them, they are much less likely to have a successful case against the failure to meet their SLA.

(Not directed at GitHub specifically, but at bogus status pages.)

>>Shekel+(OP)
fake and not automated are pretty different

>>Shekel+(OP)
From my experience, GitHub is the best out there when it comes to updating their status page.

>>Shekel+(OP)
Really? Why?

That's so disappointing.

>>Shekel+(OP)
Status pages are updated by humans and the humans need to (1) realize there's a problem and (2) understand the magnitude of the problem and (3) put that on the status page.

It's not fake, it's just a human process. And automating this would be error prone just the same.

>>AYBABT+C4
Very good points. Meanwhile I have clients asking me why they can't have a status page to which I reply: you can, but ultimately to be completely fail proof it will be a human updating it slowly. To which they reply: but GitHub or X does it...

Very infuriating, that.

>>Night_+P3
Two technical reasons capstoned by driving business motivation:

-False positives -Short outages that last a minute or three

Ultimately, SLA's and uptime guarantees. That way, a business can't automatically tally every minute of publicly admitted downtime against the 99.99999% uptime guarantee, and the onus to prove a breach of contract is on the customer

>>Macuyi+B5
There's some nice tooling these days for this. E.g. https://firehydrant.com/ and https://incident.io both make this a faster, more embedded process.

>>AYBABT+C4
I wouldn't necessarily call them fake, but the issue often has to be big enough for most companies to admit to it. AWS often has smaller outages that they will never acknowledge.

>>AYBABT+k7
Hey, incident.io CEO here! Thanks for mentioning us.

>>AYBABT+C4
Also (2b) convince their boss that the “optics” are better to update sooner than later.

>>AYBABT+k7
And Jeli.io for this! With the Statuspage integration, you can set the status, impact, write a message for customers, and select impacted components all without leaving Slack. Statuspage gets updated with a click of a button.