Slack Outage Map
The map below depicts the most recent cities worldwide where Slack users have reported problems and outages. If you are having an issue with Slack, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Slack users affected:
Slack is a cloud-based set of proprietary collaboration tools and services. It's meant for teams and workplaces, can be used across multiple devices and platforms.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| New York City, NY | 1 |
| Brest, Brittany | 1 |
Check Current Status
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Slack Issues Reports
Latest outage, problems and issue reports in social media:
-
Manoj Yadav (@Manoj____Yadav) reported@TheNickBigar @CricTalk29 @SlackHQ No it doesn’t track time, you need to tell the time spent via message. Example- worked on X for 30 mins - remind me about checking the production issue around 3 pm The idea is to reduce friction for users on how they track time and tasks
-
Antonio Ventre (@antonioventre_) reportedA lot of companies in Hong Kong today got kicked out from shared @SlackHQ channels with clients etc However, Slack sent multiple emails to everyone back in February to move to Alibaba Cloud We did the migration in March, for 2 of our companies, and forced to do yearly plans (can’t do monthly subs with Alibaba Cloud) No major issues faced, apart from the fact that we doubled paid, since after the yearly payment they charged monthly again (but said that they will refund) If anyone has problems DM me, I have direct phone access with a representative and could fix this potentially asap
-
VISHAL (@_THE__FUHRER) reported@SlackHQ @stewart Stewart Butterfield and his team were developing a game called "Glitch" in 2011 The Glitch was an ambitious and creative multiplayer game, but it struggled to find a large enough playerbase. They had to shut it down on 2012
-
Peval 🇮🇹 🇪🇺 🇬🇧🏳️🌈 (@jabawack81) reported@gabsmashh Once nearly turned down a job interview because the invite came through @MicrosoftTeams. Spent the whole call trying to casually work out if they used @SlackHQ instead. They did.
-
Son of Earth (@vasundhar) reported@SlackHQ there is issue with your cache where you store message send failure and likes
-
Matthew Gattozzi 📷 Ads/Videos/Photos for Brands (@MatthewGattozzi) reported@RomanEcom @SlackHQ My HK clients dealing with the same issue
-
Krazed 🇵🇸 (@Krazed) reported@SlackHQ you have a degradation rn? unable to create channels and getting intermittent issues with events
-
PatrickUllrich (@ItsPatrickU) reported@karrisaarinen @linear @SlackHQ Linear coding agent when? 👀 currently handing it off to another service but be nice to skip the extra step.
-
Livleen Gill (@nutritogo) reported@SlackHQ - having a very difficult time with your product as a new customer. No help
-
Darcy (@darcy_jpa) reported@SlackHQ @linear @cursor_ai Slack is a garbage product. Everything about it is trash. The reliability is trash, the support is trash, and the way you handle users is absolute trash. Impressive how consistently terrible you manage to be.
-
TheHardTruth (@Watching1776) reported@SlackHQ You need to fix that app so it stops putting people into Auto Silence repeatedly without touching anything. Your code is trash
-
Jimidate (@Jimidvte) reported@SlackHQ, I’m having issues with my mobile notifications. I’ve checked every setting on my phone, uninstalled and reinstalled the app, yet I still don’t receive any push notifications. I’m missing time-sensitive information because I have to open the app before I see any updates.
-
Kitayoshi (@kitayoshi_son) reported@alphato_o @SlackHQ Even a sticky banner hanging on the workspace saying “Your workspace will be shutting down” on the chat page would be better. They could even use the UI components for the 90-day limit. Today’s behavior makes it seem like they just don’t care.
-
jimmy hackett (@j1mmyhackett) reportedthe scariest bugs in an agent system aren't the ones that crash loudly. they're the ones that succeed. quietly. and then stop. and you don't find out for three days. this week i shipped `fix(daily): heartbeat + agent-health for the daily-report jobs` (commit 10c954a). the cron had been running. the launchd plist was registered. no errors in the log. but the report wasn't landing in @SlackHQ. it took me longer than i want to admit to realize the job had silently stopped delivering. no crash, no alert, just absence. the mental model i pulled from it: a job that runs is not the same as a job that works. completion and correctness are two different signals, and most infra only monitors the first one. heartbeats fix this. you instrument the output, not just the process. if the report doesn't land by 8:05am, something fires. you stop trusting the scheduler and start verifying the result. this applies way past cron jobs. any pipeline where you only watch for failure will eventually drift silently into uselessness. the absence of an error is not evidence of health. once i wired heartbeats into the @AnthropicAI-powered agent fleet, i found two other jobs that had the same problem. they looked fine. they weren't. if you're running automated jobs and you're not monitoring outputs, you're not monitoring. what's the longest a silent failure ran in your system before you caught it?
-
Giuseppe Skyline (@giskyexplorer) reported@gustaf @SlackHQ Notifications are the bandaid for broken reliability. WhatsApp stays quiet because it works.
Check Current Status