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:

  • neilsuperduper
    Neil Chudleigh (@neilsuperduper) reported

    .@SlackHQ this message pops whenever i try to do any navigation. persists across restarts. also please fix the search results ↓ keypress issue, the first ↓ is being eaten by the system so when I am moving fast I am constantly going to the wrong place you need to make sure bugs like this dont continue, you have serious competition coming that is going to take business from you if you continue to let your product rot.

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

  • 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

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

    6:30a Got eMail down to zero, and started the team with assignments in @SlackHQ.

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

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

    8:30a Back at my desk, loading the team up in @SlackHQ with today's assignment, getting eMail down to zero.

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

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

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

  • disismohi
    Mohi (@disismohi) reported

    @SlackHQ: 40% less merge queue time, CI type-checking down from 7.5 minutes to 1.25 minutes. Canva: 58s to first error in the editor down to 4.8s.

  • iamTRA
    Rohan (@iamTRA) reported

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

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

  • imTulip
    Tulip 🌷 ☮️ (@imTulip) reported

    Is @SlackHQ down?

  • onelonesabre
    y - alex ⚔️ (@onelonesabre) reported

    @SlackHQ @question_base can't use these features when your app is down my friend

  • ravilutionx
    Ravi (@ravilutionx) reported

    @SlackHQ @trq212 And a verbosity problem

  • rodrigoberriel
    Rodrigo Berriel (@rodrigoberriel) reported

    @thdxr @SlackHQ unbelievable right? terrible ux

Check Current Status