Live data from Hacker News

Incident at Slack

status.slack.com

11–20 of 96 posts

Re: Incident at Slack

#11
post #8
post #6

Earlier quoted context omitted.

Mine as well. I understand that Slack is widely used and I appreciate seeing their post-mortems discussed on HN but I don't consider image uploads issues with no technical explanations news-worthy and valuable enough for HN.

It seems you are of the minority... it's on the front page

A 404 link with a catchy title and "Show HN" raided from Twitter were also on the front page in recent hours.

Re: Incident at Slack

#12
post #6

Earlier quoted context omitted.

Mine as well. I understand that Slack is widely used and I appreciate seeing their post-mortems discussed on HN but I don't consider image uploads issues with no technical explanations news-worthy and valuable enough for HN.

> but I don't consider image uploads issues with no technical explanations news-worthy and valuable enough for HN Have you read the status entry? Among other things, calls is also affected.

Still not an "incident at Slack".

Re: Incident at Slack

#14

Yesterday Discord & Spotify, today Slack. Is it normal to have these big guys fail back to back?

Yes, that is completely normal. SAAS service disruptions happen all the time.

Re: Incident at Slack

#15

I 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 something going on on such channels (which brings anxiety and discomfort).

So, when Slack is down, it's actually a nice "everybody is offline: either take some time off or work focused on whatever you need to work on"... which is a nice thing to experience from time to time during regular business hours.

Re: Incident at Slack

#18

I 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…

Sounds like slack is the new "spend all day in your cubicle".

Re: Incident at Slack

#19

Yesterday Discord & Spotify, today Slack. Is it normal to have these big guys fail back to back?

Slack has a major outage almost weekly

We deal with issues because something is screwed up with their APIs badly enough that service is degraded all the time.

Re: Incident at Slack

#20
post #14

Yesterday Discord & Spotify, today Slack. Is it normal to have these big guys fail back to back?

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?
Post reply on HN