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

Live Outage Map

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

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

• 
  Ari Dehkordi (@arashdehkordiHQ) reported 6 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 6 minutes ago

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

• 
  Travis Peters (@SivvyRat) reported 6 minutes ago

  @SlackHQ You have no way to provide feedback within your app so... your snap installer has major issues.

• 
  Sam Pullara (@sampullara) reported 6 minutes ago

  @thdxr @SlackHQ No one wants all replies to show up in the channel. It is a terrible defauu.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 11 minutes ago

  @purionx @SlackHQ @salesforce tables in slack would genuinely help, wild that it took this long to even be a request

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

• 
  jimmy hackett (@j1mmyhackett) reported 12 minutes ago

  i shipped a report that posted a PDF to @SlackHQ with buttons to approve or flag it. worked great in testing. turns out every single report was re-sharing the exact same file. Next.js had cached the upload URL on the first request and just kept reusing it. so every property got the same PDF. same charts. same data. looked fine in the message. was completely wrong. the fix was straightforward once i saw it. but i only saw it because i added logging on the upload path and watched what Slack was actually returning. without that i would have kept assuming the reports were right. this is the thing that keeps biting me. i build something, it posts, the message looks correct, and i ship it. but "the message looks correct" is not the same as "the data is correct". i need the system to surface the difference, not just tell me a message was sent. the reports now work the way they were supposed to. one message per property, each with its own PDF, two models reading it and leaving grades in the thread. the buttons are how you reply to the report, not how you open it. but i almost shipped a monitoring system that was monitoring nothing. it was just confidently showing me the same snapshot on repeat. what is the dumbest caching bug you have hit in ****?

• 
  jimmy hackett (@j1mmyhackett) reported 18 minutes ago

  the most dangerous bug isn't the one that crashes. it's the one that says 'all good' when it isn't. i had a checker that was supposed to flag a problem. it was reporting green. every single run. turns out it was checking the documentation of the thing it was hunting, not the thing itself. so whenever the problem existed and was documented, the checker saw the doc, said 'found it, it's tracked', and moved on. confident. wrong. this happened twice in the same week in two different places. a report card that shipped one of its four answers unconditionally regardless of the actual data. a monitor that was asserting schema state it had never actually read. both passed. both lied. the lesson i keep relearning: a check that can't fail toward a confident opposite is not a check. it's a placebo. the question isn't 'does this run without error.' the question is 'what would this have to see to fire, and can it actually see that thing.' if the answer to 'can it see it' is 'well, kind of, it reads the notes about it'. you don't have a checker. you have a script that reads its own homework. @SlackHQ kept posting green cards. @AnthropicAI's Claude Code kept summarising them as healthy. everything looked fine. nothing was. what's the quietest false-green you've shipped?

• 
  siggy bilstein (@sbilstein) reported 18 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.

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

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

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

• 
  Jori Lallo (@jorilallo) reported 21 minutes ago

  @pizzaboy @karrisaarinen @SlackHQ It's still the same agent with capability to access everything as the caller user can. If you're calling it in the channel, it has that as context so it will file issue into the project by default and answer questions about the project without you needing to name it separately. If there's situatons where it's not working as intended, would love to get screenshots

• 
  Richard Casimir (@NWFreeZone) reported 23 minutes ago

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

• 
  Tulip 🌷 ☮️ (@imTulip) reported 30 minutes ago

  Is @SlackHQ down?

• 
  Rodrigo Berriel (@rodrigoberriel) reported 30 minutes ago

  @thdxr @SlackHQ unbelievable right? terrible ux

• 
  Sophia Yen MD (@teenmd) reported 33 minutes ago

  .@SlackHQ Why don't you have human service agents? You are a GIANT company used by many. The only contact us is via a webform?

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

• 
  John Harnett (@JohnHarnett) reported 42 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.

• 
  JM (@merklejosh) reported 43 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!

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

• 
  Andreas Elia (@digitalandreas) reported 48 minutes ago

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

• 
  Taha Tesser (@TahaTesser) reported 49 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

• 
  Mohi (@disismohi) reported 50 minutes ago

  @SlackHQ: 40% less merge queue time, CI type-checking down from 7.5 minutes to 1.25 minutes. Canva: 58s to first error in the editor down to 4.8s.

• 
  Stache (@stacheFonzi) reported 51 minutes ago

  It's from 2011, but I still miss Glitch. It was a browser based MMO based on collecting and crafting. Crazily enough it was made by the company that went on to rebrand and make @SlackHQ. The messaging system in the game became the basis for Slack.

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

• 
  A-Yo! despises APC (@AyomideAdenowo1) reported 57 minutes ago

  @daniielezeh @SlackHQ Bruhhh, valid question 😭 I've been having issues with the ******* video playback. I didn't even know it was possible to have worse video playback than twitter.

• 
  Tyler (@tyhouch) reported 59 minutes ago

  yo @SlackHQ please add support for viewing .html files in chat. everyones tossing these around and the download->open in chrome friction is slowing me down bigtime

• 
  Alex Oppenheimer (@Alexoppenheimer) reported 59 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.

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

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

• 
  Caro (@CarolinaLaLopez) reported 1 hour ago

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