Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Incident at Slack

status.slack.com

Post reply on HN
Print view View original

41–50 of 96 posts

Re: Incident at Slack

#41

Post by abcmer »

marapuru wrote: post #30

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

Documenting on a webpage allows a historical record of the incident long after the incident is over. I agree that an in-app notification would also be a nice feature.

Re: Incident at Slack

#42

Post by lenn0x »

dagw wrote: post #35
madeofpalk wrote: post #34

Earlier quoted context omitted.

Wouldn't that be an anti-feature? When Slack is down, Slack can't tell you when it is down. It's why status pages are often on other domains/systems etc, so the status page remains up while everything else is on fire.

While it of course won't work in every case, in this case Slack wasn't down, you just couldn't attach files in some situations. This is something Slack easily could have communicated as soon as you tried to attach a file. Now it look like it worked and then times out after a couple of minutes and deleted your message

Ever since this started, been seeing 100% failure on webhooks for Event subscriptions.

Re: Incident at Slack

#43

Post by lenn0x »

mritzmann wrote: post #7
hericium wrote: 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.

been seeing 100% failures on webhook event subscriptions too. that's only reason I noticed right away.

Re: Incident at Slack

#44

Post by dr_pardee »

marapuru wrote: post #30

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

Add their status to one of your channels (https://slack.com/apps/A0F81R7U7-rss)

/feed subscribe https://status.slack.com/feed/rss

Re: Incident at Slack

#45

Post by lopis »

sdevonoes wrote: post #15
londons_explore wrote: post #10

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…

Reading people's experiences in their companies makes me feel a) sad that there's so many people that have to endure this kind of work environment, b) so fortunate that I can't identify myself with any of this.

If I text someone and they reply within a day, that's fine to me, and it's fine to any of my colleagues. If it takes more than a day, I'll ping them again, and everyone can still chill.

Re: Incident at Slack

#46

Post by lrem »

rjh29 wrote: post #28
WJW wrote: post #24

Earlier quoted context omitted.

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.

The 99.9% claims is likely on the actual uptime, not on the time the status page claimed to be up.

Re: Incident at Slack

#47

Post by sharklazer »

zht wrote: post #39
can16358p wrote: post #37

Earlier quoted context omitted.

If it's on a different domain and servers, I don't think it will be an issue. If they have it on an API call to (making it up) api.slack.com/status it might very well go down when things go wrong, making it useless. However if they physically host it elsewhere ideally on a different cloud provider, with a different domain, say, slackstatus.com/api-status that is completely separate from the actual services, which can…

this sounds very complicated lol

No, not really. If your calls time out, ping the status server. Done.

It sounds more like laziness than complication to me. But that typifies Slack dev culture—“just use duct tape”

Re: Incident at Slack

#48

Post by cupofpython »

lopis wrote: post #45
sdevonoes wrote: post #15

Earlier quoted context omitted.

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…

Reading people's experiences in their companies makes me feel a) sad that there's so many people that have to endure this kind of work environment, b) so fortunate that I can't identify myself with any of this. If I text someone and they reply within a day, that's fine to me, and it's fine to any of my colleagues. If it takes more than a day, I'll ping them again, and everyone can still chill.

what industry are you in?

Re: Incident at Slack

#49

Post by Linkd »

sharklazer wrote: post #47
zht wrote: post #39

Earlier quoted context omitted.

this sounds very complicated lol

No, not really. If your calls time out, ping the status server. Done. It sounds more like laziness than complication to me. But that typifies Slack dev culture—“just use duct tape”

And that's exactly how you DDOS your status server.
Post reply on HN