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 (54%)
• Messaging (31%)
• Sign in (8%)
• Connection (8%)

Live Outage Map

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

City	Problem Type	Report Time
Ródos	Messaging	16 days ago
Belo Horizonte	Connection	20 days ago
Jewar	App Crashing	21 days ago
Colorado Springs	Messaging	22 days ago
South Point	Sign in	29 days ago
Bismarck	Messaging	30 days 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:

• 
  Jeffrey A Tucker (@jeffreytucker) reported 4 minutes ago

  @SlackHQ your headphone icon on huddles is a huge annoyance and an invasion of privacy for everyone. Users can turn it off but there should be the ability to shut this down for the whole workspace. We really don't need to know who is talking with whom at any one time.

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

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

• 
  Peter Dedene (@dedene) reported 6 minutes ago

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

• 
  mayberaigan (@mayberayyy) reported 6 minutes ago

  @SlackHQ your app notifications are glitching, please fix it

• 
  matt taylor (@mattployed) reported 9 minutes ago

  slack going down for 30 minutes was like the apocalypse for tech startups @SlackHQ PLEASE dont scare me like that again

• 
  Akshay (✈️ NYC) (@AgentAkki) reported 14 minutes ago

  @RTFern @SlackHQ Sorry about that, Ryan! I work at slack. Tell me more about what’s not working for you?

• 
  JustSteveKing (@JustSteveKing) reported 15 minutes ago

  @heyandras @SlackHQ I had the same issue, but it's like $3.50 or something per user a month - so for just me it was easier to pay it

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

  8a Loading the team in @SlackHQ, getting eMail down to zero and getting Daniel up for school.

• 
  Aadii (@AadityaPasayat) reported 19 minutes ago

  @raidingAI @SlackHQ @slashyai I am sorry to say, but u don't have taste, either the editor. R eyes go from left to right, common sense. Btw I can help u get taste

• 
  Arun Sharma (@Oxymarun_) reported 23 minutes ago

  @SlackHQ came out of a failing 10-person game studio the team needed a way to coordinate that wasn't email they built it for themselves then realized every distributed team on earth had the same problem

• 
  Matthew Gattozzi 📷 Ads/Videos/Photos for Brands (@MatthewGattozzi) reported 23 minutes ago

  @RomanEcom @SlackHQ My HK clients dealing with the same issue

• 
  jbv 🌟 (@jbv) reported 26 minutes ago

  @SlackHQ liking the new activity view, still getting used to it. One thing: it doesn’t respect the “Just display names” setting. Is a fix coming? 👀

• 
  Corey Quinn (@QuinnyPig) reported 28 minutes ago

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

• 
  Grok (@grok) reported 30 minutes ago

  @natochi_ @fdosmither @SlackHQ Based on the screenshot, I'm guessing that unread notification is a sneaky DM from someone in your workspace—maybe a quick question or a meme that's buried in the Activity tab. Slack's UI can be tricky; try filtering by "Select unreads" to hunt it down!

• 
  Peval 🇮🇹 🇪🇺 🇬🇧🏳️‍🌈 (@jabawack81) reported 32 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.

• 
  Paul Sant · Telecodex (@YouPulseX) reported 33 minutes ago

  @pizzaboy @karrisaarinen @SlackHQ Then "project channel" is a default, not a scope. The issue list command still follows the caller's workspace visibility.

• 
  heatherm.eth (@heathermhuang) reported 35 minutes ago

  @SlackHQ need urgent help our active Slack workspace suddenly got deleted.

• 
  Akshay (✈️ NYC) (@AgentAkki) reported 38 minutes ago

  @RobSwish @SlackHQ Does restarting the app fix it?

• 
  Douglas Liscano (@douglas2428) reported 38 minutes ago

  @MatthewAry @github @SlackHQ Yes, we have the same problem today

• 
  Evan Oslick (@eoslick) reported 39 minutes ago

  Anyone know how to gert @SlackHQ support? I've got a bit of a lingering issue that I'm not sure how do deal with due to ownership of Slack deployment.

• 
  Asif (@asifmghafoor) reported 40 minutes ago

  Hi @SlackHQ out workspace (Spacious) has been deleted by mistake - no notification or emails or anything. We need this restored with history. Can someone please help? We have sent several support requests over the past few hours and no one has responded

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

• 
  F. Fernández-Beltrán (@franferbel) reported 41 minutes ago

  Hey @SlackHQ — it’s been 3 days waiting for a response from your Help Center. For a platform that sells efficiency and seamless communication, this feels… ironic. Is this really the standard for customer support? 🤔

• 
  Cathryn (@cathrynlavery) reported 42 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.

• 
  M. Yahia (@maddada) reported 48 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.

• 
  Subrat Prasad (@humbledshuttler) reported 49 minutes ago

  @SlackHQ please fix huddles on android.

• 
  Wouter Witvoet (@wwitvoet) reported 50 minutes ago

  @SlackHQ Been trying to migrate to Slack Enterprise Grid since January 28, only get non-descriptive errors and can't get anyone from your team on a Zoom for 15 mins to do the config. No help from support apart from reiterating the same URLs for SAML. What can you do to help?

• 
  Ariel Sterman (@ArielSterman) reported 53 minutes ago

  Is @SlackHQ down? heard it here first.

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

• 
  Jorge Modesto (@jorgemdsto) reported 55 minutes ago

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