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:

• 
  mayberaigan (@mayberayyy) reported 5 minutes ago

  @SlackHQ your app notifications are glitching, please fix it

• 
  LoopGantt (@loopgantt) reported 6 minutes ago

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

• 
  Ari Dehkordi (@arashdehkordiHQ) reported 8 minutes ago

  @karrisaarinen @SlackHQ Did Linear do this before agents? I tried project-level Slack channels at my org and found it works for enterprise engagements nicely, but breaks down at feature/epic level projects for our SaaS. There's a granularity sweet spot, too fine and context switching costs spike. Too coarse and projects blur. Plus no project is actually isolated in small teams, so cross-project conversations forced more people onto each channel and productive engagement suffered. I get the AI context-confinement angle, but curious what other benefits you're seeing?

• 
  David Welch (@david_welch) reported 11 minutes ago

  Hey @SlackHQ, there's some talk in the security community about the world is sorta burning down and we need a new space for community discussion. Would you ever donate to help a very highly visible space? You'd be next to names like IBM/Dell/Microsoft/etc. DMs open to chat

• 
  Conor Bronsdon (@ConorBronsdon) reported 11 minutes ago

  .@SlackHQ is building for multiplayer AI: tag a coding agent into a Slack conversation and it spins up a coding channel: everyone in that convo gets a live dev environment, diffs post as artifacts, and the channel winds down when the task is done. With the launch of Slack Code, Claudeforce, their MCP and more, Slack is putting Agents in the channels where teams already work, not simply in a private chat with one person. Their position is that the whole team should be able to watch, steer, and review what the agent does. Slack Chief Product Officer Jaime DeLanghe joined me on @chain_ofthought to explain how Slack is building a team AI environment, what happens mechanically when a code channel is created, why Anthropic pushes so much of its code through Slack, how the channel permission model became the agent context model, and what has to change in engineering culture when the whole team is steering one agent. I think Slack is the platform best positioned to become the context harness where enterprise agents run: agents that see what the team discusses, permissions that already exist, and a cultural opportunity hiding inside every multiplayer coding session. Chapters: (0:00) Slack as an IDE and a GitHub for your team (0:29) Who is Jaime DeLanghe (1:21) The reaction to the Slack Code launch (5:30) Why coding agents belong in a context-rich environment (6:08) Engineers now manage agents, not copy-paste code (7:24) The permission model: agents get the channel's context (11:44) What happens when a code channel is created (15:00) Why Anthropic pushes so much code through Slack (19:14) Steering one agent with many people: culture decides (24:54) Slackbot, skills, and MCPs: agents go where the work is (30:53) The solo terminal vs. agents in social spaces (33:53) Org charts and ownership when agents join the team (39:33) Learning loops and shared agent memory (42:39) Citations, recency, and accidental knowledge management (46:50) Context bloat and multi-pass search for agents (50:01) How Jaime uses Slackbot as CPO (52:38) Slack Code is V1 of multiplayer AI

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

  8a On my morning @Zoom with Jbazmine. Planning out the day, so we can work out the plan. Going through and getting eMail down to zero and assigning tasks in @SlackHQ.

• 
  Johan Cutych (@johancutych) reported 15 minutes ago

  first you need to fix the rate limits @SlackHQ

• 
  Taha Tesser (@TahaTesser) reported 17 minutes ago

  @KhalidWarsa @SlackHQ Because each workspace has own login. Even if you login on one device. You cannot sync all those workspaces under one account on another device

• 
  Michael Grinich (@grinich) reported 18 minutes ago

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

• 
  Evis Drenova (@evisdrenova) reported 21 minutes ago

  @sbilstein @SlackHQ yeah to your earlier point i think it depends at what layer you want to attack it i.e. rust builds are slow, caching can help but github actions is trash for it, but blacksmith isn't bad, is there a generic solution you can use that *just works* on any CI? alternatively, go after the actual docker execution layer but not clear to me how much of a bottleneck that actually is vs. language specific idiosyncrasies buildkit is pretty optimized from what i've heard but i generally agree with make it fast and stupidly easy to use!

• 
  Noah Levin (@nlevin) reported 23 minutes ago

  @SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏

• 
  Kit Langton (@kitlangton) reported 29 minutes ago

  @ferran9908 @SlackHQ Alas, this one is broken on desktop 😭 Every time a user responds, it disappears.

• 
  Luigi ➔ nora.finance (@luigiremor) reported 31 minutes ago

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

• 
  TT 😋 (@MotivatingPeng) reported 32 minutes ago

  @OpenAIDevs @googledrive @SlackHQ Can we fix Codex.... When it does a context automatically compacted it stops what its doing

• 
  Josh Ellithorpe (@zquestz) reported 33 minutes ago

  It is very obvious that @SlackHQ does absolutely zero QA testing on Linux. You would think they would at least do a basic sanity test. Latest release has a completely broken system tray, and broken desktop icon. Glad I hardly use this crap anymore.