zlacker

>>mikebo+(OP)
So down right now...I wonder why they still use https://www.githubstatus.com/ that reports everything is alright when it's not!

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

>>Shekel+S2
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+u7
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.

>>Macuyi+t8
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+ca
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.