1. Home
  2. Companies
  3. Slack
Slack

Slack status: messaging issues and outage reports

Service-wide status: Slack

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

Slack signals over the past 24 hours. The dashed line is the service-wide baseline used to detect unusual activity.

  • Service-wide signals
  • Service-wide baseline

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.

  • 40% App Crashing (40%)
  • 20% Messaging (20%)
  • 20% Connection (20%)
  • 20% Video (20%)

Live Outage Map

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

CityProblem TypeReport Time
Township of Evan Messaging 13 days ago
Township of Evan App Crashing 15 days ago
Guayaquil Video 20 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:

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

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

  • JohnHarnett
    John Harnett (@JohnHarnett) reported

    @cyberomin @digitalandreas @SlackHQ If you've filed a bug with them on the last 5 years and arent a big co then you'd know. They dont fix stuff just because it's broken.

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

    8:30a Got Daniel dropped off and heading back to my office to load the team up in @SlackHQ and get eMail down to zero.

  • maddada
    M. Yahia (@maddada) reported

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

  • kzer_ai
    kzer_AI (@kzer_ai) reported

    @OpenAI @linear @SlackHQ The agent that pulls context from docs, email, chats, and code to update your Linear ticket: "status: someone else's problem"

  • 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

  • teostealth
    Teo Vanyo Adiputra (@teostealth) reported

    @karrisaarinen @SlackHQ The handoff from Slack discussion to actual tracked issue is where most teams drop the ball - keeping that loop tight is harder than it sounds.

  • mjparme
    Vortex (@mjparme) reported

    @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

  • adilmania
    Adil Mania. (@adilmania) reported

    @NebulaAI @safizaq @SlackHQ discord integration is kinda broken, like i keep having "nebula" links showing, if you can fix that, that will be perfect.

  • MotivatingPeng
    TT 😋 (@MotivatingPeng) reported

    @OpenAIDevs @googledrive @SlackHQ Can we fix Codex.... When it does a context automatically compacted it stops what its doing

  • mutru
    Otto Hilska (@mutru) reported

    @SlackHQ The new Activity view is an amazing improvement. One thing that would make it better: the same thread can appear multiple times (for example the original post and a reply). It would help to allow deduplicating threads from the list.

  • MozzyFX
    Leon (@MozzyFX) reported

    Please @SlackHQ can you add a proper GIF selector I need to send better gifs right after I take down production

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

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

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

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

    6a Getting eMail down to zero, loading up the team is @SlackHQ. Planning the day, so I can work the plan.

  • Domino_mys
    Domino Mysłowski (@Domino_mys) reported

    There 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

  • Manoj____Yadav
    Manoj Yadav (@Manoj____Yadav) reported

    @TheNickBigar @CricTalk29 @SlackHQ No it doesn’t track time, you need to tell the time spent via message. Example- worked on X for 30 mins - remind me about checking the production issue around 3 pm The idea is to reduce friction for users on how they track time and tasks

  • casspa
    Cass Anderson (@casspa) reported

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

  • ngeloxyz
    Angelo 🇵🇷 (@ngeloxyz) reported

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

  • downtownberlin
    Georg S. Kuklick (@downtownberlin) reported

    @SlackHQ @linear Then fix your MCP server!

  • _bhuvanesh_
    Bhuvanesh Sridharan (@_bhuvanesh_) reported

    as much hate @MicrosoftTeams gets, at least the meeting chat and other chats are on the same platform. Absence of synergy between @SlackHQ chat and Google meet is such a pet peeve. Non issue in grand scheme but still bothering whenever people send links in gmeet.

  • getbluejay_ai
    Bluejay (@getbluejay_ai) reported

    Bluejay AI can now act in @SlackHQ, not just answer. Run a simulation. Check how production calls went overnight. Resolve the issues that caused the failures. All from the channel your team is already in. Test, monitor, and improve your agents. Now in Slack. Led by Ronniel Gandhe.

  • FluorineHQ
    Fluorine (@FluorineHQ) reported

    @gustaf @SlackHQ Reliability is the floor, not the ceiling. Slack hit the floor and is now adding notification noise to mask it — classic engagement-metric trap. The deeper issue: messaging apps stopped being where work happens and became where work gets talked about. That's the gap worth solving.

  • HamidAli
    Hamid Ali (@HamidAli) reported

    Uh is @SlackHQ having issues…? 👀 #Slack

  • SGN06380601
    SGN (@SGN06380601) reported

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

  • cathrynlavery
    Cathryn (@cathrynlavery) reported

    @Shopify @klaviyo @SlackHQ The Non-Technical Technical Dictionary, Day 2: Frontend & Backend Every app has a front of house and a back of house. Same as a restaurant. The frontend is what you see and touch. Think of Amazon, or any website you use. → The menu bar, the buttons, the search box. Everything on screen is just a list of things you're allowed to ask for. That's the menu, the dining room, the host stand. But nothing on that menu is actually happening at your table. When you hit "Buy Now," it's like placing an order with a waiter. He walks it back, the kitchen cooks it, and he brings it out when it's ready. The backend = the kitchen. You'll find database, business logic, server. Anything heavy (pulling your order history, processing a payment, sending an email) happens back there. The frontend only handles what fits at the table: how the buttons look, what color the page is, the small animations etc. Think Michelin star. They're not torching your steak tableside. They need the walk-in, the grill, the prep station, the sous chef. Software is the same. The interesting work needs the full kitchen. When a service like Cloudflare or AWS goes down and takes half the internet with it, that's a backend problem. The ghost kitchen caught fire and every restaurant relying on it went dark. A frontend problem is the one you've seen a hundred times: a button that won't click, text piled on top of an image, a page that looks broken on your phone. Frontend is form, where backend is function.

  • dhruv2038
    Dhruv (@dhruv2038) reported

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

  • aunder
    April Underwood (@aunder) reported

    In this day and age of infosec threats, this subject line from @SlackHQ is a bad call. After the brief cortisol spike that someone using the name Miles Davis had joined our Slack, I scrolled down, and then just wondered why on earth I would want this in my work communication tool.

  • hey_amandam
    Amanda (@hey_amandam) reported

    @TejasKumar_ @SlackHQ Yes 👏 The issue with this (and all things like it) for me is that there seems to be some idea that anyone sees "AI" and immediately associates that with some value. What user pain of mine are you solving? I literally do not care if you are using AI or not to solve it, I just want the best experience. Explore AI as a cta is a waste of space and my mental energy

Slack detected incident history

These records describe service-wide increases in reported problems. They do not confirm an outage at every address. Recorded end times describe our detection window, not a provider-confirmed repair.

  • Detected:
    Detection ended: (11 minutes)
  • Detected:
    Detection ended: (71 minutes)
  • Detected:
    Detection ended: (70 minutes)
  • Detected:
    No end recorded. This alone does not establish the current status.
  • Detected:
    No end recorded. This alone does not establish the current status.
  • Detected:
    No end recorded. This alone does not establish the current status.

What to do if Slack is not working

Compare your issue with the local reports and map. Note the affected service and when the problem began before contacting Slack; report your own experience using the report button above.

How to interpret these reports

Direct reports are submitted by visitors. Locations may be estimated from their connection or supplied by the reporter. A low local count does not establish that service is working; the service-wide status and local report totals describe different areas. How our outage detection works