Slack status: messaging issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Slack reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Slack users through our website.

• App Crashing (50%)
• Connection (25%)
• Video (25%)

Live Outage Map

The most recent Slack outage reports came from the following cities:

City	Problem Type	Report Time
Township of Evan	App Crashing	1 day ago
Guayaquil	Video	6 days ago
New York City	App Crashing	1 month ago
Brest	Connection	2 months ago
Ródos	Messaging	3 months ago
Belo Horizonte	Connection	3 months ago

Full 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:

• 
  Josh Ellithorpe (@zquestz) reported 3 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.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 9 minutes ago

  @purionx @SlackHQ @salesforce tables in slack would genuinely help, wild that it took this long to even be a request

• 
  trent.sol (@trentdotsol) reported 10 minutes ago

  @cavemanloverboy @alessandrod @SlackHQ i did. it's the ones who won't that are the problem

• 
  Dhruv (@dhruv2038) reported 12 minutes ago

  Is @SlackHQ broken today - I am using Focus mode - seems like the emoticons are breaking.

• 
  Subrat Prasad (@humbledshuttler) reported 16 minutes ago

  @SlackHQ please fix huddles on android.

• 
  Assaf Kipnis (@Kipnis_a) reported 16 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

• 
  duh (@qudnesa) reported 20 minutes ago

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

• 
  a Nate da Novenchi 🐂🀄️ (@NATE9169) reported 23 minutes ago

  @adjohu @SlackHQ The crypto community loves the idea of Wild Static, do you have a solana wallet we can donate to to help fund you vision?

• 
  jimmy hackett (@j1mmyhackett) reported 25 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?

• 
  Signal House (@SignalHouseSMS) reported 26 minutes ago

  @SlackHQ @notion the only repetitive question saved here that matters is 'is the otp service still down.' second only to 'is the otp service still down for everyone or just me'

• 
  Hamid Ali (@HamidAli) reported 28 minutes ago

  Uh is @SlackHQ having issues…? 👀 #Slack

• 
  Jordy.app (@Jordy_vD_) reported 30 minutes ago

  . @SlackHQ slack gets a lot of things right, but the iOS app’s search functionality is very bad. Can I please chat with someone who can then hopefully fix it?

• 
  Salman (@m_salman_afzal) reported 31 minutes ago

  no meaningful way to contribute. Just like closed source/proprietary software, you can report issues, but whether it gets fixed or not depends upon the creator. For example, there are couple of issue that I reported to @SlackHQ regarding screen sharing popups,

• 
  Rahul Chetia (@ayoImNotTrippin) reported 32 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.

• 
  Teo Vanyo Adiputra (@teostealth) reported 36 minutes ago

  @karrisaarinen @SlackHQ The handoff from Slack discussion to actual tracked issue is where most teams drop the ball - keeping that loop tight is harder than it sounds.

• 
  Evgeny (@PlotnikovDev) reported 36 minutes ago

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

• 
  IT (@IncredibleTrade) reported 40 minutes ago

  Any issues with @SlackHQ

• 
  Corey Quinn (@QuinnyPig) reported 45 minutes ago

  @samlambert @joshmgross It’s almost impossible to mention a bug in Slack and get anyone at @SlackHQ to fix it.

• 
  Mike Rochefort 🐧 (@omenosdev) reported 45 minutes ago

  @SlackHQ I've sent a message in via the feedback address, but for 4.50.136 either there's been an undisclosed change of GPG keys used in signing Linux packages or the wrong key was used accidentally. For environments with strict package verification this leads to install errors.

• 
  Georg S. Kuklick (@downtownberlin) reported 46 minutes ago

  @SlackHQ @linear Then fix your MCP server!

• 
  Fluorine (@FluorineHQ) reported 46 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.

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 47 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.

• 
  y - alex ⚔️ (@onelonesabre) reported 47 minutes ago

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

• 
  Chimene | Dantown (@AgentC_006) reported 47 minutes ago

  @thdxr @SlackHQ It’s always weird that you cannot actively reply to messages on Slack. The experience feels broken.

• 
  Conor Bronsdon (@ConorBronsdon) reported 48 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

• 
  Vortex (@mjparme) reported 49 minutes ago

  @SlackHQ why is there no obvious way to join a channel in Slack? Seems like a huge usability problem, the + sign next to channels creates a channel, but joining one is very elusive

• 
  tulumpo (@tulumpo) reported 50 minutes ago

  $IOND still in pre-launch. second delay message, 10:31 and now 10:39. this is normal. "All NASDAQ systems are fully operational" is in the message. nothing is broken. direct listings open when price discovery settles, not on a clock. @coinbase, @SlackHQ and @Spotify all opened late too.

• 
  Evis Drenova (@evisdrenova) reported 51 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!

• 
  Vlad (@vladoustinov) reported 54 minutes ago

  @MerlinEgalite @SlackHQ The problem is they gave up on product a long time ago haha But yes embedding tools/workflows inside interfaces people are already used to use (slack/email/Notion etc) is the way to go

• 
  Michael Grinich (@grinich) reported 55 minutes ago

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