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 (50%)
- Connection (50%)
Live Outage Map
The most recent Slack outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 New York City
|
App Crashing | 30 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:
-
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?
-
🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reportedIts really disappointing that @SlackHQ status page suggests its up, when it's clearly down and you can get up to date status from X users who are reporting the same issues.
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting eMail down to zero and loading up the team in @SlackHQ.
-
Gap | Suby (@gaspardlezin) reportedCan someone please buy @SlackHQ and shut it down? This platform is horrible.
-
Jason Alco (@jason_alco) reported@SlackHQ Our team loves the platform, but we really need to fix the mark unread feature. It’s been broken for years now. First, you should be able to mark a channel as unread without opening the channel and selecting a message. Second, half the time marking a message as unread doesn’t work. I have to go message by message, trying over and over until one works. Please fix this, thank you 🫠
-
Travis Peters (@SivvyRat) reported@SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.
-
Son of Earth (@vasundhar) reported@SlackHQ there is issue with your cache where you store message send failure and likes
-
Agustín Ruiz (@aguscruiz) reportedHi @SlackHQ, can you please fix this notification dot issue? It's been bothering me for like a month or more already. It shows that I have something unread when I don't. Even hovering on it makes the dot go away when there's something unread. It's very annoying for people with "unread anxiety" like me lol. Thank you 🫶
-
GosuCoder (@GosuCoder) reportedSlackbot legit might be one of my favorite uses of AI outside of coding. I use this thing constantly to find past conversations, summarize entire chats, help write responses, look for things I might be forgetting, or even look up past context on a decision or topic. Seriously @SlackHQ this legit improves my life
-
David Welch (@david_welch) reportedHey @SlackHQ, there's some talk in the security community about the world is sorta burning down and we need a new space for community discussion. Would you ever donate to help a very highly visible space? You'd be next to names like IBM/Dell/Microsoft/etc. DMs open to chat
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6:30a Getting eMail down to zero. Planning out the work, so I can work out the plan. Loading support and production into @SlackHQ.
-
Richard Casimir (@NWFreeZone) reported@xsupport @slackHQ X links on slack (android) Still not working. All other sites redirect properly from slack. Just NOT X.
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported8:30a Back at my desk, loading the team up in @SlackHQ with today's assignment, getting eMail down to zero.
-
Uday Subbarayan (@udaysubbarayan) reported@SlackHQ Pl don’t hide the URL’s. Your recent overdoing here is creating problems Thanks
-
Mohammad Romman (@MohammadRoman8) reported@SlackHQ are you guys shutting down? It’s been more than a week I’ve been contacting you guys. Support isn’t responding at all
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported8:30a Got Daniel dropped off and heading back to my office to load the team up in @SlackHQ and get eMail down to zero.
-
Alex Oppenheimer (@Alexoppenheimer) reported@SlackHQ I can't login to even contact support. I am in an infinite 2FA loop. And I am being overcharged. Needless to say, I am not happy.
-
Angelo 🇵🇷 (@ngeloxyz) reported@chrismunns @SlackHQ lmao its broken for me too I am using Railway's client for Slack now + Beeper for DMs.
-
Theodor Marcu (@theodormarcu) reportedPutting an agent in Slack creates a very different type of 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.
-
SeattleViewHomes (@SeattleViewHome) reported@MadronaVentures @SlackHQ @salesforce Should we expect investment & AI to be doubling down on the green economy now that no one credible is promoting the fossil fuel/engineered obsolescence economies to be sustainable or even beneficial?
-
Andreas Elia (@digitalandreas) reported@cyberomin @SlackHQ Just to name a few: - Randomly opening channels a few miles up in the chat so I have to go all the way back down again - Right-click context menus are all over the place and inconsistent - Ghost notifications that show up randomly with no notification to go alongside them
-
Cathryn (@cathrynlavery) reported@Shopify @klaviyo @SlackHQ The Non-Technical Technical Dictionary, Day 2: Frontend & Backend Every app has a front of house and a back of house. Same as a restaurant. The frontend is what you see and touch. Think of Amazon, or any website you use. → The menu bar, the buttons, the search box. Everything on screen is just a list of things you're allowed to ask for. That's the menu, the dining room, the host stand. But nothing on that menu is actually happening at your table. When you hit "Buy Now," it's like placing an order with a waiter. He walks it back, the kitchen cooks it, and he brings it out when it's ready. The backend = the kitchen. You'll find database, business logic, server. Anything heavy (pulling your order history, processing a payment, sending an email) happens back there. The frontend only handles what fits at the table: how the buttons look, what color the page is, the small animations etc. Think Michelin star. They're not torching your steak tableside. They need the walk-in, the grill, the prep station, the sous chef. Software is the same. The interesting work needs the full kitchen. When a service like Cloudflare or AWS goes down and takes half the internet with it, that's a backend problem. The ghost kitchen caught fire and every restaurant relying on it went dark. A frontend problem is the one you've seen a hundred times: a button that won't click, text piled on top of an image, a page that looks broken on your phone. Frontend is form, where backend is function.
-
mewc (@the_mewc) reported@SlackHQ lots of bugs and issues right now. Can't create channels and lots of jankyness. This release is a lot.
-
Andreas Elia (@digitalandreas) reported@hugorcd @SlackHQ @github It has been broken for so long they probably think it's a feature internally
-
Noah Levin (@nlevin) reported@SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏
-
Evgeny (@PlotnikovDev) reported@adilmania @SlackHQ What problem with slack? We use slack and discord.
-
JM (@merklejosh) reported@SlackHQ There seems to be a bug in your Version 4.50.140 app (Mac) where if you have open a New message and you try to then click in the Search bar, you can't – it just flashes. Can you please fix this. It's very annoying. Thanks!
-
Greg Boyd / WGBOYD (@gregboyd) reported@SlackHQ What are the chances we can cut down the number of clicks to start a huddle from four to say… one? Driving me crazy. 🙏🏻
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6:30a Back at the home office. Getting eMail down to zero. Planning the day so I can work out the plan. Passing work into @SlackHQ.
-
Michael Grinich (@grinich) reported@SlackHQ Please fix the rate limits. The current Slack API is practically useless since you reduced them.