Slack status: messaging issues and outage reports

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.

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	12 days ago
Township of Evan	App Crashing	13 days ago
Guayaquil	Video	18 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:

• 
  Vortex (@mjparme) reported 3 minutes ago

  @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

• 
  Cass Anderson (@casspa) reported 13 minutes ago

  @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?

• 
  Chimene | Dantown (@AgentC_006) reported 16 minutes ago

  @thdxr @SlackHQ It’s always weird that you cannot actively reply to messages on Slack. The experience feels broken.

• 
  Jon Slemp (@Jon_Slemp) reported 20 minutes ago

  Bug report for you @SlackHQ — when receiving a DM notification from Agents, and those agents are setup as Slack apps you have to DM directly in an app channel, once you hit a certain number of chats in your history tab you can no longer navigate to the DM directly by clicking the DM notification on mobile. You basically get navigated to a blank screen and effectively chat find the message ever. Please fix. This is a disaster of a bug.

• 
  Dan (@pizzaboy) reported 20 minutes ago

  @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

• 
  Rodrigo Berriel (@rodrigoberriel) reported 21 minutes ago

  @thdxr @SlackHQ unbelievable right? terrible ux

• 
  Akshay (✈️ NYC) (@AgentAkki) reported 23 minutes ago

  @RobSwish @SlackHQ Does restarting the app fix it?

• 
  siggy bilstein (@sbilstein) reported 27 minutes ago

  @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.

• 
  Rohan (@iamTRA) reported 32 minutes ago

  Slack upload API down? @SlackHQ Cratered team's morning.

• 
  Peter Garber (@petegarber) reported 32 minutes ago

  @Cartidise @OutofGalaxyy The icons might be stupid here but Gchat works pretty well inside of Gmail and this UI actually is OK. The only problem is that Gchat should literally be able to replace @SlackHQ but it’s been ignored.

• 
  Sam Pullara (@sampullara) reported 33 minutes ago

  @thdxr @SlackHQ No one wants all replies to show up in the channel. It is a terrible defauu.

• 
  Salman (@m_salman_afzal) reported 33 minutes ago

  no meaningful way to contribute. Just like closed source/proprietary software, you can report issues, but whether it gets fixed or not depends upon the creator. For example, there are couple of issue that I reported to @SlackHQ regarding screen sharing popups,

• 
  LANGERIUS (@Langerius) reported 34 minutes ago

  @BarknTuncer @SlackHQ yeah notification sync issues are still surprisingly common

• 
  Richard Casimir (@NWFreeZone) reported 35 minutes ago

  @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) reported 37 minutes ago

  6:30a Quickly getting eMail down to zero, loading the team up in @SlackHQ before a full morning of appointments.

• 
  Uday Subbarayan (@udaysubbarayan) reported 38 minutes ago

  @SlackHQ Pl don’t hide the URL’s. Your recent overdoing here is creating problems Thanks

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 40 minutes ago

  6: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.

• 
  Josh Ellithorpe (@zquestz) reported 42 minutes ago

  It 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.

• 
  Luke Hutchison (@LukeHutchison) reported 42 minutes ago

  Why 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!

• 
  Chris Munns (@chrismunns) reported 43 minutes ago

  somehow @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.

• 
  Kelly Carter (@Gr8fulTr8s) reported 45 minutes ago

  @SlackHQ issues connecting to a new workspace. Where can I get support?

• 
  y - alex ⚔️ (@onelonesabre) reported 46 minutes ago

  @SlackHQ @question_base can't use these features when your app is down my friend

• 
  Rahul Chetia (@ayoImNotTrippin) reported 48 minutes ago

  @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.

• 
  Johan Cutych (@johancutych) reported 48 minutes ago

  first you need to fix the rate limits @SlackHQ

• 
  LoopGantt (@loopgantt) reported 50 minutes ago

  @NotionHQ @SlackHQ Channel-scoped agents fix the biggest AI rollout blocker — broad access feels risky to admins. Smart default.

• 
  jbv 🌟 (@jbv) reported 52 minutes ago

  @SlackHQ liking the new activity view, still getting used to it. One thing: it doesn’t respect the “Just display names” setting. Is a fix coming? 👀

• 
  Jorge Modesto (@jorgemdsto) reported 54 minutes ago

  @peduarte Yes @SlackHQ messed something up recently. Search is terrible now.

• 
  Rab Memari (@rabmemari) reported 55 minutes ago

  @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

• 
  Corey Quinn (@QuinnyPig) reported 60 minutes ago

  @samlambert @joshmgross It’s almost impossible to mention a bug in Slack and get anyone at @SlackHQ to fix it.

• 
  Savi (@SaviPabla) reported 1 hour ago

  @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