It was updated just now with a message saying "Users are having trouble connecting to Slack". So about 15 minutes since the comment above. However, I think the first reports started a bit earlier, so maybe 30 minutes is a better estimate.
Oh I forgot they are Salesforce now. We had to argue with Heroku, sometimes for weeks, before they even acknowledged they had hour-long outages that affected us. I hope Slack doesn't go the same way.
I'm curious if somebody from Slack could comment how much the acquisition changed Slack technologies.
I have first hand info from Avast - Norton merger and turning into corporation which doesn't value good RE talents was ridiculous and I've worked in corporate before, but this was just another level.
Middle management and up, their technical knowledge ended at turning PC on, hehe.
Btw they forced everybody even devs/RE guys into switching from Slack to Teams.
But still I have respect for original owners who build this AV company from 0. Too bad over the years it turned into this BS, where gathering and selling people's data is a normal thing for them.
At least there are guys from ESET, which is where people really care about fighting malware.
nah it's perfect for a lot of people who struggle to keep up with chats, just go to activity and you can find the chat you were just in instead of having to scroll through tons of channels
Wow. I wish. I think at my work we average around 5 or 6. Now it’s so hard to switch between them quickly, see what notifications there are and change your status.
I find this so infuriating that the standard flow is:
1. Notice issue;
2. Check provider status page which says all fine:
3. Have to go to HN to find the info that should’ve been on their status page.
This is what happens when performance reviews are tied to outages. I spent over five years at AWS, and even internally we treated the AWS status page as a running joke -- a bunch of us used an extension which just set the level of every outage to one higher than had been posted (i.e., green i/blue diamond was yellow, yellow was red).
The problem is, organisational leaders have performance reviews (and bonuses) tied to service health, and they'll avoid declaring outages to avoid looking bad.
53 comments
[ 4.5 ms ] story [ 106 ms ] threadI also just got the refreshed Slack UI moments before the outage, these things may or may not be related.
Status page is not updated: https://status.slack.com
Might be related: https://fortune.com/2023/10/05/slack-employees-one-week-off-...
When I visit the homepage on a guest browser session though it seems to work fine.
For a colleague it works all the way.
Sounds like a DNS issue.
I have first hand info from Avast - Norton merger and turning into corporation which doesn't value good RE talents was ridiculous and I've worked in corporate before, but this was just another level.
Middle management and up, their technical knowledge ended at turning PC on, hehe.
Btw they forced everybody even devs/RE guys into switching from Slack to Teams.
But still I have respect for original owners who build this AV company from 0. Too bad over the years it turned into this BS, where gathering and selling people's data is a normal thing for them.
At least there are guys from ESET, which is where people really care about fighting malware.
Or use one of the myriad websites which tracks this stuff, such as https://downforeveryoneorjustme.com/
In my case, only the desktop app failed. I was still able to use the web version
It would (and did) because it’s not just a service check, it also allows for users to report issues. Scroll down on the page.
https://downforeveryoneorjustme.com/slack
“Users are having trouble connecting”
“Some customers are encountering various errors”
They know exactly what’s going on, at least superficially via usage metrics, and should be able to quantify it.
The problem is, organisational leaders have performance reviews (and bonuses) tied to service health, and they'll avoid declaring outages to avoid looking bad.