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.

  • 54% App Crashing (54%)
  • 31% Messaging (31%)
  • 8% Sign in (8%)
  • 8% Connection (8%)

Live Outage Map

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

CityProblem TypeReport Time
Ródos Messaging 24 days ago
Belo Horizonte Connection 28 days ago
Jewar App Crashing 29 days ago
Colorado Springs Messaging 29 days ago
South Point Sign in 1 month ago
Bismarck Messaging 1 month 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:

  • AgentAkki
    Akshay (✈️ NYC) (@AgentAkki) reported

    @RTFern @SlackHQ Sorry about that, Ryan! I work at slack. Tell me more about what’s not working for you?

  • coinandcrypto
    Dog (@coinandcrypto) reported

    @SlackHQ Most AI agents fail because they’re written by bloated enterprise teams who don’t really know what problem they’re solving.

  • JoshCaughtFire
    josh (@JoshCaughtFire) reported

    @peduarte @SlackHQ I like how the proposed community note is like ‘no they can’t’ then you read the slack docs and there is a self service export tool for org owners

  • douglas2428
    Douglas Liscano (@douglas2428) reported

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

  • PlotnikovDev
    Evgeny (@PlotnikovDev) reported

    @adilmania @SlackHQ What problem with slack? We use slack and discord.

  • Langerius
    LANGERIUS (@Langerius) reported

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

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

  • troy_ruediger
    Troy Ruediger (@troy_ruediger) reported

    @Benioff @scottastevenson @SlackHQ That’s so much easier than seeing business owners try and argue for their products usability. Could very well be user error but irrelevant after this approach. Both sides on the same team working to make things better. Very smooth MB.

  • franferbel
    F. Fernández-Beltrán (@franferbel) reported

    Hey @SlackHQ — it’s been 3 days waiting for a response from your Help Center. For a platform that sells efficiency and seamless communication, this feels… ironic. Is this really the standard for customer support? 🤔

  • omenosdev
    Mike Rochefort 🐧 (@omenosdev) reported

    @SlackHQ I've sent a message in via the feedback address, but for 4.50.136 either there's been an undisclosed change of GPG keys used in signing Linux packages or the wrong key was used accidentally. For environments with strict package verification this leads to install errors.

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

  • Gr8fulTr8s
    Kelly Carter (@Gr8fulTr8s) reported

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

  • YukanL
    Ken Liao (@YukanL) reported

    It's been almost 2 days since @SlackHQ deleted our company workspace without warning. Aside from a vague email a few months ago about migrating to a different reseller in our region, there was no communication at all leading up to the deletion. Support only responds with the same message template telling us to reach out to sales and hasn't responded to followups since yesterday. Some of the worst SaaS customer service I've ever experienced. What are the best alternatives to Slack?

  • yongqianme
    YQ (@yongqianme) reported

    SaaS will die because of @SlackHQ immediately shutting down the paid service. Self-hosted service with agent is the future!

  • wwitvoet
    Wouter Witvoet (@wwitvoet) reported

    @SlackHQ Been trying to migrate to Slack Enterprise Grid since January 28, only get non-descriptive errors and can't get anyone from your team on a Zoom for 15 mins to do the config. No help from support apart from reiterating the same URLs for SAML. What can you do to help?

  • abhi__katiyar
    Abhishek (@abhi__katiyar) reported

    @peduarte @SlackHQ Mental model to help people make right choices “all your communication will become public record if your company gets subpoenaed”

  • rhymezx_code
    Jide (@rhymezx_code) reported

    @SlackHQ Tell me why Slack desktop is not working on Ubuntu 26.04 ( Resolute Raccoon ) ??? Honestly i have tried o #Ubuntu

  • kyukxs
    Mutatyo (@kyukxs) reported

    New Slack Design is terrible. @SlackHQ can I revert to a previous version just a few updates from this one!

  • HotForMoot
    Riley Read-Only (@HotForMoot) reported

    Cmon @SlackHQ help the tfr

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

  • 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

  • dhruv2038
    Dhruv (@dhruv2038) reported

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

  • ahmedtokyo
    Tokyo (@ahmedtokyo) reported

    There’s this huge bug in slack where if you click on a draft message from your drafts on iPhone, Slack just fully deletes the draft message and opens an empty composer. This made me lose a lot of work. @SlackHQ you can fix this with claude. Just paste this tweet there.

  • grok
    Grok (@grok) reported

    @natochi_ @fdosmither @SlackHQ Based on the screenshot, I'm guessing that unread notification is a sneaky DM from someone in your workspace—maybe a quick question or a meme that's buried in the Activity tab. Slack's UI can be tricky; try filtering by "Select unreads" to hunt it down!

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

  • bkwebster
    Brandon Karl Webster (@bkwebster) reported

    @adilmania @SlackHQ Better alternatives exist - it’s used abundantly because of the mindshare and scale. The only replacement would be a totally new and obvious form factor that leads to the same outcome in a better way - not a better alternative to the same problem.

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

  • nlevin
    Noah Levin (@nlevin) reported

    @SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏

  • jakemor
    Jake Mor (@jakemor) reported

    can someone at @SlackHQ please for the love of god fix drag and drop to attach a file? how has this been an issue for months without anyone realizing? Steps to reproduce: Drag file to attach. Nothing happens. no file attached.

  • immehmetali
    Mehmet Ali (@immehmetali) reported

    @SlackHQ Context is necessary but not sufficient. The real bottleneck is decision architecture: knowing when to retrieve, when to reason, and when to act. More context doesn't fix a broken agent loop.