The desktop app started recover more functionality closer to noon Pacific.
Tom’s Guide reached out to Slack for comment or more information on the outage.
A spokesperson directed us to the status page.
Outage reports rolling in
Users first reported a Slack outage at around 11 a.m.
ET, withDowndetectorreports climbing to over 3,000 by 11:24 a.m. Users may also experience issues when attempting to log-in.
Thank you for your continued patience as we continue investigating.
We’ll be following up with further updates as they become available."
When did Slack acknowledge the outage?
On the status page, Slack first posted that it was investigating the issue at 10:27 a.m.
It’s not easy, but we (and tons of other companies) are making it work.
This update came around 9 AM Pacific.
No timeline from the company yet.
Users may also experience issues when attempting to log-in.
We appreciate your continued patience.
More updates will be shared as soon as possible."
Then there was also an outage in January 2021.
Looks like we can now add February 2025 to the list.
Back…ish?
Several of our colleagues have been able to log back into their Slack profiles and respond in channels.
However, a number of us are still locked out.
We’re seeing similar reports from other companies.
In some cases Slack never went down at all.
As of this post, Slack’s status page says the company is still investigating the issue.
We’ll be back with more updates as soon as they’re available."
We were directed to the Slack status page which still says the company is investigating the issue.
We’ll be back with more updates as soon as they’re available."
Right now, the reports have declined but are holding steady around 1200 according to their graphs.
The Desktop app still appears down.
There are alternatives though they don’t all offer the same level of experience.
Microsoft Teams and Google Chat, for example, are more for meetings.
Teams is far more finicky to set up, though it does integrate with the Office 365 platform.
Google Chat is part of the Google Workspace but uses threads over channels.
Both seem to be paid as well.
That service offers channels, DMs, and Zoom-esque meetings.
What do you like to use?
Maybe it’s back?
TheSlack status pageremains the same.
Slack’s most recent message indicates there still might be problems.
Users may also continue to experience issues when attempting to log-in.
Well provide new information as soon as its available."
Slack appears to back up
As far as we can tell, Slack is back up.
Down Detector is finally under 500 reports.
The Slack Status page recently updated to read that the company is working to get back to normal.
We apologize for the continued trouble."
We have seen some issues with people not receiving notifications but the general chat and channels are back up.
Let us know if its still down for you.
There’s no official word on when everything will return to normal.
We apologize for the continued trouble," reads the update posted at 2:35 p.m.
It’s possible Slack is trying to be conservative with its reports in case something goes wrong.
How did your company communicate?
While Slack was down, how did your team function?
Did you pivot to email?
Have you tried different communication methods like Microsoft Teams or Google Meet?
Slack issue identified
Slack has updated its status page with some news regarding the ongoing outage.
The company has some good news this time, claiming the issue has been identified.
Some users may still reproduce symptoms such as issues loading their workspaces.
According to the update, database shards in the Slack system are causing “feature degradation issues.”
Shards are portions of a system that usually help spread the load of the work filtering through the system.
The status page still lists the same sectors of Slack as being comrpomised.
Here’s the latest update from the Status page.
“Slash commands will be temporarily disrupted for a few minutes as we work on restoring service.
Users who boot during this time may experience issues.
Thank you for your patience.”
The outage is over
The outage appears to finally be fully over.