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

Live Outage Map

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

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

• 
  Amanda (@hey_amandam) reported 5 minutes ago

  @TejasKumar_ @SlackHQ Yes 👏 The issue with this (and all things like it) for me is that there seems to be some idea that anyone sees "AI" and immediately associates that with some value. What user pain of mine are you solving? I literally do not care if you are using AI or not to solve it, I just want the best experience. Explore AI as a cta is a waste of space and my mental energy

• 
  Manoj Yadav (@Manoj____Yadav) reported 5 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

• 
  mayberaigan (@mayberayyy) reported 13 minutes ago

  @SlackHQ your app notifications are glitching, please fix it

• 
  Brad Beckett (@bradbeckett) reported 13 minutes ago

  With how much sensitive data @SlackHQ stores, it's surprising they don't yet support Passkey login or have a BIMI email verification certificate so their legitimate emails get a blue verified check mark in major email service providers. @digicert pls reach out to them!

• 
  Tyler (@tyhouch) reported 14 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

• 
  Salman (@m_salman_afzal) reported 14 minutes ago

  no meaningful way to contribute. Just like closed source/proprietary software, you can report issues, but whether it gets fixed or not depends upon the creator. For example, there are couple of issue that I reported to @SlackHQ regarding screen sharing popups,

• 
  Karri Saarinen (@karrisaarinen) reported 18 minutes ago

  @gustaf @ycombinator @SlackHQ What is degrading? WhatsApp imo is not a good example. Can’t even hold login on a desktop, and have to auth with your phone. Sync not super reliable either

• 
  Dan (@pizzaboy) reported 21 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

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

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

• 
  Drew Hirschi (@ashirsc) reported 26 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.

• 
  Ravi (@ravilutionx) reported 28 minutes ago

  @SlackHQ @trq212 And a verbosity problem

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

• 
  Gary McMillian (@GaryMcMillianTX) reported 34 minutes ago

  @SlackHQ You need to fix your search before moving on to AI.

• 
  Sammie (@nexgencoded) reported 34 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....

• 
  Pavel Zagorodnikh (@pavzagor) reported 35 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 👀

• 
  Mohi (@disismohi) reported 35 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.

• 
  Cathryn (@cathrynlavery) reported 40 minutes ago

  @Shopify @klaviyo @SlackHQ The Non-Technical Technical Dictionary, Day 2: Frontend & Backend Every app has a front of house and a back of house. Same as a restaurant. The frontend is what you see and touch. Think of Amazon, or any website you use. → The menu bar, the buttons, the search box. Everything on screen is just a list of things you're allowed to ask for. That's the menu, the dining room, the host stand. But nothing on that menu is actually happening at your table. When you hit "Buy Now," it's like placing an order with a waiter. He walks it back, the kitchen cooks it, and he brings it out when it's ready. The backend = the kitchen. You'll find database, business logic, server. Anything heavy (pulling your order history, processing a payment, sending an email) happens back there. The frontend only handles what fits at the table: how the buttons look, what color the page is, the small animations etc. Think Michelin star. They're not torching your steak tableside. They need the walk-in, the grill, the prep station, the sous chef. Software is the same. The interesting work needs the full kitchen. When a service like Cloudflare or AWS goes down and takes half the internet with it, that's a backend problem. The ghost kitchen caught fire and every restaurant relying on it went dark. A frontend problem is the one you've seen a hundred times: a button that won't click, text piled on top of an image, a page that looks broken on your phone. Frontend is form, where backend is function.

• 
  Captain (@Cap039) reported 41 minutes ago

  @SlackHQ One recent Slack regression: If you edit a post that contains a link, the link preview disappears. Please fix this 🙏

• 
  Ellen DaSilva (@ellenjdasilva) reported 49 minutes ago

  Sketchy behavior: Someone from @SlackHQ joined my company channel last week saying "we're here to help you with the product" (we're not having issues). Then today started pestering me about an overdue invoice (we don't have one). Beyond violating. Shameful behavior @salesforce.

• 
  Savi (@SaviPabla) reported 51 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

• 
  Salman (@m_salman_afzal) reported 54 minutes ago

  @SlackHQ But whether they decide to act on it will depend how much they prioritize the issue. And this is what open source could become as well. We can only report but only their agent factories can now contribute. So, it kind of is closed source since no one is now reading the 100k loc

• 
  Caro (@CarolinaLaLopez) reported 54 minutes ago

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

• 
  Rodrigo Berriel (@rodrigoberriel) reported 54 minutes ago

  @thdxr @SlackHQ unbelievable right? terrible ux

• 
  Stache (@stacheFonzi) reported 54 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.

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

• 
  Jake Mor (@jakemor) reported 56 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.

• 
  Michael Grinich (@grinich) reported 56 minutes ago

  @SlackHQ Please fix the rate limits. The current Slack API is practically useless since you reduced them.

• 
  Peter Dedene (@dedene) reported 57 minutes ago

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

• 
  Livleen Gill (@nutritogo) reported 1 hour ago

  @SlackHQ - having a very difficult time with your product as a new customer. No help

• 
  y - alex ⚔️ (@onelonesabre) reported 1 hour ago

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