1. Home
  2. ❯
  3. Companies
  4. ❯
  5. Slack
  6. ❯
  7. Outage Map
Slack

Slack Outage Map

The map below depicts the most recent cities worldwide where Slack users have reported problems and outages. If you are having an issue with Slack, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Slack users affected:

Less
More
Check Current Status

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.

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
New York City, NY 1
Brest, Brittany 1
Check Current Status

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:

  • 4kingtheworld
    kingoftheworld (@4kingtheworld) reported

    @antonioventre_ @SlackHQ Hey man, I’d really appreciate help getting Slack restored. I’ve got a company with 40 employees and it’s catastrophic man anything you can do to help Tried dming but it didn’t work

  • 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

  • quionie
    Q (@quionie) reported

    @thdxr @SlackHQ ohhh i’m so down for this because this would be MUCH better lol

  • iamTRA
    Rohan (@iamTRA) reported

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

  • TheMishmashCat
    The Mishmash Cat (@TheMishmashCat) reported

    [1/5] Your #brain cannot multithread. When you switch from writing code to answering a @SlackHQ ping, your prefrontal cortex doesn't execute a clean parallel jump - it triggers an expensive, messy tear-down and rebuild process. You are burning raw compute.

  • TeaseTech
    Bad **** (@TeaseTech) reported

    @thdxr @SlackHQ What's the problem?

  • calvinclee
    Calvin Lee (@calvinclee) reported

    @SlackHQ the mobile app has significantly regressed. why do I have a DM tab and an activity tab that only lets me filter down to DMs again? I want to easily filter for mentions.

  • jbv
    jbv 🌟 (@jbv) reported

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

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

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

  • RaziAns14640044
    Razi Ansari (@RaziAns14640044) reported

    @SlackHQ should fix the UX of their video player. It's one of the worst pieces of UX I've ever interacted with. It feels like I suddenly landed on some government app. Too messy

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

  • ivadapav
    rushikesh (@ivadapav) reported

    @SlackHQ down. What's next?

  • OneTrueHomie
    𝐎𝐧𝐞𝐓𝐫𝐮𝐞𝐇𝐨𝐦𝐢𝐞(👑,👑) (@OneTrueHomie) reported

    isn't this the same problem @PromptQL promised @sama in order to kill @SlackHQ ?

Check Current Status