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

• 
  Gary McMillian (@GaryMcMillianTX) reported 16 seconds ago

  @SlackHQ You need to fix your search before moving on to AI.

• 
  M. Yahia (@maddada) reported 3 minutes ago

  @aaditsh @adilmania @SlackHQ Same, it's 10 times better than discord, teams, hangout, zoom, etc. Not sure about newer apps but I literally have 0 issues with slack. It's really good with connect too if you work with external companies, beats email by light years.

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

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

• 
  Peter Dedene (@dedene) reported 4 minutes ago

  @tobi +1000 to this 🙌 Please @SlackHQ, we are practically begging for this fix at this point

• 
  VISHAL (@_THE__FUHRER) reported 5 minutes ago

  @SlackHQ @stewart Stewart Butterfield and his team were developing a game called "Glitch" in 2011 The Glitch was an ambitious and creative multiplayer game, but it struggled to find a large enough playerbase. They had to shut it down on 2012

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

  @RobSwish @SlackHQ Does restarting the app fix it?

• 
  Ravi (@ravilutionx) reported 12 minutes ago

  @SlackHQ @trq212 And a verbosity problem

• 
  Tyler (@tyhouch) reported 13 minutes ago

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

• 
  The Mishmash Cat (@TheMishmashCat) reported 20 minutes ago

  [1/5] Your #brain cannot multithread. When you switch from writing code to answering a @SlackHQ ping, your prefrontal cortex doesn't execute a clean parallel jump - it triggers an expensive, messy tear-down and rebuild process. You are burning raw compute.

• 
  LANGERIUS (@Langerius) reported 24 minutes ago

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

• 
  Luke Hutchison (@LukeHutchison) reported 25 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!

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

• 
  Theodor Marcu (@theodormarcu) reported 27 minutes ago

  Putting an agent in Slack creates a very different type of UX problem: it has to know when to shut up We spent a lot of time tuning when Devin should speak, stay quiet, or move work into a separate channel. Devin was the first agent to support Slack natively, so it was great to bring 2 years of those learnings to @SlackHQ for the Slack Code launch.

• 
  Alex Oppenheimer (@Alexoppenheimer) reported 28 minutes ago

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

• 
  Douglas Liscano (@douglas2428) reported 28 minutes ago

  @MatthewAry @github @SlackHQ Yes, we have the same problem today

• 
  A-Yo! despises APC (@AyomideAdenowo1) reported 29 minutes ago

  @daniielezeh @SlackHQ Bruhhh, valid question 😭 I've been having issues with the ******* video playback. I didn't even know it was possible to have worse video playback than twitter.

• 
  Jon Slemp (@Jon_Slemp) reported 31 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.

• 
  Jimidate (@Jimidvte) reported 39 minutes ago

  @SlackHQ, I’m having issues with my mobile notifications. I’ve checked every setting on my phone, uninstalled and reinstalled the app, yet I still don’t receive any push notifications. I’m missing time-sensitive information because I have to open the app before I see any updates.

• 
  Dhruv (@dhruv2038) reported 42 minutes ago

  Is @SlackHQ broken today - I am using Focus mode - seems like the emoticons are breaking.

• 
  Paul Thornton (@Fusspawn) reported 46 minutes ago

  @SlackHQ @dorukkavcioglu I miss the old glitch game, had fun with some of your old founders in that :(

• 
  Vortex (@mjparme) reported 46 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

• 
  Karri Saarinen (@karrisaarinen) reported 48 minutes ago

  @gustaf @ycombinator @SlackHQ I’d say Slack. Haven’t really experienced those issues you mention. Unless my internet is very bad. iMessage/whatsapp overly phone and counterparty focused so I’m more often wondering if the message actually got delivered or not and if the problem is me or them. Slack is more of a server and it doesn’t send the message if it doesn’t work.

• 
  Angelo 🇵🇷 (@ngeloxyz) reported 49 minutes ago

  @chrismunns @SlackHQ lmao its broken for me too I am using Railway's client for Slack now + Beeper for DMs.

• 
  Kit Langton (@kitlangton) reported 50 minutes ago

  @ferran9908 @SlackHQ Alas, this one is broken on desktop 😭 Every time a user responds, it disappears.

• 
  David Welch (@david_welch) reported 51 minutes ago

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

• 
  Vish (@vish_sh_) reported 51 minutes ago

  @SlackHQ Slack bot requires a proper fix first.

• 
  Awais alwaisy (@alvaisy) reported 51 minutes ago

  @adilmania @SlackHQ what's wrong with slack. bunch of alternatives. each one made money. slack is still stable and useful. i don't have any issue with slakc except limited message history for free users

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 52 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.

• 
  Ellen DaSilva (@ellenjdasilva) reported 56 minutes ago

  Sketchy behavior: Someone from @SlackHQ joined my company channel last week saying "we're here to help you with the product" (we're not having issues). Then today started pestering me about an overdue invoice (we don't have one). Beyond violating. Shameful behavior @salesforce.

• 
  Savi (@SaviPabla) reported 59 minutes 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