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:

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

  • casspa
    Cass Anderson (@casspa) reported

    @Yonar87 @SlackHQ same issue here. Just sent them an email. Their status landing page says they've been 100% find this quarter which makes me think maybe they just don't update that page?

  • ravilutionx
    Ravi (@ravilutionx) reported

    @SlackHQ @trq212 And a verbosity problem

  • alvaisy
    Awais alwaisy (@alvaisy) reported

    @adilmania @SlackHQ what's wrong with slack. bunch of alternatives. each one made money. slack is still stable and useful. i don't have any issue with slakc except limited message history for free users

  • kurushdubash
    Kurush Dubash (@kurushdubash) reported

    @SlackHQ can you please revert your most recent update, it is so bad. This is terrible for anyone who is inbox 0. Please don't make me use Teams

  • ArielSterman
    Ariel Sterman (@ArielSterman) reported

    Is @SlackHQ down? heard it here first.

  • kyukxs
    Mutatyo (@kyukxs) reported

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

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

    8:30a Loading up the team in @SlackHQ and getting eMail down to zero. Planning out the day, so I can work out the plan.

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

  • digitalandreas
    Andreas Elia (@digitalandreas) reported

    @johnbarker @SlackHQ Doesn't feel like they are. We've had a bunch of pre-existing issues for a while now (I replied to the other fella in the tweet with examples).

  • gregboyd
    Greg Boyd / WGBOYD (@gregboyd) reported

    @SlackHQ What are the chances we can cut down the number of clicks to start a huddle from four to say… one? Driving me crazy. 🙏🏻

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

  • 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

  • iceman_ome
    wanderingwanderer (@iceman_ome) reported

    .@SlackHQ and @Jira have the weirdest integration possible. Have spent the last 15 mins trying to remove jira app from Slack, but unable to. Can someone more knowledgeable help?

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

Check Current Status