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:

  • m_salman_afzal
    Salman (@m_salman_afzal) reported

    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,

  • 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

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

  • m_salman_afzal
    Salman (@m_salman_afzal) reported

    @SlackHQ But whether they decide to act on it will depend how much they prioritize the issue. And this is what open source could become as well. We can only report but only their agent factories can now contribute. So, it kind of is closed source since no one is now reading the 100k loc

  • jbv
    jbv 🌟 (@jbv) reported

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

  • Krazed
    Krazed 🇵🇸 (@Krazed) reported

    @SlackHQ you have a degradation rn? unable to create channels and getting intermittent issues with events

  • kitlangton
    Kit Langton (@kitlangton) reported

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

  • douglas2428
    Douglas Liscano (@douglas2428) reported

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

  • tulumpo
    tulumpo (@tulumpo) reported

    $IOND still in pre-launch. second delay message, 10:31 and now 10:39. this is normal. "All NASDAQ systems are fully operational" is in the message. nothing is broken. direct listings open when price discovery settles, not on a clock. @coinbase, @SlackHQ and @Spotify all opened late too.

  • nutritogo
    Livleen Gill (@nutritogo) reported

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

  • 202409R
    miya (@202409R) reported

    @ManusAI @SlackHQ This kind of UX that charges users instantly without a clear confirmation step is unacceptable. @ManusAI please fix this and issue a refund. Users should NOT be charged $394 by mistake.

  • karrisaarinen
    Karri Saarinen (@karrisaarinen) reported

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

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

  • _THE__FUHRER
    VISHAL (@_THE__FUHRER) reported

    @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

  • humbledshuttler
    Subrat Prasad (@humbledshuttler) reported

    @SlackHQ please fix huddles on android.

  • AgentC_006
    Chimene | Dantown (@AgentC_006) reported

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

  • eoslick
    Evan Oslick (@eoslick) reported

    Anyone know how to gert @SlackHQ support? I've got a bit of a lingering issue that I'm not sure how do deal with due to ownership of Slack deployment.

  • philliphaydon
    🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported

    Its really disappointing that @SlackHQ status page suggests its up, when it's clearly down and you can get up to date status from X users who are reporting the same issues.

  • mayberayyy
    mayberaigan (@mayberayyy) reported

    @SlackHQ your app notifications are glitching, please fix it

  • 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

  • vasundhar
    Son of Earth (@vasundhar) reported

    @SlackHQ there is issue with your cache where you store message send failure and likes

  • Cap039
    Captain (@Cap039) reported

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

  • HamidAli
    Hamid Ali (@HamidAli) reported

    Uh is @SlackHQ having issues…? 👀 #Slack

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

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

    8a On my morning @Zoom with Jbazmine. Planning out the day, so we can work out the plan. Going through and getting eMail down to zero and assigning tasks in @SlackHQ.

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

  • qudnesa
    duh (@qudnesa) reported

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

  • Watching1776
    TheHardTruth (@Watching1776) reported

    @SlackHQ You need to fix that app so it stops putting people into Auto Silence repeatedly without touching anything. Your code is trash

  • ravilutionx
    Ravi (@ravilutionx) reported

    @SlackHQ @trq212 And a verbosity problem

  • sbilstein
    siggy bilstein (@sbilstein) reported

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