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.
- Connection (50%)
- App Crashing (25%)
- Messaging (25%)
Live Outage Map
The most recent Slack outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 New York City
|
App Crashing | 25 days ago |
 Brest
|
Connection | 1 month 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:
-
Livleen Gill (@nutritogo) reported@SlackHQ - having a very difficult time with your product as a new customer. No help
-
mayberaigan (@mayberayyy) reported@SlackHQ your app notifications are glitching, please fix it
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting eMail down to zero, passing out assignments in @SlackHQ
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6a Getting eMail down to zero, loading up the team is @SlackHQ. Planning the day, so I can work the plan.
-
mr.tipton (@mrtipton_art) reported@pizzaboy @SlackHQ Nah, I’m that guy. Gotta fix it
-
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).
-
Chris Munns (@chrismunns) reportedsomehow @SlackHQ filtering of channels/DMs for last 30 days active hasn't worked for me for months. is this just a broken feature or have I done a thing.
-
MarketingMax.com (@MarketingMax) reportedI never call out bad marketing But this is just infuriating. I pay them thousands of dollars a year, have the app installed in my computer, phone, and even iPad … so why did I get this? And why is it not optimized for dark iPhones? Let me know if you need help @SlackHQ @Benioff
-
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?
-
Gap | Suby (@gaspardlezin) reportedCan someone please buy @SlackHQ and shut it down? This platform is horrible.
-
Drew Hirschi (@ashirsc) reported@SlackHQ pls never ask me again if I want to DM a thread when I tag someone with no text. This is a terrible feature.
-
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.
-
miya (@202409R) reported@ManusAI @SlackHQ This kind of UX that charges users instantly without a clear confirmation step is unacceptable. @ManusAI please fix this and issue a refund. Users should NOT be charged $394 by mistake.
-
Luigi ➔ nora.finance (@luigiremor) reported@discord @beeper I think I won't have this issue with @SlackHQ...
-
Douglas Liscano (@douglas2428) reported@MatthewAry @github @SlackHQ Yes, we have the same problem today
-
Cass Anderson (@casspa) reported@Yonar87 @SlackHQ same issue here. Just sent them an email. Their status landing page says they've been 100% find this quarter which makes me think maybe they just don't update that page?
-
Angelo 🇵🇷 (@ngeloxyz) reported@chrismunns @SlackHQ lmao its broken for me too I am using Railway's client for Slack now + Beeper for DMs.
-
Ariel Sterman (@ArielSterman) reportedIs @SlackHQ down? heard it here first.
-
Arun Sharma (@Oxymarun_) reported@SlackHQ came out of a failing 10-person game studio the team needed a way to coordinate that wasn't email they built it for themselves then realized every distributed team on earth had the same problem
-
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.
-
Calvin Lee (@calvinclee) reported@SlackHQ the mobile app has significantly regressed. why do I have a DM tab and an activity tab that only lets me filter down to DMs again? I want to easily filter for mentions.
-
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.
-
Otto Hilska (@mutru) reported@SlackHQ The new Activity view is an amazing improvement. One thing that would make it better: the same thread can appear multiple times (for example the original post and a reply). It would help to allow deduplicating threads from the list.
-
Theodor Marcu (@theodormarcu) reportedPutting an agent in Slack creates a very different UX problem: it has to know when to shut up We spent a lot of time tuning when Devin should speak, stay quiet, or move work into a separate channel. Devin was the first agent to support Slack natively, so it was great to bring 2 years of those learnings to @SlackHQ for the Slack Code launch.
-
Rohan (@iamTRA) reportedSlack upload API down? @SlackHQ Cratered team's morning.
-
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
-
Signal House (@SignalHouseSMS) reported@SlackHQ @notion the only repetitive question saved here that matters is 'is the otp service still down.' second only to 'is the otp service still down for everyone or just me'
-
𝐎𝐧𝐞𝐓𝐫𝐮𝐞𝐇𝐨𝐦𝐢𝐞(👑,👑) (@OneTrueHomie) reportedisn't this the same problem @PromptQL promised @sama in order to kill @SlackHQ ?
-
KRYTOS (@CSO_Krytos) reported@Cal_Irvine @thdxr @SlackHQ threads are terrible
-
Uday Subbarayan (@udaysubbarayan) reported@SlackHQ Pl don’t hide the URL’s. Your recent overdoing here is creating problems Thanks