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

Live Outage Map

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

City	Problem Type	Report Time
New York City	App Crashing	24 days ago
Brest	Connection	1 month ago
Ródos	Messaging	3 months ago
Belo Horizonte	Connection	3 months ago
Jewar	App Crashing	3 months ago
Colorado Springs	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:

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

  6:30a Quickly getting eMail down to zero, loading the team up in @SlackHQ before a full morning of appointments.

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

• 
  ImagineArt (@ImagineArt_X) reported 7 minutes ago

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

• 
  Teo Vanyo Adiputra (@teostealth) reported 8 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.

• 
  Peter Dedene (@dedene) reported 8 minutes ago

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

• 
  Kit Langton (@kitlangton) reported 8 minutes ago

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

• 
  Paul Thornton (@Fusspawn) reported 8 minutes ago

  @SlackHQ @dorukkavcioglu I miss the old glitch game, had fun with some of your old founders in that :(

• 
  Dhruv (@dhruv2038) reported 10 minutes ago

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

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

  @RobSwish @SlackHQ Does restarting the app fix it?

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

  8:30a Back at my desk, loading the team up in @SlackHQ with today's assignment, getting eMail down to zero.

• 
  matt taylor (@mattployed) reported 12 minutes ago

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

• 
  Douglas Liscano (@douglas2428) reported 18 minutes ago

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

• 
  Otto Hilska (@mutru) reported 20 minutes ago

  @SlackHQ The new Activity view is an amazing improvement. One thing that would make it better: the same thread can appear multiple times (for example the original post and a reply). It would help to allow deduplicating threads from the list.

• 
  Sammie (@nexgencoded) reported 25 minutes ago

  @SlackHQ really said what if your coworker wasn't annoying enough?? now you can add an AI coding agent to the group chat @Claude fix this 30 seconds later claude: PR opened greg from accounting: why is there a PR claude: I have no idea who Greg is....

• 
  Theodor Marcu (@theodormarcu) reported 27 minutes ago

  Putting an agent in Slack creates a very different UX problem: it has to know when to shut up We spent a lot of time tuning when Devin should speak, stay quiet, or move work into a separate channel. Devin was the first agent to support Slack natively, so it was great to bring 2 years of those learnings to @SlackHQ for the Slack Code launch.

• 
  Riley Read-Only (@HotForMoot) reported 29 minutes ago

  Cmon @SlackHQ help the tfr

• 
  mr.tipton (@mrtipton_art) reported 36 minutes ago

  @pizzaboy @SlackHQ Nah, I’m that guy. Gotta fix it

• 
  Ajith Joseph (@theajithjoseph) reported 36 minutes ago

  Friday thought. @stewart raised $17 million to build a video game. 3 years of work! 40 people. And almost nobody wanted to play it. He shut it down in December 2012 and laid off most of the team. The only thing left standing was the chat tool they'd built to talk to each other while working on it. That tool was @SlackHQ. @salesforce bought it for $27.7 billion. The thing you're building in the quiet stretch isn't wasted. Sometimes it turns out to be the actual product.

• 
  Giuseppe Skyline (@giskyexplorer) reported 38 minutes ago

  @gustaf @SlackHQ Notifications are the bandaid for broken reliability. WhatsApp stays quiet because it works.

• 
  Q (@quionie) reported 39 minutes ago

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

• 
  Ari Dehkordi (@arashdehkordiHQ) reported 41 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?

• 
  The Mishmash Cat (@TheMishmashCat) reported 41 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.

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

  6a Getting eMail down to zero, loading up the team is @SlackHQ. Planning the day, so I can work the plan.

• 
  gerry🗯 (@Gerry) reported 46 minutes ago

  @zquestz @SlackHQ Ask codex to fix it

• 
  Aadii (@AadityaPasayat) reported 47 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

• 
  IT (@IncredibleTrade) reported 50 minutes ago

  Is @SlackHQ mobile app down?

• 
  Gap | Suby (@gaspardlezin) reported 51 minutes ago

  Can someone please buy @SlackHQ and shut it down? This platform is horrible.

• 
  a Nate da Novenchi 🐂🀄️ (@NATE9169) reported 55 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?

• 
  Pavel Zagorodnikh (@pavzagor) reported 56 minutes ago

  @SlackHQ you should really fix your reactions search its such a pain to remember the names of emojis. Look at what folks at @raycast and @telegram do 👀

• 
  IT (@IncredibleTrade) reported 59 minutes ago

  Any issues with @SlackHQ