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:

  • vladoustinov
    Vlad (@vladoustinov) reported

    @MerlinEgalite @SlackHQ The problem is they gave up on product a long time ago haha But yes embedding tools/workflows inside interfaces people are already used to use (slack/email/Notion etc) is the way to go

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

  • dbrogdon
    Darrell Brogdon (@dbrogdon) reported

    Yesterday I signed up for a service. Today, all my @SlackHQ had a notification asking if I wanted to connect some bot of that service to my Slack accounts. One thing has nothing to do with the other, as far as I'm concern. If this keeps up, I'll delete all of my Slack accounts.

  • qudnesa
    duh (@qudnesa) reported

    @SlackHQ @question_base why not fix your own agent first?

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

  • SeattleViewHome
    SeattleViewHomes (@SeattleViewHome) reported

    @MadronaVentures @SlackHQ @salesforce Should we expect investment & AI to be doubling down on the green economy now that no one credible is promoting the fossil fuel/engineered obsolescence economies to be sustainable or even beneficial?

  • luigiremor
    Luigi ➔ nora.finance (@luigiremor) reported

    @discord @beeper I think I won't have this issue with @SlackHQ...

  • iamTRA
    Rohan (@iamTRA) reported

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

  • loopgantt
    LoopGantt (@loopgantt) reported

    @NotionHQ @SlackHQ Channel-scoped agents fix the biggest AI rollout blocker — broad access feels risky to admins. Smart default.

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

  • kzer_ai
    kzer_AI (@kzer_ai) reported

    @OpenAI @linear @SlackHQ The agent that pulls context from docs, email, chats, and code to update your Linear ticket: "status: someone else's problem"

  • NWFreeZone
    Richard Casimir (@NWFreeZone) reported

    @xsupport @slackHQ X links on slack (android) Still not working. All other sites redirect properly from slack. Just NOT X.

  • rodrigoberriel
    Rodrigo Berriel (@rodrigoberriel) reported

    @thdxr @SlackHQ unbelievable right? terrible ux

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

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

Check Current Status