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 (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	5 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:

• 
  jimmy hackett (@j1mmyhackett) reported 5 minutes ago

  i 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 ****?

• 
  Captain (@Cap039) reported 6 minutes ago

  @SlackHQ One recent Slack regression: If you edit a post that contains a link, the link preview disappears. Please fix this 🙏

• 
  knut (@kmelve) reported 6 minutes ago

  Now that @SlackHQ Code is a thing, will they finally ship Glitch out of flash?

• 
  ImagineArt (@ImagineArt_X) reported 10 minutes ago

  @SlackHQ @SlackHQ cute, but can you fix the "copying emojis from slack to somewhere else please"

• 
  Alexander Cranga (@alexandercranga) reported 11 minutes ago

  /copy from Claude -> paste in Slack -> doesn’t keep the formatting. @SlackHQ please fix

• 
  IT (@IncredibleTrade) reported 13 minutes ago

  Is @SlackHQ mobile app down?

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

  8:30a Back at my desk, loading the team up in @SlackHQ with today's assignment, getting eMail down to zero.

• 
  LoopGantt (@loopgantt) reported 16 minutes ago

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

• 
  Drew Hirschi (@ashirsc) reported 16 minutes ago

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

• 
  M. Yahia (@maddada) reported 16 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.

• 
  Sam Pullara (@sampullara) reported 17 minutes ago

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

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

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

• 
  Björne 🇸🇪🏋️‍♂️ (@SilchQuatch) reported 20 minutes ago

  @QuinnyPig @SlackHQ Every single unwarranted notification births months of hate inside of me. Literally anti-ads for me, any pattern of it and I immediately remove the service. I guess it has to work or it wouldn't be done?

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

• 
  Josh Ellithorpe (@zquestz) reported 22 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.

• 
  Taha Tesser (@TahaTesser) reported 27 minutes ago

  @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

• 
  Rab Memari (@rabmemari) reported 28 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

• 
  mewc (@the_mewc) reported 28 minutes ago

  @SlackHQ lots of bugs and issues right now. Can't create channels and lots of jankyness. This release is a lot.

• 
  Johan Cutych (@johancutych) reported 32 minutes ago

  first you need to fix the rate limits @SlackHQ

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

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

  7:30a Getting eMail down to zero and loading up the team in @SlackHQ.

• 
  Tulip 🌷 ☮️ (@imTulip) reported 44 minutes ago

  Is @SlackHQ down?

• 
  Travis Peters (@SivvyRat) reported 45 minutes ago

  @SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.

• 
  Rahul Chetia (@ayoImNotTrippin) reported 47 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.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 47 minutes ago

  @purionx @SlackHQ @salesforce tables in slack would genuinely help, wild that it took this long to even be a request

• 
  jimmy hackett (@j1mmyhackett) reported 50 minutes ago

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

• 
  Corey Quinn (@QuinnyPig) reported 53 minutes ago

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

• 
  Georg S. Kuklick (@downtownberlin) reported 55 minutes ago

  @SlackHQ @linear Then fix your MCP server!

• 
  Jason Alco (@jason_alco) reported 55 minutes ago

  @SlackHQ Our team loves the platform, but we really need to fix the mark unread feature. It’s been broken for years now. First, you should be able to mark a channel as unread without opening the channel and selecting a message. Second, half the time marking a message as unread doesn’t work. I have to go message by message, trying over and over until one works. Please fix this, thank you 🫠