Live data from Hacker News

Slack issues

status.slack.com

31–40 of 67 posts

Re: Slack issues

#31

There was definitely a 20 minute window where it was down for us. Messages were occasionally getting through but often in the wrong order, and many just failed.

Yeah, same for me. Most of the messages I tried to send failed and I had to retry sending them at a later point.

Re: Slack issues

#34
post #9

Another status page that sucks. Slack goes down, people start texting me about it, status page is green, HN informs me that Slack is actually down. Next time I build a status page it will simply be a static HTML with green indicators and some random metrics, looks like it is the industry standard. :facepalm:

There are two kinds of status pages. Those that show you red when the service is up (automated) and those that show you green when the service is down (manual and automated) - or some mix of those two. You don't want made up information too, so for the manual one you'll get some delay for the analysis of the situation. Your actions are extremely unlikely to change if the downtime is for less than half an hour. So wha…

I expect:

* not lying

* not having to dig out our logs and proofs for SLA reasons on obvious fuckup.

> (Yes, I got annoyed at a thousandth comment that essentially says the status update is not instantaneous and perfectly reflecting the situation)

It's not about it being minute behind reality, it's about it lying in entirety. Why you have so much problems with understanding that ?

Re: Slack issues

#35
post #18

https://downdetector.com/status/slack/ Slack is definitely down even though their status page says otherwise. Incentives matter. If there is no penalty for misrepresenting the current state of an outage, you are going to find that company driven status pages are going to be frequently inaccurate.

In fact, there's an inverse incentive at play here. Slack is on the hook for missed SLA, so any admission of issue is legally and financially culpable. This means they don't want to admit to an issue until it's impossible to deny there is one.

There is also an incentive to display the proper status, since if you show all green when the service is down, you look dumb.

We recently improved our status reporting because our old status system might not accurately indicate if only a part of our service went down, so it might show green even though (some) customers definitely saw very obvious downtime.

Re: Slack issues

#36
post #35
post #18

Earlier quoted context omitted.

In fact, there's an inverse incentive at play here. Slack is on the hook for missed SLA, so any admission of issue is legally and financially culpable. This means they don't want to admit to an issue until it's impossible to deny there is one.

There is also an incentive to display the proper status, since if you show all green when the service is down, you look dumb. We recently improved our status reporting because our old status system might not accurately indicate if only a part of our service went down, so it might show green even though (some) customers definitely saw very obvious downtime.

When the choice is between temporarily "looking dumb" and permanently loosing a bunch of money because of SLAs, companies like Salesforce usually make the latter choice.

Re: Slack issues

#37
post #35

Earlier quoted context omitted.

There is also an incentive to display the proper status, since if you show all green when the service is down, you look dumb. We recently improved our status reporting because our old status system might not accurately indicate if only a part of our service went down, so it might show green even though (some) customers definitely saw very obvious downtime.

When the choice is between temporarily "looking dumb" and permanently loosing a bunch of money because of SLAs, companies like Salesforce usually make the latter choice.

I feel like customers treating you like a bunch of fucking idiots is not gonna be a great boost to your bottom line either. Maybe if you're in a market sector where reputation doesn't matter and you don't have any competition swooping in.

Re: Slack issues

#38
post #33
post #16

Finally! A chance to get some work done, undisturbed!

plugging my IRC gateway https://github.com/ltworf/localslackirc I find that using slack from IRC, and having the option to deprive some people/channels to notify me is very helpful to reduce the amount of distractions.

Nice! How does this compare to wee-slack?

Re: Slack issues

#39
Would a decent status page be an actually intelligent use of blockchain? We could have a global network of computers responsible for determining a consensus on whether a service is truly and actually down or not. It could be captured in an independent ledger, and ideally used as a canonical determination for status pages, SLA disputes, etc.

Re: Slack issues

#40
post #37

Earlier quoted context omitted.

When the choice is between temporarily "looking dumb" and permanently loosing a bunch of money because of SLAs, companies like Salesforce usually make the latter choice.

I feel like customers treating you like a bunch of fucking idiots is not gonna be a great boost to your bottom line either. Maybe if you're in a market sector where reputation doesn't matter and you don't have any competition swooping in.

The people signing the contract with Slack is not looking at the status pages, generally.
Post reply on HN