Slack status: messaging issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
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.
Problems in the last 24 hours
The graph below depicts the number of Slack reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
At the moment, we haven't detected any problems at Slack. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Slack users through our website.
- App Crashing (33%)
- Messaging (33%)
- Connection (33%)
Live Outage Map
The most recent Slack outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 New York City
|
App Crashing | 26 days ago |
 Brest
|
Connection | 2 months ago |
 Ródos
|
Messaging | 3 months ago |
 Belo Horizonte
|
Connection | 3 months ago |
 Jewar
|
App Crashing | 3 months ago |
|
Colorado Springs
|
Messaging | 3 months ago |
Full Outage Map
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:
-
Bad **** (@TeaseTech) reported@thdxr @SlackHQ What's the problem?
-
Travis Peters (@SivvyRat) reported@SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.
-
Brandon Karl Webster (@bkwebster) reported@adilmania @SlackHQ Better alternatives exist - it’s used abundantly because of the mindshare and scale. The only replacement would be a totally new and obvious form factor that leads to the same outcome in a better way - not a better alternative to the same problem.
-
Sammie (@nexgencoded) reported@SlackHQ really said what if your coworker wasn't annoying enough?? now you can add an AI coding agent to the group chat @Claude fix this 30 seconds later claude: PR opened greg from accounting: why is there a PR claude: I have no idea who Greg is....
-
Dan (@pizzaboy) reported@karrisaarinen @SlackHQ Hey @karrisaarinen are the new project slack channels scoped to just that project I.e if you use the Linear slack bot in the channel will it only have access to issues and data from that project? I found that to be an issue a couple of months ago that the bot wasn’t able to be scoped down? Or was this a skill issue on my end
-
matt taylor (@mattployed) reportedslack going down for 30 minutes was like the apocalypse for tech startups @SlackHQ PLEASE dont scare me like that again
-
Awais alwaisy (@alvaisy) reported@adilmania @SlackHQ what's wrong with slack. bunch of alternatives. each one made money. slack is still stable and useful. i don't have any issue with slakc except limited message history for free users
-
IT (@IncredibleTrade) reportedIs @SlackHQ mobile app down?
-
Jide (@rhymezx_code) reported@SlackHQ Tell me why Slack desktop is not working on Ubuntu 26.04 ( Resolute Raccoon ) ??? Honestly i have tried o
-
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
-
IT (@IncredibleTrade) reportedAny issues with @SlackHQ
-
Ellen DaSilva (@ellenjdasilva) reportedSketchy behavior: Someone from @SlackHQ joined my company channel last week saying "we're here to help you with the product" (we're not having issues). Then today started pestering me about an overdue invoice (we don't have one). Beyond violating. Shameful behavior @salesforce.
-
Jose Urquiza (@hollowvox) reportedWe're about to start letting our employees fix their own bugs with @v0 and @SlackHQ. Why report a bug to another system when you can send it straight to v0? All I have to do is review the PR and merge it in. So confident in the models and the platform that I can go hands off.
-
Noah Levin (@nlevin) reported@SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏
-
jimmy hackett (@j1mmyhackett) reportedi shipped a report that posted a PDF to @SlackHQ with buttons to approve or flag it. worked great in testing. turns out every single report was re-sharing the exact same file. Next.js had cached the upload URL on the first request and just kept reusing it. so every property got the same PDF. same charts. same data. looked fine in the message. was completely wrong. the fix was straightforward once i saw it. but i only saw it because i added logging on the upload path and watched what Slack was actually returning. without that i would have kept assuming the reports were right. this is the thing that keeps biting me. i build something, it posts, the message looks correct, and i ship it. but "the message looks correct" is not the same as "the data is correct". i need the system to surface the difference, not just tell me a message was sent. the reports now work the way they were supposed to. one message per property, each with its own PDF, two models reading it and leaving grades in the thread. the buttons are how you reply to the report, not how you open it. but i almost shipped a monitoring system that was monitoring nothing. it was just confidently showing me the same snapshot on repeat. what is the dumbest caching bug you have hit in ****?
-
Q (@quionie) reported@thdxr @SlackHQ ohhh i’m so down for this because this would be MUCH better lol
-
Jon Slemp (@Jon_Slemp) reportedBug report for you @SlackHQ — when receiving a DM notification from Agents, and those agents are setup as Slack apps you have to DM directly in an app channel, once you hit a certain number of chats in your history tab you can no longer navigate to the DM directly by clicking the DM notification on mobile. You basically get navigated to a blank screen and effectively chat find the message ever. Please fix. This is a disaster of a bug.
-
Simon Taylor (@sytaylor) reportedDear @SlackHQ and @beehiiv Making ctrl+k NOT be the hyperlink shortcut is deliberate pain inflicated on GDocs and Gsuite users. Please fix.
-
TT 😋 (@MotivatingPeng) reported@OpenAIDevs @googledrive @SlackHQ Can we fix Codex.... When it does a context automatically compacted it stops what its doing
-
Adil Mania. (@adilmania) reported@NebulaAI @safizaq @SlackHQ discord integration is kinda broken, like i keep having "nebula" links showing, if you can fix that, that will be perfect.
-
Bhuvanesh Sridharan (@_bhuvanesh_) reportedas much hate @MicrosoftTeams gets, at least the meeting chat and other chats are on the same platform. Absence of synergy between @SlackHQ chat and Google meet is such a pet peeve. Non issue in grand scheme but still bothering whenever people send links in gmeet.
-
Tyler (@tyhouch) reportedyo @SlackHQ please add support for viewing .html files in chat. everyones tossing these around and the download->open in chrome friction is slowing me down bigtime
-
Luigi ➔ nora.finance (@luigiremor) reported@discord @beeper I think I won't have this issue with @SlackHQ...
-
y - alex ⚔️ (@onelonesabre) reported@SlackHQ @question_base can't use these features when your app is down my friend
-
Andreas Elia (@digitalandreas) reported@johnbarker @SlackHQ Doesn't feel like they are. We've had a bunch of pre-existing issues for a while now (I replied to the other fella in the tweet with examples).
-
Ravi (@ravilutionx) reported@SlackHQ @trq212 And a verbosity problem
-
Krazed 🇵🇸 (@Krazed) reported@SlackHQ you have a degradation rn? unable to create channels and getting intermittent issues with events
-
Razi Ansari (@RaziAns14640044) reported@SlackHQ should fix the UX of their video player. It's one of the worst pieces of UX I've ever interacted with. It feels like I suddenly landed on some government app. Too messy
-
Kleptocracy (@lfdoyfydoydtd) reported@salesforce @SlackHQ Instead of buying other crappy software companies, create the best sales rep. SFDC 1.0>2.0>3.0... ITS ALL SO BROKEN. Broken company that had a chance to replace salespeople but didn’t use the data and systems they already had to make it happen with agents. WTF is agentforce?
-
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?