I find slack so bloated and slow it would probably take me about 15 minutes to realise it was actually down.
Incident at Slack
31–40 of 96 posts
Re: Incident at Slack
#32Time for self-hosted https://rocket.chat :)
Re: Incident at Slack
#33I know a bunch of SaaS and other services have been hit, but at this is like the 3rd major slack outage this month. And typically my colleagues and I need to search third party sites to get any notification of what’s happening.
Re: Incident at Slack
#34I'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…
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.
Re: Incident at Slack
#35I'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…
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
Re: Incident at Slack
#36My mind went completely diff direction after reading "Incident AT".
Yeah really bad choice of word. “Availability” or “Degraded” is what they’re looking for.
Re: Incident at Slack
#37I'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…
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.
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 both query the actual service with a call from outside and can be updated manually with physical persons at Slack, and the client checks that domain, I think it can work.
Re: Incident at Slack
#38I'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…
It makes perfect sense from a user perspective but I suspect the company isn't interested in making mere users aware of ongoing issues via the service itself.
Re: Incident at Slack
#39Earlier 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.
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
Re: Incident at Slack
#40I'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…
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.
But in this case Slack was not down. Parts of the service were frustratingly lagging, like uploading a picture or using reactions. Circle CI does have this sort of warning on their sidebar. There's so many parts to a big software product that it would definitely useful to know if some part of it was having issues.