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%)
- Connection (33%)
- Video (33%)
Live Outage Map
The most recent Slack outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Guayaquil
|
Video | 11 hours ago |
 New York City
|
App Crashing | 1 month ago |
 Brest
|
Connection | 2 months ago |
 Ródos
|
Messaging | 3 months ago |
 Belo Horizonte
|
Connection | 3 months ago |
 Jewar
|
App Crashing | 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:
-
Jide (@rhymezx_code) reported@SlackHQ Tell me why Slack desktop is not working on Ubuntu 26.04 ( Resolute Raccoon ) ??? Honestly i have tried o #Ubuntu
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting eMail down to zero and loading up the team in @SlackHQ.
-
Assaf Kipnis (@Kipnis_a) reportedClaude is the best corporate CYA buddy I used to have full CYA files with records of messages, emails and things I did - I was terrible at keeping those and people took advantage of that. With Claude and @meetgranola - I have canonical record of all conversations, @SlackHQ messages, emails, canonical decisions - everything Oh, you say I didnt do something? I didnt respond? Here come the receipts
-
Jake Mor (@jakemor) reportedcan someone at @SlackHQ please for the love of god fix drag and drop to attach a file? how has this been an issue for months without anyone realizing? Steps to reproduce: Drag file to attach. Nothing happens. no file attached.
-
Subrat Prasad (@humbledshuttler) reported@SlackHQ please fix huddles on android.
-
Vortex (@mjparme) reported@SlackHQ why is there no obvious way to join a channel in Slack? Seems like a huge usability problem, the + sign next to channels creates a channel, but joining one is very elusive
-
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
-
Peval 🇮🇹 🇪🇺 🇬🇧🏳️🌈 (@jabawack81) reported@gabsmashh Once nearly turned down a job interview because the invite came through @MicrosoftTeams. Spent the whole call trying to casually work out if they used @SlackHQ instead. They did.
-
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.
-
Krazed 🇵🇸 (@Krazed) reported@SlackHQ you have a degradation rn? unable to create channels and getting intermittent issues with events
-
Luke Hutchison (@LukeHutchison) reportedWhy we're SaaSmaxxing at Perfect Venue Three months ago I tried vibe coding our way out of half our SaaS stack and racked up a $20k Replit bill. Now we are doing the opposite, doubling down on our existing vendors and adding more to our stack. It started small. A better prospecting tool built in Replit. ICP scoring, competitor signals, enrichment. It "worked," and that was the problem. I could come up with an idea and within minutes a version that "worked" was in front of me. It was a lot of fun at first. Once you see how fast you can build exactly what you want, scope creeps hard. Within weeks I was eyeing our ATS, our feedback board, and parts of HubSpot. Part of me also wanted to try vibe coding because when you're leading a company where "apocalypse" is being added to your industry category, I thought it would be good to know if it was a real threat or just hype. We sell software to restaurants and venues. Homegrown spreadsheets and internal tools have always been our biggest competitor, long before AI. So the real question wasn't "can you build your own?" It was: has that math actually shifted, or does it just feel like it has? But then reality set in. I was quickly reminded of the saying in engineering that "the first 90% of a project takes 90% of the time, and the remaining 10% takes another 90% of the time." Getting a demo working was fast, but feature requests and bugs quickly piled up. Obviously we could put the feature requests in the icebox, but that defeats one of the main goals of custom software: being able to customize it to your business. The problem is that customization requires a customizer. Every field and edge case routed through one person. Me. Next, we explored having an engineer work on building a more sustainable solution. However, the direct cost of that engineer working on an internal tool was much higher than all of our SaaS spend combined. The indirect cost was even higher, because it meant that engineer was not working on our core product and building features that could drive much more revenue than the costs they would be able to reduce, not to mention stronger market positioning. There were also other indirect costs. I was interviewing for a recruiting role and explaining to her that we were moving off Ashby to a vibe coded tool. As soon as the words came out of my mouth, I could tell that decision was a bug and not a feature. The reality is that people have worked with many popular SaaS tools for years. They may not love them, but they know how to work with them, and they can focus on doing their job instead of being a design partner for a vibe coded tool. Another challenge was that growth meant building. Even if we were able to build and maintain a custom solution, it was just for a point in time. As the team and company grew, we needed new functionality. With a SaaS vendor, it is very rare that we would need something they didn't already have. They've been solving for the needs of thousands of businesses for years, it's rare we would really need something that another one of their customers had not come across before. Often we'd have to pay more, but it was as simple as a quick upgrade. With a vibe coded solution, it meant understanding the problem, designing and building a solution, and then maintaining it. So where are we today? We're SaaSmaxxing. We're getting everything we already paid for out of the tools we already have - here is how we're doing it. Use AI to better use our SaaS tools. Instead of seeing the problem as AI vs. SaaS, we're using AI to help us better use the tools we have. One of the most frustrating things about SaaS products is that they can be complex and hard to use, with settings buried and functionality hidden. Help centers only go so far. With Claude, I'm able to explain what I'm trying to do, and it can help me configure our existing tools or find a product that integrates with our existing software and solves the problem. Use vibe coding to prototype functionality we wish we had. When there is functionality that we wish we had with our vendors, we'll vibe code a prototype and then find ways to recreate that functionality with our existing tools. Take the 80/20 and move on. Almost every improvement we wanted had a good-enough version in a product we already paid for. Solving for the last 20% was far more expensive than it was worth. Clearly define the problem. As a business owner, my problem was that it was frustrating to log into all of these different tools to understand what was going on with my business. I now use a tool called Viktor to easily pull information across all of our different tools and send reports to me in Slack. File the feature request. Their roadmap is free engineering. A vendor building it once for a thousand customers beats me building it once for us. Has the build-versus-buy line moved? Yes. Building the feature list is dramatically cheaper than it was two years ago. But the feature list was never the expensive part. Owning it is. For the vast majority of our vendors, the amount we pay is a fraction of the value we get, even in the AI era. Our industry is changing faster than ever, and who knows what functionality new models will bring, but this is where we've landed for now. We're buying @HubSpot, @SlackHQ, Canny, Ashby, etc - and focusing on building Perfect Venue faster than ever with the help of AI. Great work @dharmesh and team on the continued updates!
-
a Nate da Novenchi 🐂🀄️ (@NATE9169) reported@adjohu @SlackHQ The crypto community loves the idea of Wild Static, do you have a solana wallet we can donate to to help fund you vision?
-
Rab Memari (@rabmemari) reported@chriskim_dev @Teknium No problem. I think its more of a @SlackHQ problem, but happy to check if I can fix it in Hermes and push a PR
-
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.
-
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....
-
Sam Pullara (@sampullara) reported@thdxr @SlackHQ No one wants all replies to show up in the channel. It is a terrible defauu.
-
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
-
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.
-
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?
-
LoopGantt (@loopgantt) reported@NotionHQ @SlackHQ Channel-scoped agents fix the biggest AI rollout blocker — broad access feels risky to admins. Smart default.
-
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.
-
Taha Tesser (@TahaTesser) reported@KhalidWarsa @SlackHQ Because each workspace has own login. Even if you login on one device. You cannot sync all those workspaces under one account on another device
-
IT (@IncredibleTrade) reportedAny issues with @SlackHQ
-
kzer_AI (@kzer_ai) reported@OpenAI @linear @SlackHQ The agent that pulls context from docs, email, chats, and code to update your Linear ticket: "status: someone else's problem"
-
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
-
✩°｡⋆⸜ (@lenvioux) reportedHEY @SlackHQ WHY I DIDNT GET NOTIFICATIONS neither on my phone for every conversation i had?!?! nor on my laptop app… unless i checked it every minutes?!!!? HELP
-
gerry🗯 (@Gerry) reported@zquestz @SlackHQ Ask codex to fix it
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting email down to zero and loading both the website support and production teams in @SlackHQ.
-
matt taylor (@mattployed) reportedslack going down for 30 minutes was like the apocalypse for tech startups @SlackHQ PLEASE dont scare me like that again
-
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.