Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Slack Is Down (slack.com)
58 points by stevefan1999 on Oct 6, 2023 | hide | past | favorite | 51 comments


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.


Low hanging fruit: HN-based LLM-powered status page for *


You don’t need an LLM for that. Grab the feed and filter for post titles with “Ask HN”, “is”, and “down”.

Or use one of the myriad websites which tracks this stuff, such as https://downforeveryoneorjustme.com/


I'm not sure if the "downforeveryoneorjustme" would detect this issue.

In my case, only the desktop app failed. I was still able to use the web version


> I'm not sure if the "downforeveryoneorjustme" would detect this issue.

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


The underlying problem seems to be that “status pages” are now marketing and branding touchpoints instead of sources of information.



Will be interesting to see how long it takes them to update the status page. I will use this comment as a timestamp.


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.


https://slack.com/ is down too. Someone is having a terrible day...


They‘re probably in their Salesforce training already, should be up again in a week ;)


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.


Off topic, but how would you compare ESET and Bitdefender? (Kaspersky is kinda out of scope at least at the moment)


Productivity skyrockets


Yet their status page says that everything is fine... This says enough about how these status pages are unusable these days.


HackerNews is the status page for everything. I only came here now to check if Slack is down.


I really hope they incur some sort of data corruption that deletes the new UI code base while it’s down.


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


Nah, it’s terrible for a lot of people who struggle with all the workspaces and needless amount of clicks to get anything done.


i think most people are only in 1 slack


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.


you're in 5 or 6 different companies slacks?


Yeah? That’s pretty normal from what I’ve seen. Three business related ones. Two local meetup groups. One personal one.


I like the new UI. It works for me.


Status page is updated with ongoing incident: https://status.slack.com/2023-10/ad8f0e62516e8812


It’s not the most reassuring to see deflecting language:

“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.


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.


Yes, looks like it's their Auth system that is down, so this is likely system-wide for them.

I also just got the refreshed Slack UI moments before the outage, these things may or may not be related.


According to https://status.slack.com/ everything is fine. But it's not.


All that stuff is probably hardcoded. The traditional way of building a status page.


AWS thought us that one cannot trust status pages


I got the refreshed UI a few days back, so I'd be surprised if it was related.


Status page: Everything's fine. Morgan Freeman: Everything was, in fact, not fine.


Seems like DNS related issue? My client's not working but my colleagues are fine.


It's up again


Seems to be running fine for me (accessing from London)


Started working again for me (Norway)


Working from Scotland as well.


working from France and UK


doesn't work from sweden


yep ok for australia


Some people in our company are still able to have huddles and send messages while some cant. Maybe partial outage?


Meanwhile my raspberry pi has a sign saying "4 slack outages since last reboot"


It seems totally fine to me (London), maybe it's just down on the browser?


Seems fine via the client. Down via browser though.


Client down for me. Can't send messages. Same for my colleague in another country.


I can access it successfully via Google Chrome. The native client and Firefox are broken.

For a colleague it works all the way.

Sounds like a DNS issue.


Client for me is down. Even their homepage.

When I visit the homepage on a guest browser session though it seems to work fine.


For me client was completely dead, works now


Back up for the moment: US, east coast.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: