Slack Outage Map

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:

• 
  Akshay (✈️ NYC) (@AgentAkki) reported 1 minute ago

  @kurushdubash @patriciosainzr @SlackHQ 👋I work at Slack. Could you share a screenshot or more details on what's not working?

• 
  Q (@quionie) reported 2 minutes ago

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

• 
  Ravi (@ravilutionx) reported 6 minutes ago

  @SlackHQ @trq212 And a verbosity problem

• 
  Salman (@m_salman_afzal) reported 6 minutes ago

  @SlackHQ But whether they decide to act on it will depend how much they prioritize the issue. And this is what open source could become as well. We can only report but only their agent factories can now contribute. So, it kind of is closed source since no one is now reading the 100k loc

• 
  Subrat Prasad (@humbledshuttler) reported 7 minutes ago

  @SlackHQ please fix huddles on android.

• 
  Johan Cutych (@johancutych) reported 9 minutes ago

  first you need to fix the rate limits @SlackHQ

• 
  Rob Swift (@RobSwish) reported 10 minutes ago

  @AgentAkki @SlackHQ Restarting doesn't help, and I mentioned this in the dms, it seems so weird to basically have 2 dm lists.

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 12 minutes ago

  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.

• 
  Peval 🇮🇹 🇪🇺 🇬🇧🏳️‍🌈 (@jabawack81) reported 18 minutes ago

  @gabsmashh Once nearly turned down a job interview because the invite came through @MicrosoftTeams. Spent the whole call trying to casually work out if they used @SlackHQ instead. They did.

• 
  SeattleViewHomes (@SeattleViewHome) reported 24 minutes ago

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

• 
  jimmy hackett (@j1mmyhackett) reported 27 minutes ago

  i shipped a report that posted a PDF to @SlackHQ with buttons to approve or flag it. worked great in testing. turns out every single report was re-sharing the exact same file. Next.js had cached the upload URL on the first request and just kept reusing it. so every property got the same PDF. same charts. same data. looked fine in the message. was completely wrong. the fix was straightforward once i saw it. but i only saw it because i added logging on the upload path and watched what Slack was actually returning. without that i would have kept assuming the reports were right. this is the thing that keeps biting me. i build something, it posts, the message looks correct, and i ship it. but "the message looks correct" is not the same as "the data is correct". i need the system to surface the difference, not just tell me a message was sent. the reports now work the way they were supposed to. one message per property, each with its own PDF, two models reading it and leaving grades in the thread. the buttons are how you reply to the report, not how you open it. but i almost shipped a monitoring system that was monitoring nothing. it was just confidently showing me the same snapshot on repeat. what is the dumbest caching bug you have hit in ****?

• 
  jimmy hackett (@j1mmyhackett) reported 27 minutes ago

  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?

• 
  Assaf Kipnis (@Kipnis_a) reported 30 minutes ago

  Claude is the best corporate CYA buddy I used to have full CYA files with records of messages, emails and things I did - I was terrible at keeping those and people took advantage of that. With Claude and @meetgranola - I have canonical record of all conversations, @SlackHQ messages, emails, canonical decisions - everything Oh, you say I didnt do something? I didnt respond? Here come the receipts

• 
  Angelo 🇵🇷 (@ngeloxyz) reported 33 minutes ago

  @chrismunns @SlackHQ lmao its broken for me too I am using Railway's client for Slack now + Beeper for DMs.

• 
  Alexander Cranga (@alexandercranga) reported 33 minutes ago

  /copy from Claude -> paste in Slack -> doesn’t keep the formatting. @SlackHQ please fix