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 | 2 days 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:
-
Gary McMillian (@GaryMcMillianTX) reported@SlackHQ You need to fix your search before moving on to AI.
-
Noah Levin (@nlevin) reported@SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏
-
Q (@quionie) reported@thdxr @SlackHQ ohhh i’m so down for this because this would be MUCH better lol
-
Evgeny (@PlotnikovDev) reported@adilmania @SlackHQ What problem with slack? We use slack and discord.
-
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!
-
Sam Pullara (@sampullara) reported@thdxr @SlackHQ No one wants all replies to show up in the channel. It is a terrible defauu.
-
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....
-
IT (@IncredibleTrade) reportedIs @SlackHQ mobile app down?
-
jimmy hackett (@j1mmyhackett) reportedi shipped a report that posted a PDF to @SlackHQ with buttons to approve or flag it. worked great in testing. turns out every single report was re-sharing the exact same file. Next.js had cached the upload URL on the first request and just kept reusing it. so every property got the same PDF. same charts. same data. looked fine in the message. was completely wrong. the fix was straightforward once i saw it. but i only saw it because i added logging on the upload path and watched what Slack was actually returning. without that i would have kept assuming the reports were right. this is the thing that keeps biting me. i build something, it posts, the message looks correct, and i ship it. but "the message looks correct" is not the same as "the data is correct". i need the system to surface the difference, not just tell me a message was sent. the reports now work the way they were supposed to. one message per property, each with its own PDF, two models reading it and leaving grades in the thread. the buttons are how you reply to the report, not how you open it. but i almost shipped a monitoring system that was monitoring nothing. it was just confidently showing me the same snapshot on repeat. what is the dumbest caching bug you have hit in ****?
-
IT (@IncredibleTrade) reportedAny issues with @SlackHQ
-
HOURLY LIFE of Fred Campos (@FredsDaily) reported7:30a Getting eMail down to zero and loading up the team in @SlackHQ.
-
Leon (@MozzyFX) reportedPlease @SlackHQ can you add a proper GIF selector I need to send better gifs right after I take down production
-
Corey Quinn (@QuinnyPig) reported@samlambert @joshmgross It’s almost impossible to mention a bug in Slack and get anyone at @SlackHQ to fix it.
-
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.
-
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
-
Domino Mysłowski (@Domino_mys) reportedThere was Pay by Eye, by Ring, by Watch… time to Pay by Juice? 🧃💳 Okay, this one was just a joke created by Callum (FrostyTrollz). But 10 years ago, paying with your watch or ring also sounded ridiculous. A great example of how today’s joke can become tomorrow’s product is.. @SlackHQ The team behind Slack was actually building an online game called Glitch. As the founders later mentioned: “The game was absolutely preposterous.” Eventually, the game failed and was shut down. However, the internal chat tool they built to communicate became more valuable than the game itself. That tool became Slack, now used by millions of teams. 🌱 Follow for more wild growth-hacks
-
Uday Subbarayan (@udaysubbarayan) reported@SlackHQ Pl don’t hide the URL’s. Your recent overdoing here is creating problems Thanks
-
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.
-
TT 😋 (@MotivatingPeng) reported@OpenAIDevs @googledrive @SlackHQ Can we fix Codex.... When it does a context automatically compacted it stops what its doing
-
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
-
Josh Ellithorpe (@zquestz) reportedIt is very obvious that @SlackHQ does absolutely zero QA testing on Linux. You would think they would at least do a basic sanity test. Latest release has a completely broken system tray, and broken desktop icon. Glad I hardly use this crap anymore.
-
Travis Peters (@SivvyRat) reported@SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.
-
Chimene | Dantown (@AgentC_006) reported@thdxr @SlackHQ It’s always weird that you cannot actively reply to messages on Slack. The experience feels broken.
-
𝐎𝐧𝐞𝐓𝐫𝐮𝐞𝐇𝐨𝐦𝐢𝐞(👑,👑) (@OneTrueHomie) reportedisn't this the same problem @PromptQL promised @sama in order to kill @SlackHQ ?
-
Douglas Liscano (@douglas2428) reported@MatthewAry @github @SlackHQ Yes, we have the same problem today
-
Hamid Ali (@HamidAli) reportedUh is @SlackHQ having issues…? 👀 #Slack
-
duh (@qudnesa) reported@SlackHQ @question_base why not fix your own agent first?
-
SGN (@SGN06380601) reported@SlackHQ i need customer service help and am not getting a response from your agentforce. can you please help?
-
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
-
Giuseppe Skyline (@giskyexplorer) reported@gustaf @SlackHQ Notifications are the bandaid for broken reliability. WhatsApp stays quiet because it works.