1. Home
  2. ❯
  3. Companies
  4. ❯
  5. 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.

  • 40% App Crashing (40%)
  • 30% Messaging (30%)
  • 20% Connection (20%)
  • 10% Sign in (10%)

Live Outage Map

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

CityProblem TypeReport Time
New York City App Crashing 5 days ago
Brest Connection 25 days ago
RΓ³dos Messaging 2 months ago
Belo Horizonte Connection 2 months ago
Jewar App Crashing 2 months ago
Colorado Springs Messaging 2 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:

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

  • bradbeckett
    Brad Beckett (@bradbeckett) reported

    With how much sensitive data @SlackHQ stores, it's surprising they don't yet support Passkey login or have a BIMI email verification certificate so their legitimate emails get a blue verified check mark in major email service providers. @digicert pls reach out to them!

  • Gr8fulTr8s
    Kelly Carter (@Gr8fulTr8s) reported

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

  • HotForMoot
    Riley Read-Only (@HotForMoot) reported

    Cmon @SlackHQ help the tfr

  • iamTRA
    Rohan (@iamTRA) reported

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

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

  • downtownberlin
    Georg S. Kuklick (@downtownberlin) reported

    @SlackHQ @linear Then fix your MCP server!

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

  • j1mmyhackett
    jimmy hackett (@j1mmyhackett) reported

    the scariest bugs in an agent system aren't the ones that crash loudly. they're the ones that succeed. quietly. and then stop. and you don't find out for three days. this week i shipped `fix(daily): heartbeat + agent-health for the daily-report jobs` (commit 10c954a). the cron had been running. the launchd plist was registered. no errors in the log. but the report wasn't landing in @SlackHQ. it took me longer than i want to admit to realize the job had silently stopped delivering. no crash, no alert, just absence. the mental model i pulled from it: a job that runs is not the same as a job that works. completion and correctness are two different signals, and most infra only monitors the first one. heartbeats fix this. you instrument the output, not just the process. if the report doesn't land by 8:05am, something fires. you stop trusting the scheduler and start verifying the result. this applies way past cron jobs. any pipeline where you only watch for failure will eventually drift silently into uselessness. the absence of an error is not evidence of health. once i wired heartbeats into the @AnthropicAI-powered agent fleet, i found two other jobs that had the same problem. they looked fine. they weren't. if you're running automated jobs and you're not monitoring outputs, you're not monitoring. what's the longest a silent failure ran in your system before you caught it?

  • giskyexplorer
    Giuseppe Skyline (@giskyexplorer) reported

    @gustaf @SlackHQ Notifications are the bandaid for broken reliability. WhatsApp stays quiet because it works.

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

  • johancutych
    Johan Cutych (@johancutych) reported

    first you need to fix the rate limits @SlackHQ

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

  • ImagineArt_X
    ImagineArt (@ImagineArt_X) reported

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

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

  • 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

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

    @kurushdubash @patriciosainzr @SlackHQ πŸ‘‹I work at Slack. Could you share a screenshot or more details on what's not working?

  • Fusspawn
    Paul Thornton (@Fusspawn) reported

    @SlackHQ @dorukkavcioglu I miss the old glitch game, had fun with some of your old founders in that :(

  • darcy_jpa
    Darcy (@darcy_jpa) reported

    @SlackHQ @linear @cursor_ai Slack is a garbage product. Everything about it is trash. The reliability is trash, the support is trash, and the way you handle users is absolute trash. Impressive how consistently terrible you manage to be.

  • digitalandreas
    Andreas Elia (@digitalandreas) reported

    @cyberomin @SlackHQ Just to name a few: - Randomly opening channels a few miles up in the chat so I have to go all the way back down again - Right-click context menus are all over the place and inconsistent - Ghost notifications that show up randomly with no notification to go alongside them

  • stacheFonzi
    Stache (@stacheFonzi) reported

    It's from 2011, but I still miss Glitch. It was a browser based MMO based on collecting and crafting. Crazily enough it was made by the company that went on to rebrand and make @SlackHQ. The messaging system in the game became the basis for Slack.

  • asifmghafoor
    Asif (@asifmghafoor) reported

    Hi @SlackHQ out workspace (Spacious) has been deleted by mistake - no notification or emails or anything. We need this restored with history. Can someone please help? We have sent several support requests over the past few hours and no one has responded

  • IncredibleTrade
    IT (@IncredibleTrade) reported

    Is @SlackHQ mobile app down?

  • karrisaarinen
    Karri Saarinen (@karrisaarinen) reported

    @gustaf @ycombinator @SlackHQ What is degrading? WhatsApp imo is not a good example. Can’t even hold login on a desktop, and have to auth with your phone. Sync not super reliable either

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

  • Jon_Slemp
    Jon Slemp (@Jon_Slemp) reported

    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.

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

  • trentdotsol
    trent.sol (@trentdotsol) reported

    @cavemanloverboy @alessandrod @SlackHQ i did. it's the ones who won't that are the problem

  • heathermhuang
    heatherm.eth (@heathermhuang) reported

    @SlackHQ need urgent help our active Slack workspace suddenly got deleted.

  • kyukxs
    Mutatyo (@kyukxs) reported

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