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	10 days ago
Township of Evan	App Crashing	11 days ago
Guayaquil	Video	16 days ago
New York City	App Crashing	2 months ago
Brest	Connection	2 months ago
Ródos	Messaging	4 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:

• 
  Alexander Cranga (@alexandercranga) reported 27 seconds ago

  /copy from Claude -> paste in Slack -> doesn’t keep the formatting. @SlackHQ please fix

• 
  Bad **** (@TeaseTech) reported 58 seconds ago

  @thdxr @SlackHQ What's the problem?

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

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

• 
  Jason Alco (@jason_alco) reported 2 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 3 minutes ago

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

• 
  Brad Beckett (@bradbeckett) reported 3 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!

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

• 
  Agustín Ruiz (@aguscruiz) reported 4 minutes ago

  Hi @SlackHQ, can you please fix this notification dot issue? It's been bothering me for like a month or more already. It shows that I have something unread when I don't. Even hovering on it makes the dot go away when there's something unread. It's very annoying for people with "unread anxiety" like me lol. Thank you 🫶

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

• 
  Michael Grinich (@grinich) reported 11 minutes ago

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

• 
  Razi Ansari (@RaziAns14640044) reported 11 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

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

  8:30a Loading up the team in @SlackHQ and getting eMail down to zero. Planning out the day, so I can work out the plan.

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

  @RTFern @SlackHQ Sorry about that, Ryan! I work at slack. Tell me more about what’s not working for you?

• 
  Calvin Lee (@calvinclee) reported 23 minutes ago

  @SlackHQ the mobile app has significantly regressed. why do I have a DM tab and an activity tab that only lets me filter down to DMs again? I want to easily filter for mentions.

• 
  Cathryn (@cathrynlavery) reported 24 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.

• 
  Gary McMillian (@GaryMcMillianTX) reported 25 minutes ago

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

• 
  Johan Cutych (@johancutych) reported 27 minutes ago

  first you need to fix the rate limits @SlackHQ

• 
  LoopGantt (@loopgantt) reported 30 minutes ago

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

• 
  Kelly Carter (@Gr8fulTr8s) reported 35 minutes ago

  @SlackHQ issues connecting to a new workspace. Where can I get support?

• 
  ImagineArt (@ImagineArt_X) reported 35 minutes ago

  @SlackHQ @SlackHQ cute, but can you fix the "copying emojis from slack to somewhere else please"

• 
  Douglas Liscano (@douglas2428) reported 35 minutes ago

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

• 
  Jon Slemp (@Jon_Slemp) reported 37 minutes ago

  Bug report for you @SlackHQ — when receiving a DM notification from Agents, and those agents are setup as Slack apps you have to DM directly in an app channel, once you hit a certain number of chats in your history tab you can no longer navigate to the DM directly by clicking the DM notification on mobile. You basically get navigated to a blank screen and effectively chat find the message ever. Please fix. This is a disaster of a bug.

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

• 
  Rab Memari (@rabmemari) reported 40 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

• 
  Chimene | Dantown (@AgentC_006) reported 41 minutes ago

  @thdxr @SlackHQ It’s always weird that you cannot actively reply to messages on Slack. The experience feels broken.

• 
  Andreas Elia (@digitalandreas) reported 46 minutes ago

  @johnbarker @SlackHQ Doesn't feel like they are. We've had a bunch of pre-existing issues for a while now (I replied to the other fella in the tweet with examples).

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

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

• 
  Vortex (@mjparme) reported 51 minutes ago

  @SlackHQ why is there no obvious way to join a channel in Slack? Seems like a huge usability problem, the + sign next to channels creates a channel, but joining one is very elusive

• 
  jbv 🌟 (@jbv) reported 54 minutes ago

  liking the new slack activity view—still getting used to it. One thing: it doesn’t respect the “Just display names” setting. Is a fix coming? 👀 @SlackHQ

• 
  Jorge Modesto (@jorgemdsto) reported 55 minutes ago

  @peduarte Yes @SlackHQ messed something up recently. Search is terrible now.