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 (40%)
- Messaging (20%)
- Connection (20%)
- Video (20%)
Live Outage Map
The most recent Slack outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Township of Evan
|
Messaging | 9 days ago |
|
Township of Evan
|
App Crashing | 10 days ago |
 Guayaquil
|
Video | 15 days ago |
|
New York City
|
App Crashing | 2 months ago |
 Brest
|
Connection | 2 months ago |
 Ródos
|
Messaging | 4 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:
-
Q (@quionie) reported@thdxr @SlackHQ ohhh i’m so down for this because this would be MUCH better lol
-
Conor Bronsdon (@ConorBronsdon) reported.@SlackHQ is building for multiplayer AI: tag a coding agent into a Slack conversation and it spins up a coding channel: everyone in that convo gets a live dev environment, diffs post as artifacts, and the channel winds down when the task is done. With the launch of Slack Code, Claudeforce, their MCP and more, Slack is putting Agents in the channels where teams already work, not simply in a private chat with one person. Their position is that the whole team should be able to watch, steer, and review what the agent does. Slack Chief Product Officer Jaime DeLanghe joined me on @chain_ofthought to explain how Slack is building a team AI environment, what happens mechanically when a code channel is created, why Anthropic pushes so much of its code through Slack, how the channel permission model became the agent context model, and what has to change in engineering culture when the whole team is steering one agent. I think Slack is the platform best positioned to become the context harness where enterprise agents run: agents that see what the team discusses, permissions that already exist, and a cultural opportunity hiding inside every multiplayer coding session. Chapters: (0:00) Slack as an IDE and a GitHub for your team (0:29) Who is Jaime DeLanghe (1:21) The reaction to the Slack Code launch (5:30) Why coding agents belong in a context-rich environment (6:08) Engineers now manage agents, not copy-paste code (7:24) The permission model: agents get the channel's context (11:44) What happens when a code channel is created (15:00) Why Anthropic pushes so much code through Slack (19:14) Steering one agent with many people: culture decides (24:54) Slackbot, skills, and MCPs: agents go where the work is (30:53) The solo terminal vs. agents in social spaces (33:53) Org charts and ownership when agents join the team (39:33) Learning loops and shared agent memory (42:39) Citations, recency, and accidental knowledge management (46:50) Context bloat and multi-pass search for agents (50:01) How Jaime uses Slackbot as CPO (52:38) Slack Code is V1 of multiplayer AI
-
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.
-
April Underwood (@aunder) reportedIn this day and age of infosec threats, this subject line from @SlackHQ is a bad call. After the brief cortisol spike that someone using the name Miles Davis had joined our Slack, I scrolled down, and then just wondered why on earth I would want this in my work communication tool.
-
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
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported6:30a Quickly getting eMail down to zero, loading the team up in @SlackHQ before a full morning of appointments.
-
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....
-
Gary McMillian (@GaryMcMillianTX) reported@SlackHQ You need to fix your search before moving on to AI.
-
trent.sol (@trentdotsol) reported@cavemanloverboy @alessandrod @SlackHQ i did. it's the ones who won't that are the problem
-
Stache (@stacheFonzi) reportedIt's from 2011, but I still miss Glitch. It was a browser based MMO based on collecting and crafting. Crazily enough it was made by the company that went on to rebrand and make @SlackHQ. The messaging system in the game became the basis for Slack.
-
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
-
Paul Sant · Telecodex (@YouPulseX) reported@pizzaboy @karrisaarinen @SlackHQ Then "project channel" is a default, not a scope. The issue list command still follows the caller's workspace visibility.
-
Sam Pullara (@sampullara) reported@thdxr @SlackHQ No one wants all replies to show up in the channel. It is a terrible defauu.
-
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?
-
Noah Levin (@nlevin) reported@SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏
-
Andreas Elia (@digitalandreas) reported@SlackHQ Can you fix the main parts of Slack before adding more features pls? 🙏
-
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.
-
jimmy hackett (@j1mmyhackett) reportedthe most dangerous bug isn't the one that crashes. it's the one that says 'all good' when it isn't. i had a checker that was supposed to flag a problem. it was reporting green. every single run. turns out it was checking the documentation of the thing it was hunting, not the thing itself. so whenever the problem existed and was documented, the checker saw the doc, said 'found it, it's tracked', and moved on. confident. wrong. this happened twice in the same week in two different places. a report card that shipped one of its four answers unconditionally regardless of the actual data. a monitor that was asserting schema state it had never actually read. both passed. both lied. the lesson i keep relearning: a check that can't fail toward a confident opposite is not a check. it's a placebo. the question isn't 'does this run without error.' the question is 'what would this have to see to fire, and can it actually see that thing.' if the answer to 'can it see it' is 'well, kind of, it reads the notes about it'. you don't have a checker. you have a script that reads its own homework. @SlackHQ kept posting green cards. @AnthropicAI's Claude Code kept summarising them as healthy. everything looked fine. nothing was. what's the quietest false-green you've shipped?
-
duh (@qudnesa) reported@SlackHQ @question_base why not fix your own agent first?
-
Hamid Ali (@HamidAli) reportedUh is @SlackHQ having issues…? 👀 #Slack
-
Rodrigo Berriel (@rodrigoberriel) reported@thdxr @SlackHQ unbelievable right? terrible ux
-
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.
-
Luigi ➔ nora.finance (@luigiremor) reported@discord @beeper I think I won't have this issue with @SlackHQ...
-
Travis Peters (@SivvyRat) reported@SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.
-
Dhruv (@dhruv2038) reportedIs @SlackHQ broken today - I am using Focus mode - seems like the emoticons are breaking.
-
IT (@IncredibleTrade) reportedAny issues with @SlackHQ
-
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.
-
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?
-
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.
-
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?