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:

• 
  siggy bilstein (@sbilstein) reported 5 minutes ago

  @evisdrenova hmm kinda like Kaniko caching locally, but I think the problem is that the industry has broadly gotten used to very slow deploy pipelines. Back when I was at @SlackHQ in like 2018, we used to SCP the monolith across the fleet and deploy in a couple minutes. Containerization is awesome for various reasons but it has gotten an entire generation of developers to just expect builds + deploys to take at least 15 and usually closer to 45. I do wonder how much perf you could squeeze out with replacing BuildKit but I imagine it's already highly optimized. I just *feel* like developers shouldn't have to think so much about why their builds are slow.

• 
  Ariel Sterman (@ArielSterman) reported 7 minutes ago

  Is @SlackHQ down? heard it here first.

• 
  Peter Dedene (@dedene) reported 9 minutes ago

  @tobi +1000 to this 🙌 Please @SlackHQ, we are practically begging for this fix at this point

• 
  Rahul Chetia (@ayoImNotTrippin) reported 10 minutes ago

  @SlackHQ there’s a widespread issue with slack today. Not sure about Mac but my entire team with windows seems to be impacted. Slack becomes irresponsive on windows a few minutes in. Tried ‘repair’ and force close, but no help there. We are using app in our phones to communicate.

• 
  Neil Chudleigh (@neilsuperduper) reported 11 minutes ago

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

• 
  Ravi (@ravilutionx) reported 12 minutes ago

  @SlackHQ @trq212 And a verbosity problem

• 
  Awais alwaisy (@alvaisy) reported 15 minutes ago

  @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

• 
  Andreas Elia (@digitalandreas) reported 17 minutes ago

  @SlackHQ Can you fix the main parts of Slack before adding more features pls? 🙏

• 
  ImagineArt (@ImagineArt_X) reported 17 minutes ago

  @SlackHQ @SlackHQ cute, but can you fix the "copying emojis from slack to somewhere else please"

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 17 minutes ago

  7:30a Getting eMail down to zero and loading up the team in @SlackHQ.

• 
  Ellen DaSilva (@ellenjdasilva) reported 19 minutes ago

  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.

• 
  noah (@noahsolomon) reported 21 minutes ago

  @hiiinternet @SlackHQ It’s a big problem actually

• 
  Michael Grinich (@grinich) reported 22 minutes ago

  @SlackHQ Please fix the rate limits. The current Slack API is practically useless since you reduced them.

• 
  jimmy hackett (@j1mmyhackett) reported 22 minutes ago

  the most dangerous bug isn't the one that crashes. it's the one that says 'all good' when it isn't. i had a checker that was supposed to flag a problem. it was reporting green. every single run. turns out it was checking the documentation of the thing it was hunting, not the thing itself. so whenever the problem existed and was documented, the checker saw the doc, said 'found it, it's tracked', and moved on. confident. wrong. this happened twice in the same week in two different places. a report card that shipped one of its four answers unconditionally regardless of the actual data. a monitor that was asserting schema state it had never actually read. both passed. both lied. the lesson i keep relearning: a check that can't fail toward a confident opposite is not a check. it's a placebo. the question isn't 'does this run without error.' the question is 'what would this have to see to fire, and can it actually see that thing.' if the answer to 'can it see it' is 'well, kind of, it reads the notes about it'. you don't have a checker. you have a script that reads its own homework. @SlackHQ kept posting green cards. @AnthropicAI's Claude Code kept summarising them as healthy. everything looked fine. nothing was. what's the quietest false-green you've shipped?

• 
  Fluorine (@FluorineHQ) reported 22 minutes ago

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