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:
-
Rob Swift (@RobSwish) reported@AgentAkki @SlackHQ Restarting doesn't help, and I mentioned this in the dms, it seems so weird to basically have 2 dm lists.
-
Ari Dehkordi (@arashdehkordiHQ) reported@karrisaarinen @SlackHQ Did Linear do this before agents? I tried project-level Slack channels at my org and found it works for enterprise engagements nicely, but breaks down at feature/epic level projects for our SaaS. There's a granularity sweet spot, too fine and context switching costs spike. Too coarse and projects blur. Plus no project is actually isolated in small teams, so cross-project conversations forced more people onto each channel and productive engagement suffered. I get the AI context-confinement angle, but curious what other benefits you're seeing?
-
Bluejay (@getbluejay_ai) reportedBluejay AI can now act in @SlackHQ, not just answer. Run a simulation. Check how production calls went overnight. Resolve the issues that caused the failures. All from the channel your team is already in. Test, monitor, and improve your agents. Now in Slack. Led by Ronniel Gandhe.
-
Evan Oslick (@eoslick) reportedAnyone know how to gert @SlackHQ support? I've got a bit of a lingering issue that I'm not sure how do deal with due to ownership of Slack deployment.
-
Akshay (✈️ NYC) (@AgentAkki) reported@RobSwish @SlackHQ Does restarting the app fix it?
-
Paul Thornton (@Fusspawn) reported@SlackHQ @dorukkavcioglu I miss the old glitch game, had fun with some of your old founders in that :(
-
🇹🇼 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.
-
Ajith Joseph (@theajithjoseph) reportedFriday thought. @stewart raised $17 million to build a video game. 3 years of work! 40 people. And almost nobody wanted to play it. He shut it down in December 2012 and laid off most of the team. The only thing left standing was the chat tool they'd built to talk to each other while working on it. That tool was @SlackHQ. @salesforce bought it for $27.7 billion. The thing you're building in the quiet stretch isn't wasted. Sometimes it turns out to be the actual product.
-
siggy bilstein (@sbilstein) reported@evisdrenova hmm kinda like Kaniko caching locally, but I think the problem is that the industry has broadly gotten used to very slow deploy pipelines. Back when I was at @SlackHQ in like 2018, we used to SCP the monolith across the fleet and deploy in a couple minutes. Containerization is awesome for various reasons but it has gotten an entire generation of developers to just expect builds + deploys to take at least 15 and usually closer to 45. I do wonder how much perf you could squeeze out with replacing BuildKit but I imagine it's already highly optimized. I just *feel* like developers shouldn't have to think so much about why their builds are slow.
-
Evis Drenova (@evisdrenova) reported@sbilstein @SlackHQ yeah to your earlier point i think it depends at what layer you want to attack it i.e. rust builds are slow, caching can help but github actions is trash for it, but blacksmith isn't bad, is there a generic solution you can use that *just works* on any CI? alternatively, go after the actual docker execution layer but not clear to me how much of a bottleneck that actually is vs. language specific idiosyncrasies buildkit is pretty optimized from what i've heard but i generally agree with make it fast and stupidly easy to use!
-
Neil Chudleigh (@neilsuperduper) reported.@SlackHQ this message pops whenever i try to do any navigation. persists across restarts. also please fix the search results ↓ keypress issue, the first ↓ is being eaten by the system so when I am moving fast I am constantly going to the wrong place you need to make sure bugs like this dont continue, you have serious competition coming that is going to take business from you if you continue to let your product rot.
-
Jide (@rhymezx_code) reported@SlackHQ Tell me why Slack desktop is not working on Ubuntu 26.04 ( Resolute Raccoon ) ??? Honestly i have tried o
-
Rahul Chetia (@ayoImNotTrippin) reported@SlackHQ there’s a widespread issue with slack today. Not sure about Mac but my entire team with windows seems to be impacted. Slack becomes irresponsive on windows a few minutes in. Tried ‘repair’ and force close, but no help there. We are using app in our phones to communicate.
-
Savi (@SaviPabla) reported@trq212 Please @SlackHQ help us. I’m so tired of telling ppl to download. I’ve now started making videos of the html files and then sharing file as well lol
-
Riley Read-Only (@HotForMoot) reportedCmon @SlackHQ help the tfr
-
Kurush Dubash (@kurushdubash) reported@SlackHQ can you please revert your most recent update, it is so bad. This is terrible for anyone who is inbox 0. Please don't make me use Teams
-
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
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported8:30a Loading up the team in @SlackHQ and getting eMail down to zero. Planning out the day, so I can work out the plan.
-
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!
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported8a Loading the team in @SlackHQ, getting eMail down to zero and getting Daniel up for school.
-
Tulip 🌷 ☮️ (@imTulip) reportedIs @SlackHQ down?
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting email down to zero and loading both the website support and production teams in @SlackHQ.
-
Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported@purionx @SlackHQ @salesforce tables in slack would genuinely help, wild that it took this long to even be a request
-
Alex Sidorenko (@alexei_sid) reported@Moore_Irish @salesforce @SlackHQ Pricing changes that reduce admin control while pushing AI features rarely improve outcomes. The real test: does the AI actually help teams make faster, better decisions, or is it just another feature tax masquerading as innovation?
-
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?
-
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.
-
Sophia Yen MD (@teenmd) reported.@SlackHQ Why don't you have human service agents? You are a GIANT company used by many. The only contact us is via a webform?
-
Peter Dedene (@dedene) reported@tobi +1000 to this 🙌 Please @SlackHQ, we are practically begging for this fix at this point
-
Bad **** (@TeaseTech) reported@thdxr @SlackHQ What's the problem?
-
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