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

Live Outage Map

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

City	Problem Type	Report Time
New York City	App Crashing	29 days ago
Brest	Connection	2 months 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:

• 
  LoopGantt (@loopgantt) reported 4 minutes ago

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

• 
  Corey Quinn (@QuinnyPig) reported 5 minutes ago

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

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

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

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

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

• 
  Dhruv (@dhruv2038) reported 9 minutes ago

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

• 
  Andreas Elia (@digitalandreas) reported 9 minutes ago

  @hugorcd @SlackHQ @github It has been broken for so long they probably think it's a feature internally

• 
  Rob Swift (@RobSwish) reported 10 minutes ago

  @AgentAkki @SlackHQ Restarting doesn't help, and I mentioned this in the dms, it seems so weird to basically have 2 dm lists.

• 
  Jordy.app (@Jordy_vD_) reported 11 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?

• 
  Karri Saarinen (@karrisaarinen) reported 12 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.

• 
  TT 😋 (@MotivatingPeng) reported 26 minutes ago

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

• 
  Razi Ansari (@RaziAns14640044) reported 26 minutes ago

  @SlackHQ should fix the UX of their video player. It's one of the worst pieces of UX I've ever interacted with. It feels like I suddenly landed on some government app. Too messy

• 
  gerry🗯 (@Gerry) reported 27 minutes ago

  @zquestz @SlackHQ Ask codex to fix it

• 
  Giuseppe Skyline (@giskyexplorer) reported 30 minutes ago

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

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

  7:30a Getting eMail down to zero, passing out assignments in @SlackHQ

• 
  kzer_AI (@kzer_ai) reported 33 minutes ago

  @OpenAI @linear @SlackHQ The agent that pulls context from docs, email, chats, and code to update your Linear ticket: "status: someone else's problem"

• 
  MarketingMax.com (@MarketingMax) reported 36 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

• 
  Krazed 🇵🇸 (@Krazed) reported 36 minutes ago

  @SlackHQ you have a degradation rn? unable to create channels and getting intermittent issues with events

• 
  Manoj Yadav (@Manoj____Yadav) reported 38 minutes ago

  @TheNickBigar @CricTalk29 @SlackHQ No it doesn’t track time, you need to tell the time spent via message. Example- worked on X for 30 mins - remind me about checking the production issue around 3 pm The idea is to reduce friction for users on how they track time and tasks

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 41 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.

• 
  Rohan (@iamTRA) reported 42 minutes ago

  Slack upload API down? @SlackHQ Cratered team's morning.

• 
  Alex Sidorenko (@alexei_sid) reported 42 minutes ago

  @Moore_Irish @salesforce @SlackHQ Pricing changes that reduce admin control while pushing AI features rarely improve outcomes. The real test: does the AI actually help teams make faster, better decisions, or is it just another feature tax masquerading as innovation?

• 
  siggy bilstein (@sbilstein) reported 44 minutes ago

  @evisdrenova hmm kinda like Kaniko caching locally, but I think the problem is that the industry has broadly gotten used to very slow deploy pipelines. Back when I was at @SlackHQ in like 2018, we used to SCP the monolith across the fleet and deploy in a couple minutes. Containerization is awesome for various reasons but it has gotten an entire generation of developers to just expect builds + deploys to take at least 15 and usually closer to 45. I do wonder how much perf you could squeeze out with replacing BuildKit but I imagine it's already highly optimized. I just *feel* like developers shouldn't have to think so much about why their builds are slow.

• 
  miya (@202409R) reported 48 minutes ago

  @ManusAI @SlackHQ This kind of UX that charges users instantly without a clear confirmation step is unacceptable. @ManusAI please fix this and issue a refund. Users should NOT be charged $394 by mistake.

• 
  Awais alwaisy (@alvaisy) reported 49 minutes ago

  @adilmania @SlackHQ what's wrong with slack. bunch of alternatives. each one made money. slack is still stable and useful. i don't have any issue with slakc except limited message history for free users

• 
  Ravi (@ravilutionx) reported 50 minutes ago

  @SlackHQ @trq212 And a verbosity problem

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

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

• 
  Paul Thornton (@Fusspawn) reported 56 minutes ago

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

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

  @SlackHQ @linear Then fix your MCP server!

• 
  Darrell Brogdon (@dbrogdon) reported 58 minutes ago

  Yesterday I signed up for a service. Today, all my @SlackHQ had a notification asking if I wanted to connect some bot of that service to my Slack accounts. One thing has nothing to do with the other, as far as I'm concern. If this keeps up, I'll delete all of my Slack accounts.

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