4 ms·

But the stupid status page says it's still up.... this is like S3 all over again https://status.slack.com/ https://status.slack.com/

by tcarn 9y ago

empath75 9y ago
status page wasn't even responding for me.
mtrpcic 9y ago
I swear, most of these status pages could just be static HTML with how inaccurate they are during an actual outage.
- snoman 9y ago
  Most of the time these status pages sit on, and store data in, the same infrastructure as the things it's supposed to be reporting on.
  - softawre 9y ago
    Do they really? Amazon did that one time but that was stupid of them. Most software companies use an external service (like statuspage.io) to host their status page.
- tcarn 9y ago
  HN Could make a killing selling a saas product that monitors if sites are up. Honestly it's more reliable at this point.
  - snoman 9y ago
    Ostensibly, that already exists: https://www.statuspage.io/ https://www.statuspage.io/
  - corben 9y ago
    We've actually created just that. https://hund.io https://hund.io We're a status page provider with built-in monitoring so if a service goes down the page will be updated.
  - mbroshi 9y ago
    I believe OP's point was that aggregating crowd-sourced reporting of outages is surprisingly accurate and prompt, not that there aren't any other tools for reporting outages.
- rickyc091 9y ago
  Probably the case. I've seen the same thing with Heroku. I've report an issue, then half an hour later it gets updated. Could also be a bad cache that takes a while to invalidate.
- falcolas 9y ago
  In my experience, changing the status pages at many companies involves a C-level decision, since that status page change serves as an admission of service outages. And service outages can trigger availability clauses in contracts, costing the company significant amounts of money. The mental acrobatics to justify not changing the status are often astounding: "One customer can load a partial page from Timbuktu, so we're not down."
zucked 9y ago
I can't even get that to load now. But it's Smmooooootttthhh Sailing :sunglasses:
veb 9y ago
Update from Slack on Twitter: https://twitter.com/SlackHQ/status/950812653496053760 https://twitter.com/SlackHQ/status/950812653496053760
ben174 9y ago
They finally updated it @ 11:45 AM Pacific
mariojv 9y ago
It's been updated now. I think these kind of pages are usually updated manually by incident response teams.
madmod 9y ago
It's because someone couldn't Slack the ops team. XD
teilo 9y ago
Be fair. They had it updated within 5 minutes. I know, because I had just sent a message before it went down. Compare to Amazon... an hour, two?
- ben174 9y ago
  It was well over 20 minutes. Status pages should be automated and triggered via monitoring. Not a manual thing.

But the stupid status page says it's still up.... this is like S3 all over again https://status.slack.com/ https://status.slack.com/

by tcarn 9y ago

But the stupid status page says it's still up.... this is like S3 all over again https://status.slack.com/ https://status.slack.com/

empath75 9y ago

status page wasn't even responding for me.

mtrpcic 9y ago

I swear, most of these status pages could just be static HTML with how inaccurate they are during an actual outage.

snoman 9y ago
Most of the time these status pages sit on, and store data in, the same infrastructure as the things it's supposed to be reporting on.
- softawre 9y ago
  Do they really? Amazon did that one time but that was stupid of them. Most software companies use an external service (like statuspage.io) to host their status page.
tcarn 9y ago
HN Could make a killing selling a saas product that monitors if sites are up. Honestly it's more reliable at this point.
- snoman 9y ago
  Ostensibly, that already exists: https://www.statuspage.io/ https://www.statuspage.io/
- corben 9y ago
  We've actually created just that. https://hund.io https://hund.io We're a status page provider with built-in monitoring so if a service goes down the page will be updated.
- mbroshi 9y ago
  I believe OP's point was that aggregating crowd-sourced reporting of outages is surprisingly accurate and prompt, not that there aren't any other tools for reporting outages.
rickyc091 9y ago
Probably the case. I've seen the same thing with Heroku. I've report an issue, then half an hour later it gets updated. Could also be a bad cache that takes a while to invalidate.
falcolas 9y ago
In my experience, changing the status pages at many companies involves a C-level decision, since that status page change serves as an admission of service outages. And service outages can trigger availability clauses in contracts, costing the company significant amounts of money. The mental acrobatics to justify not changing the status are often astounding: "One customer can load a partial page from Timbuktu, so we're not down."

zucked 9y ago

I can't even get that to load now. But it's Smmooooootttthhh Sailing :sunglasses:

veb 9y ago

Update from Slack on Twitter: https://twitter.com/SlackHQ/status/950812653496053760 https://twitter.com/SlackHQ/status/950812653496053760

ben174 9y ago

They finally updated it @ 11:45 AM Pacific

mariojv 9y ago

It's been updated now. I think these kind of pages are usually updated manually by incident response teams.

madmod 9y ago

It's because someone couldn't Slack the ops team. XD

teilo 9y ago

Be fair. They had it updated within 5 minutes. I know, because I had just sent a message before it went down. Compare to Amazon... an hour, two?

ben174 9y ago
It was well over 20 minutes. Status pages should be automated and triggered via monitoring. Not a manual thing.