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

• 
  ✩°｡⋆⸜ (@lenvioux) reported 22 seconds ago

  HEY @SlackHQ WHY I DIDNT GET NOTIFICATIONS neither on my phone for every conversation i had?!?! nor on my laptop app… unless i checked it every minutes?!!!? HELP

• 
  jimmy hackett (@j1mmyhackett) reported 26 seconds ago

  the scariest bugs in an agent system aren't the ones that crash loudly. they're the ones that succeed. quietly. and then stop. and you don't find out for three days. this week i shipped `fix(daily): heartbeat + agent-health for the daily-report jobs` (commit 10c954a). the cron had been running. the launchd plist was registered. no errors in the log. but the report wasn't landing in @SlackHQ. it took me longer than i want to admit to realize the job had silently stopped delivering. no crash, no alert, just absence. the mental model i pulled from it: a job that runs is not the same as a job that works. completion and correctness are two different signals, and most infra only monitors the first one. heartbeats fix this. you instrument the output, not just the process. if the report doesn't land by 8:05am, something fires. you stop trusting the scheduler and start verifying the result. this applies way past cron jobs. any pipeline where you only watch for failure will eventually drift silently into uselessness. the absence of an error is not evidence of health. once i wired heartbeats into the @AnthropicAI-powered agent fleet, i found two other jobs that had the same problem. they looked fine. they weren't. if you're running automated jobs and you're not monitoring outputs, you're not monitoring. what's the longest a silent failure ran in your system before you caught it?

• 
  IT (@IncredibleTrade) reported 5 minutes ago

  Any issues with @SlackHQ

• 
  Paul Sant · Telecodex (@YouPulseX) reported 6 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.

• 
  Bad **** (@TeaseTech) reported 7 minutes ago

  @thdxr @SlackHQ What's the problem?

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

• 
  SGN (@SGN06380601) reported 12 minutes ago

  @SlackHQ i need customer service help and am not getting a response from your agentforce. can you please help?

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

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

• 
  Angelo 🇵🇷 (@ngeloxyz) reported 13 minutes ago

  @chrismunns @SlackHQ lmao its broken for me too I am using Railway's client for Slack now + Beeper for DMs.

• 
  Dan (@pizzaboy) reported 16 minutes ago

  @karrisaarinen @SlackHQ Hey @karrisaarinen are the new project slack channels scoped to just that project I.e if you use the Linear slack bot in the channel will it only have access to issues and data from that project? I found that to be an issue a couple of months ago that the bot wasn’t able to be scoped down? Or was this a skill issue on my end

• 
  Alex Sidorenko (@alexei_sid) reported 17 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?

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

• 
  rushikesh (@ivadapav) reported 21 minutes ago

  @SlackHQ down. What's next?

• 
  JM (@merklejosh) reported 24 minutes ago

  @SlackHQ There seems to be a bug in your Version 4.50.140 app (Mac) where if you have open a New message and you try to then click in the Search bar, you can't – it just flashes. Can you please fix this. It's very annoying. Thanks!

• 
  duh (@qudnesa) reported 26 minutes ago

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

• 
  Rob Swift (@RobSwish) reported 31 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.

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

  7:30a Getting eMail down to zero and loading up the team in @SlackHQ.

• 
  Jake Mor (@jakemor) reported 34 minutes ago

  can someone at @SlackHQ please for the love of god fix drag and drop to attach a file? how has this been an issue for months without anyone realizing? Steps to reproduce: Drag file to attach. Nothing happens. no file attached.

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

  8a On my morning @Zoom with Jbazmine. Planning out the day, so we can work out the plan. Going through and getting eMail down to zero and assigning tasks in @SlackHQ.

• 
  Alex Oppenheimer (@Alexoppenheimer) reported 41 minutes ago

  @SlackHQ I can't login to even contact support. I am in an infinite 2FA loop. And I am being overcharged. Needless to say, I am not happy.

• 
  Peter Dedene (@dedene) reported 43 minutes ago

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

• 
  Dhruv (@dhruv2038) reported 44 minutes ago

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

• 
  Jose Urquiza (@hollowvox) reported 46 minutes ago

  We're about to start letting our employees fix their own bugs with @v0 and @SlackHQ. Why report a bug to another system when you can send it straight to v0? All I have to do is review the PR and merge it in. So confident in the models and the platform that I can go hands off.

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

  @kurushdubash @patriciosainzr @SlackHQ 👋I work at Slack. Could you share a screenshot or more details on what's not working?

• 
  jbv 🌟 (@jbv) reported 48 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? 👀

• 
  Johan Cutych (@johancutych) reported 51 minutes ago

  first you need to fix the rate limits @SlackHQ

• 
  Jide (@rhymezx_code) reported 53 minutes ago

  @SlackHQ Tell me why Slack desktop is not working on Ubuntu 26.04 ( Resolute Raccoon ) ??? Honestly i have tried o #Ubuntu

• 
  Drew Hirschi (@ashirsc) reported 53 minutes ago

  @SlackHQ pls never ask me again if I want to DM a thread when I tag someone with no text. This is a terrible feature.

• 
  Jason Alco (@jason_alco) reported 53 minutes ago

  @SlackHQ Our team loves the platform, but we really need to fix the mark unread feature. It’s been broken for years now. First, you should be able to mark a channel as unread without opening the channel and selecting a message. Second, half the time marking a message as unread doesn’t work. I have to go message by message, trying over and over until one works. Please fix this, thank you 🫠

• 
  Taha Tesser (@TahaTesser) reported 59 minutes ago

  @KhalidWarsa @SlackHQ Because each workspace has own login. Even if you login on one device. You cannot sync all those workspaces under one account on another device