Incident at Slack
status.slack.com
Incident at Slack
1–10 of 96 posts
Re: Incident at Slack
#2Another day, another SAAS outage.
Re: Incident at Slack
#3My mind went completely diff direction after reading "Incident AT".
Re: Incident at Slack
#4Yesterday Discord & Spotify, today Slack. Is it normal to have these big guys fail back to back?
Re: Incident at Slack
#5This is more a service degradation / outage than an incident.
Re: Incident at Slack
#6My mind went completely diff direction after reading "Incident AT".
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.
Re: Incident at Slack
#7My mind went completely diff direction after reading "Incident AT".
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.
Re: Incident at Slack
#8My mind went completely diff direction after reading "Incident AT".
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
Re: Incident at Slack
#9My mind went completely diff direction after reading "Incident AT".
[deleted]
Re: Incident at Slack
#10I 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.