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.

  • 33% App Crashing (33%)
  • 33% Messaging (33%)
  • 22% Connection (22%)
  • 11% Sign in (11%)

Live Outage Map

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

CityProblem TypeReport Time
New York City App Crashing 11 days ago
Brest Connection 1 month ago
Ródos Messaging 2 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:

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

  • alexandercranga
    Alexander Cranga (@alexandercranga) reported

    /copy from Claude -> paste in Slack -> doesn’t keep the formatting. @SlackHQ please fix

  • kyukxs
    Mutatyo (@kyukxs) reported

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

  • gaspardlezin
    Gap | Suby (@gaspardlezin) reported

    Can someone please buy @SlackHQ and shut it down? This platform is horrible.

  • mayberayyy
    mayberaigan (@mayberayyy) reported

    @SlackHQ your app notifications are glitching, please fix it

  • MohschinoKhan
    AK (@MohschinoKhan) reported

    @daveamsterdam20 @SlackHQ Same issue here wtf is going on!! @SlackHQ

  • YouPulseX
    Paul Sant · Telecodex (@YouPulseX) reported

    @pizzaboy @karrisaarinen @SlackHQ Then "project channel" is a default, not a scope. The issue list command still follows the caller's workspace visibility.

  • QuinnyPig
    Corey Quinn (@QuinnyPig) reported

    @samlambert @joshmgross It’s almost impossible to mention a bug in Slack and get anyone at @SlackHQ to fix it.

  • tyhouch
    Tyler (@tyhouch) reported

    yo @SlackHQ please add support for viewing .html files in chat. everyones tossing these around and the download->open in chrome friction is slowing me down bigtime

  • ngeloxyz
    Angelo 🇵🇷 (@ngeloxyz) reported

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

  • iamTRA
    Rohan (@iamTRA) reported

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

  • douglas2428
    Douglas Liscano (@douglas2428) reported

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

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

    7:30a Back home, getting the boys up, getting eMail down to zero, loading the team up with today's support and production website work (in @SlackHQ).

  • 67steinip
    Steini (@67steinip) reported

    @kitayoshi_son @SlackHQ We've sent 2 emails so far nothing, they arent going to respond to you because this is a MASS event, you arent alone, we didnt even get the email people talk about and some others say that as well, we just got wiped. I don't think they will help you.

  • downtownberlin
    Georg S. Kuklick (@downtownberlin) reported

    @SlackHQ @linear Then fix your MCP server!

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

    7:30a Getting eMail down to zero, passing out assignments in @SlackHQ

  • ArielSterman
    Ariel Sterman (@ArielSterman) reported

    Is @SlackHQ down? heard it here first.

  • Gr8fulTr8s
    Kelly Carter (@Gr8fulTr8s) reported

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

  • nlevin
    Noah Levin (@nlevin) reported

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

  • kitlangton
    Kit Langton (@kitlangton) reported

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

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

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

  • HotForMoot
    Riley Read-Only (@HotForMoot) reported

    Cmon @SlackHQ help the tfr

  • humbledshuttler
    Subrat Prasad (@humbledshuttler) reported

    @SlackHQ please fix huddles on android.

  • antonioventre_
    Antonio Ventre (@antonioventre_) reported

    @resulvol @RealFeatBit @SlackHQ Sure guys anyone who need help can text be and they’ll restore your access for 30 days so you can still work on the account while the migrate

  • AadityaPasayat
    Aadii (@AadityaPasayat) reported

    @raidingAI @SlackHQ @slashyai I am sorry to say, but u don't have taste, either the editor. R eyes go from left to right, common sense. Btw I can help u get taste

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

  • trentdotsol
    trent.sol (@trentdotsol) reported

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

  • teenmd
    Sophia Yen MD (@teenmd) reported

    .@SlackHQ Why don't you have human service agents? You are a GIANT company used by many. The only contact us is via a webform?

  • kitayoshi_son
    Kitayoshi (@kitayoshi_son) reported

    @alphato_o @SlackHQ Even a sticky banner hanging on the workspace saying “Your workspace will be shutting down” on the chat page would be better. They could even use the UI components for the 90-day limit. Today’s behavior makes it seem like they just don’t care.