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 (40%)
• Messaging (20%)
• Connection (20%)
• Video (20%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Messaging	5 days ago
Township of Evan	App Crashing	6 days ago
Guayaquil	Video	11 days ago
New York City	App Crashing	1 month ago
Brest	Connection	2 months ago
Ródos	Messaging	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:

• 
  Björne 🇸🇪🏋️‍♂️ (@SilchQuatch) reported 3 minutes ago

  @QuinnyPig @SlackHQ Every single unwarranted notification births months of hate inside of me. Literally anti-ads for me, any pattern of it and I immediately remove the service. I guess it has to work or it wouldn't be done?

• 
  Livleen Gill (@nutritogo) reported 3 minutes ago

  @SlackHQ - having a very difficult time with your product as a new customer. No help

• 
  Corey Quinn (@QuinnyPig) reported 3 minutes ago

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

• 
  M. Yahia (@maddada) reported 4 minutes ago

  @aaditsh @adilmania @SlackHQ Same, it's 10 times better than discord, teams, hangout, zoom, etc. Not sure about newer apps but I literally have 0 issues with slack. It's really good with connect too if you work with external companies, beats email by light years.

• 
  Q (@quionie) reported 6 minutes ago

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

• 
  SeattleViewHomes (@SeattleViewHome) reported 8 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?

• 
  Mohammad Romman (@MohammadRoman8) reported 9 minutes ago

  @SlackHQ are you guys shutting down? It’s been more than a week I’ve been contacting you guys. Support isn’t responding at all

• 
  Andreas Elia (@digitalandreas) reported 10 minutes ago

  @johnbarker @SlackHQ Doesn't feel like they are. We've had a bunch of pre-existing issues for a while now (I replied to the other fella in the tweet with examples).

• 
  tulumpo (@tulumpo) reported 11 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.

• 
  Karri Saarinen (@karrisaarinen) reported 15 minutes ago

  @gustaf @ycombinator @SlackHQ I’d say Slack. Haven’t really experienced those issues you mention. Unless my internet is very bad. iMessage/whatsapp overly phone and counterparty focused so I’m more often wondering if the message actually got delivered or not and if the problem is me or them. Slack is more of a server and it doesn’t send the message if it doesn’t work.

• 
  Richard Casimir (@NWFreeZone) reported 17 minutes ago

  @xsupport @slackHQ X links on slack (android) Still not working. All other sites redirect properly from slack. Just NOT X.

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

  6:30a Got eMail down to zero, and started the team with assignments in @SlackHQ.

• 
  IT (@IncredibleTrade) reported 27 minutes ago

  Is @SlackHQ mobile app down?

• 
  The Mishmash Cat (@TheMishmashCat) reported 31 minutes ago

  [1/5] Your #brain cannot multithread. When you switch from writing code to answering a @SlackHQ ping, your prefrontal cortex doesn't execute a clean parallel jump - it triggers an expensive, messy tear-down and rebuild process. You are burning raw compute.

• 
  Dhruv (@dhruv2038) reported 36 minutes ago

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

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

• 
  April Underwood (@aunder) reported 45 minutes ago

  In this day and age of infosec threats, this subject line from @SlackHQ is a bad call. After the brief cortisol spike that someone using the name Miles Davis had joined our Slack, I scrolled down, and then just wondered why on earth I would want this in my work communication tool.

• 
  KRYTOS (@CSO_Krytos) reported 45 minutes ago

  @Cal_Irvine @thdxr @SlackHQ threads are terrible

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

  6:30a Back at the home office. Getting eMail down to zero. Planning the day so I can work out the plan. Passing work into @SlackHQ.

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

  8:30a Loading up the team in @SlackHQ and getting eMail down to zero. Planning out the day, so I can work out the plan.

• 
  Kit Langton (@kitlangton) reported 49 minutes ago

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

• 
  Mike Rochefort 🐧 (@omenosdev) reported 49 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.

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

• 
  Kelly Carter (@Gr8fulTr8s) reported 51 minutes ago

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

• 
  Jorge Modesto (@jorgemdsto) reported 52 minutes ago

  @peduarte Yes @SlackHQ messed something up recently. Search is terrible now.

• 
  Stache (@stacheFonzi) reported 53 minutes ago

  It's from 2011, but I still miss Glitch. It was a browser based MMO based on collecting and crafting. Crazily enough it was made by the company that went on to rebrand and make @SlackHQ. The messaging system in the game became the basis for Slack.

• 
  Cathryn (@cathrynlavery) reported 56 minutes ago

  @Shopify @klaviyo @SlackHQ The Non-Technical Technical Dictionary, Day 2: Frontend & Backend Every app has a front of house and a back of house. Same as a restaurant. The frontend is what you see and touch. Think of Amazon, or any website you use. → The menu bar, the buttons, the search box. Everything on screen is just a list of things you're allowed to ask for. That's the menu, the dining room, the host stand. But nothing on that menu is actually happening at your table. When you hit "Buy Now," it's like placing an order with a waiter. He walks it back, the kitchen cooks it, and he brings it out when it's ready. The backend = the kitchen. You'll find database, business logic, server. Anything heavy (pulling your order history, processing a payment, sending an email) happens back there. The frontend only handles what fits at the table: how the buttons look, what color the page is, the small animations etc. Think Michelin star. They're not torching your steak tableside. They need the walk-in, the grill, the prep station, the sous chef. Software is the same. The interesting work needs the full kitchen. When a service like Cloudflare or AWS goes down and takes half the internet with it, that's a backend problem. The ghost kitchen caught fire and every restaurant relying on it went dark. A frontend problem is the one you've seen a hundred times: a button that won't click, text piled on top of an image, a page that looks broken on your phone. Frontend is form, where backend is function.

• 
  MarketingMax.com (@MarketingMax) reported 56 minutes ago

  I never call out bad marketing But this is just infuriating. I pay them thousands of dollars a year, have the app installed in my computer, phone, and even iPad … so why did I get this? And why is it not optimized for dark iPhones? Let me know if you need help @SlackHQ @Benioff

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

• 
  Andreas Elia (@digitalandreas) reported 1 hour ago

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