Earlier quoted context omitted.
Yes, that is completely normal. SAAS service disruptions happen all the time.
So why do they pride themselves on a 99.9% uptime if downtime is common and normal?
Downtime is not the same as service disruption
Incident at Slack
21–30 of 96 posts
Re: Incident at Slack
#22Yesterday Discord & Spotify, today Slack. Is it normal to have these big guys fail back to back?
During a war with a major cyber battle space?
I think it’s going to be the new normal
Re: Incident at Slack
#23Re: Incident at Slack
#24Earlier quoted context omitted.
Yes, that is completely normal. SAAS service disruptions happen all the time.
So why do they pride themselves on a 99.9% uptime if downtime is common and normal?
99.9% uptime is still more than 40 minutes downtime per month. According to their status page they are at 99.93% uptime for the current quarter even with the current incident.
Re: Incident at Slack
#25I wonder if there is a market for making a clone of slack, which syncs all data from slack, simply for use when slack is down. Big companies could pay monthly for "slack redundancy" from a third party.
This could be achieved by using a Matrix bridge to Slack: https://matrix.org/bridges/
Re: Incident at Slack
#26I wonder if there is a market for making a clone of slack, which syncs all data from slack, simply for use when slack is down. Big companies could pay monthly for "slack redundancy" from a third party.
Actually a clone wouldn't help much, because Slack itself is not really that great, even when it is up. There are better alternatives, which do not cause high CPU load every time one switches a channel, render Markdown properly (seriously, what is it with all the "enterprise service providers" being unable to use a decent markdown parser!?) and have have better integration with other open source tools.
Re: Incident at Slack
#27Earlier quoted context omitted.
Yes, that is completely normal. SAAS service disruptions happen all the time.
So why do they pride themselves on a 99.9% uptime if downtime is common and normal?
Uptime has nothing to do with anything in the real world. It's a number you put in an SLA of how much downtime is acceptable before they start paying you back money. And 99.9% still means 43 minutes of downtime every month. And even after that it's a calculation of risk. What does full redundancy cost vs paying back the fees for a say 24 hours of downtime? A lot of the time paying back money is way way cheaper then actually investing in technical redundancy.
Re: Incident at Slack
#28Earlier quoted context omitted.
So why do they pride themselves on a 99.9% uptime if downtime is common and normal?
99.9% uptime is still more than 40 minutes downtime per month. According to their status page they are at 99.93% uptime for the current quarter even with the current incident.
They wait multiple hours after failure before updating their status page, so their actual uptime is lower.
Re: Incident at Slack
#29I wonder if there is a market for making a clone of slack, which syncs all data from slack, simply for use when slack is down. Big companies could pay monthly for "slack redundancy" from a third party.
Well, I wouldn't use such a clone. When Slack is down, I actually feel relieved. I know I can turn off Slack any time I want, but the reality is that companies expect one to be online all the time (except during breaks of course) in regular working hours. I try to keep Slack as an async communication tool, but stakeholders just don't care about that. Also, I have a bunch of channels I cannot mute, so there is always…
You could break that expectation. I personally turn off notifications except for @-ing my name or @channel, and check DMs hourly. It has not been a problem, well, people don't DM me as much because I don't reply. Half the time they figure out the answer by themselves anyway.
Ideally you could discuss that the notifications are making you anxious and less productive and your employee could accommodate that. If your employer is not interested in helping you become more productive then maybe look somewhere else? You don't have to settle. Your mental health is paramount.
Re: Incident at Slack
#30I'm a bit baffled that a company with a communication tool like Slack does not communicate about these incidents _through_ slack itself. Why can't there be a little service notification somewhere in the screen? I know it wouldn't help much when the entire service is down, but when parts fail won't it be helpful to at least indicate this to the user?
Or might that be due to potential negative brand marketing that springs into existence when users see such a notice inside their application?