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:

  • Gr8fulTr8s
    Kelly Carter (@Gr8fulTr8s) reported

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

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

  • Jon_Slemp
    Jon Slemp (@Jon_Slemp) reported

    Bug report for you @SlackHQ — when receiving a DM notification from Agents, and those agents are setup as Slack apps you have to DM directly in an app channel, once you hit a certain number of chats in your history tab you can no longer navigate to the DM directly by clicking the DM notification on mobile. You basically get navigated to a blank screen and effectively chat find the message ever. Please fix. This is a disaster of a bug.

  • alexei_sid
    Alex Sidorenko (@alexei_sid) reported

    @Moore_Irish @salesforce @SlackHQ Pricing changes that reduce admin control while pushing AI features rarely improve outcomes. The real test: does the AI actually help teams make faster, better decisions, or is it just another feature tax masquerading as innovation?

  • qudnesa
    duh (@qudnesa) reported

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

  • MohschinoKhan
    AK (@MohschinoKhan) reported

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

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

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

  • douglas2428
    Douglas Liscano (@douglas2428) reported

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

  • Cap039
    Captain (@Cap039) reported

    @SlackHQ One recent Slack regression: If you edit a post that contains a link, the link preview disappears. Please fix this 🙏

  • udaysubbarayan
    Uday Subbarayan (@udaysubbarayan) reported

    @SlackHQ Pl don’t hide the URL’s. Your recent overdoing here is creating problems Thanks

  • 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

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

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

  • FluorineHQ
    Fluorine (@FluorineHQ) reported

    @gustaf @SlackHQ Reliability is the floor, not the ceiling. Slack hit the floor and is now adding notification noise to mask it — classic engagement-metric trap. The deeper issue: messaging apps stopped being where work happens and became where work gets talked about. That's the gap worth solving.

  • PlotnikovDev
    Evgeny (@PlotnikovDev) reported

    @adilmania @SlackHQ What problem with slack? We use slack and discord.

  • Fusspawn
    Paul Thornton (@Fusspawn) reported

    @SlackHQ @dorukkavcioglu I miss the old glitch game, had fun with some of your old founders in that :(

Check Current Status