Slack reported an outage on February 26 and 27, with most features back up by Thursday but some issues with messaging still persisting; in particular, some custom apps and bots did not work as expected. In addition, a problem with Slack Connect meant coworkers might not get notified if someone pinged them with the @ command. According to Downdetector, about 3,000 people had reported issues at the peak of the problem.
As of Thursday morning, Slack said most features had been restored. Users still experiencing trouble were advised to reload Slack (Command + Shift + R on Mac or Ctrl + Shift + R on Windows or Linux).
Slack team’s response to the outage, including Slack Connect tips
The loss of functionality on Wednesday was “related to Events API and is a symptom of an earlier incident about trouble connecting to or loading Slack,” plus an unrelated problem with Slack Connect causing the lack of notifications, Slack said.
Our workplace sysadmin team announced problems with Slack at around 1:00 p.m. EST on February 26, with some employees being unable to post messages. (My work was not disrupted.)
SEE: Slack added tools for automatically building workflows, including for developers.
Explore emtech 360 for the latest advancements in Information Technology & insightful updates from industry experts!
Source : https://www.techrepublic.com/article/slack-outage-february-2025/
