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 (22%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	App Crashing	10 days ago
Brest	Connection	1 month ago
Ródos	Messaging	2 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 2 minutes ago

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

• 
  Gustaf Alströmer (@gustaf) reported 7 minutes ago

  @karrisaarinen @ycombinator @SlackHQ I'm experiencing reliability issues with Slack. Message's aren't sent. Messages can't be deleted. App not loading properly. I haven't had any of those issues with Whatsapp ever to be honest. Messages on iPhone is even worse. It's nearly unusable for me.

• 
  Savi (@SaviPabla) reported 8 minutes ago

  @trq212 Please @SlackHQ help us. I’m so tired of telling ppl to download. I’ve now started making videos of the html files and then sharing file as well lol

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

  @RobSwish @SlackHQ Does restarting the app fix it?

• 
  Vlad (@vladoustinov) reported 11 minutes ago

  @MerlinEgalite @SlackHQ The problem is they gave up on product a long time ago haha But yes embedding tools/workflows inside interfaces people are already used to use (slack/email/Notion etc) is the way to go

• 
  duh (@qudnesa) reported 12 minutes ago

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

• 
  𝐎𝐧𝐞𝐓𝐫𝐮𝐞𝐇𝐨𝐦𝐢𝐞(👑,👑) (@OneTrueHomie) reported 15 minutes ago

  isn't this the same problem @PromptQL promised @sama in order to kill @SlackHQ ?

• 
  Evan Oslick (@eoslick) reported 19 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.

• 
  Rab Memari (@rabmemari) reported 21 minutes ago

  @chriskim_dev @Teknium No problem. I think its more of a @SlackHQ problem, but happy to check if I can fix it in Hermes and push a PR

• 
  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!

• 
  jimmy hackett (@j1mmyhackett) reported 25 minutes 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?

• 
  matt taylor (@mattployed) reported 27 minutes ago

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

• 
  Johan Cutych (@johancutych) reported 27 minutes ago

  first you need to fix the rate limits @SlackHQ

• 
  Douglas Liscano (@douglas2428) reported 28 minutes ago

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

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 29 minutes ago

  Its really disappointing that @SlackHQ status page suggests its up, when it's clearly down and you can get up to date status from X users who are reporting the same issues.

• 
  Jason Alco (@jason_alco) reported 30 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 🫠

• 
  y - alex ⚔️ (@onelonesabre) reported 32 minutes ago

  @SlackHQ @question_base can't use these features when your app is down my friend

• 
  Richard Casimir (@NWFreeZone) reported 33 minutes ago

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

• 
  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"

• 
  John Harnett (@JohnHarnett) reported 37 minutes ago

  @cyberomin @digitalandreas @SlackHQ If you've filed a bug with them on the last 5 years and arent a big co then you'd know. They dont fix stuff just because it's broken.

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

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

• 
  Element **** (@elementdsj) reported 39 minutes ago

  @SlackHQ @vercel debugging a broken deployment directly from a chat thread is actually beautiful.

• 
  Evgeny (@PlotnikovDev) reported 41 minutes ago

  @adilmania @SlackHQ What problem with slack? We use slack and discord.

• 
  Rahul Chetia (@ayoImNotTrippin) reported 41 minutes ago

  @SlackHQ there’s a widespread issue with slack today. Not sure about Mac but my entire team with windows seems to be impacted. Slack becomes irresponsive on windows a few minutes in. Tried ‘repair’ and force close, but no help there. We are using app in our phones to communicate.

• 
  Leon (@MozzyFX) reported 43 minutes ago

  Please @SlackHQ can you add a proper GIF selector I need to send better gifs right after I take down production

• 
  Caro (@CarolinaLaLopez) reported 43 minutes ago

  The @SlackHQ glitch in notification numbers is killing my vibe this morning

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

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

• 
  Slavko Kovačević (@realslavko) reported 56 minutes ago

  @SlackHQ Fix notifications first

• 
  LANGERIUS (@Langerius) reported 57 minutes ago

  @BarknTuncer @SlackHQ yeah notification sync issues are still surprisingly common

• 
  Rohan (@iamTRA) reported 59 minutes ago

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