1. Home
  2. Companies
  3. Slack
Slack

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.

  • 50% App Crashing (50%)
  • 50% Connection (50%)

Live Outage Map

The most recent Slack outage reports came from the following cities:

CityProblem TypeReport Time
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
Colorado Springs Messaging 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:

  • LukeHutchison
    Luke Hutchison (@LukeHutchison) reported

    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!

  • arashdehkordiHQ
    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?

  • SaviPabla
    Savi (@SaviPabla) reported

    @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

  • the_mewc
    mewc (@the_mewc) reported

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

  • qudnesa
    duh (@qudnesa) reported

    @SlackHQ @question_base why not fix your own agent first?

  • aguscruiz
    Agustín Ruiz (@aguscruiz) reported

    Hi @SlackHQ, can you please fix this notification dot issue? It's been bothering me for like a month or more already. It shows that I have something unread when I don't. Even hovering on it makes the dot go away when there's something unread. It's very annoying for people with "unread anxiety" like me lol. Thank you 🫶

  • j1mmyhackett
    jimmy hackett (@j1mmyhackett) reported

    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?

  • nutritogo
    Livleen Gill (@nutritogo) reported

    @SlackHQ - having a very difficult time with your product as a new customer. No help

  • ellenjdasilva
    Ellen DaSilva (@ellenjdasilva) reported

    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.

  • Gr8fulTr8s
    Kelly Carter (@Gr8fulTr8s) reported

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

  • iamTRA
    Rohan (@iamTRA) reported

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

  • FredsDaily
    HOURLY LIFE of Fred Campos (@FredsDaily) reported

    7:30a Getting email down to zero and loading both the website support and production teams in @SlackHQ.

  • SGN06380601
    SGN (@SGN06380601) reported

    @SlackHQ i need customer service help and am not getting a response from your agentforce. can you please help?

  • theodormarcu
    Theodor Marcu (@theodormarcu) reported

    Putting an agent in Slack creates a very different 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.

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

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

  • GosuCoder
    GosuCoder (@GosuCoder) reported

    Slackbot legit might be one of my favorite uses of AI outside of coding. I use this thing constantly to find past conversations, summarize entire chats, help write responses, look for things I might be forgetting, or even look up past context on a decision or topic. Seriously @SlackHQ this legit improves my life

  • downtownberlin
    Georg S. Kuklick (@downtownberlin) reported

    @SlackHQ @linear Then fix your MCP server!

  • CSO_Krytos
    KRYTOS (@CSO_Krytos) reported

    @Cal_Irvine @thdxr @SlackHQ threads are terrible

  • rodrigoberriel
    Rodrigo Berriel (@rodrigoberriel) reported

    @thdxr @SlackHQ unbelievable right? terrible ux

  • dhruv2038
    Dhruv (@dhruv2038) reported

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

  • merklejosh
    JM (@merklejosh) reported

    @SlackHQ There seems to be a bug in your Version 4.50.140 app (Mac) where if you have open a New message and you try to then click in the Search bar, you can't – it just flashes. Can you please fix this. It's very annoying. Thanks!

  • jason_alco
    Jason Alco (@jason_alco) reported

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

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

  • ayoImNotTrippin
    Rahul Chetia (@ayoImNotTrippin) reported

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

  • lenvioux
    ✩°。⋆⸜ (@lenvioux) reported

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

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

  • sampullara
    Sam Pullara (@sampullara) reported

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

  • mayberayyy
    mayberaigan (@mayberayyy) reported

    @SlackHQ your app notifications are glitching, please fix it

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