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 (54%)
• Messaging (31%)
• Sign in (8%)
• Connection (8%)

Live Outage Map

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

City	Problem Type	Report Time
Ródos	Messaging	1 month ago
Belo Horizonte	Connection	1 month ago
Jewar	App Crashing	1 month ago
Colorado Springs	Messaging	1 month ago
South Point	Sign in	2 months ago
Bismarck	Messaging	2 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:

• 
  Brandon (@brandooonndd) reported 4 minutes ago

  🚨 @cursor_ai just dropped Automations always-on AI coding agents that run 24/7, triggered by GitHub PRs, Slack messages, or timers. They handle security audits, auto-approve low-risk PRs & fix bugs overnight. The future of dev just shipped. @github @SlackHQ #AIcoding #Cursor

• 
  Michael Grinich (@grinich) reported 4 minutes ago

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

• 
  kzer_AI (@kzer_ai) reported 5 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"

• 
  Caro (@CarolinaLaLopez) reported 7 minutes ago

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

• 
  Subrat Prasad (@humbledshuttler) reported 13 minutes ago

  @SlackHQ please fix huddles on android.

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

  8:30a Back at my desk, loading the team up in @SlackHQ with today's assignment, getting eMail down to zero.

• 
  M. Yahia (@maddada) reported 17 minutes ago

  @aaditsh @adilmania @SlackHQ Same, it's 10 times better than discord, teams, hangout, zoom, etc. Not sure about newer apps but I literally have 0 issues with slack. It's really good with connect too if you work with external companies, beats email by light years.

• 
  LoopGantt (@loopgantt) reported 19 minutes ago

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

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

• 
  PatrickUllrich (@ItsPatrickU) reported 20 minutes ago

  @karrisaarinen @linear @SlackHQ Linear coding agent when? 👀 currently handing it off to another service but be nice to skip the extra step.

• 
  Hamid Ali (@HamidAli) reported 21 minutes ago

  Uh is @SlackHQ having issues…? 👀 #Slack

• 
  wanderingwanderer (@iceman_ome) reported 22 minutes ago

  .@SlackHQ and @Jira have the weirdest integration possible. Have spent the last 15 mins trying to remove jira app from Slack, but unable to. Can someone more knowledgeable help?

• 
  Cass Anderson (@casspa) reported 25 minutes ago

  @Yonar87 @SlackHQ same issue here. Just sent them an email. Their status landing page says they've been 100% find this quarter which makes me think maybe they just don't update that page?

• 
  Gustaf Alströmer (@gustaf) reported 25 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.

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

• 
  Fluorine (@FluorineHQ) reported 26 minutes ago

  @gustaf @SlackHQ Reliability is the floor, not the ceiling. Slack hit the floor and is now adding notification noise to mask it — classic engagement-metric trap. The deeper issue: messaging apps stopped being where work happens and became where work gets talked about. That's the gap worth solving.

• 
  Antonio Ventre (@antonioventre_) reported 27 minutes ago

  A lot of companies in Hong Kong today got kicked out from shared @SlackHQ channels with clients etc However, Slack sent multiple emails to everyone back in February to move to Alibaba Cloud We did the migration in March, for 2 of our companies, and forced to do yearly plans (can’t do monthly subs with Alibaba Cloud) No major issues faced, apart from the fact that we doubled paid, since after the yearly payment they charged monthly again (but said that they will refund) If anyone has problems DM me, I have direct phone access with a representative and could fix this potentially asap

• 
  April Underwood (@aunder) reported 27 minutes ago

  In this day and age of infosec threats, this subject line from @SlackHQ is a bad call. After the brief cortisol spike that someone using the name Miles Davis had joined our Slack, I scrolled down, and then just wondered why on earth I would want this in my work communication tool.

• 
  miya (@202409R) reported 28 minutes ago

  @ManusAI @SlackHQ This kind of UX that charges users instantly without a clear confirmation step is unacceptable. @ManusAI please fix this and issue a refund. Users should NOT be charged $394 by mistake.

• 
  josh (@JoshCaughtFire) reported 30 minutes ago

  @peduarte @SlackHQ I like how the proposed community note is like ‘no they can’t’ then you read the slack docs and there is a self service export tool for org owners

• 
  Awais alwaisy (@alvaisy) reported 32 minutes ago

  @adilmania @SlackHQ what's wrong with slack. bunch of alternatives. each one made money. slack is still stable and useful. i don't have any issue with slakc except limited message history for free users

• 
  dnd dhmu (@refreshmygrave) reported 33 minutes ago

  @advaithj1 @thdxr @SlackHQ bro pls fix ur support for discord no real people reply ever

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

• 
  Mike Rochefort 🐧 (@omenosdev) reported 36 minutes ago

  @SlackHQ I've sent a message in via the feedback address, but for 4.50.136 either there's been an undisclosed change of GPG keys used in signing Linux packages or the wrong key was used accidentally. For environments with strict package verification this leads to install errors.

• 
  Karri Saarinen (@karrisaarinen) reported 40 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

• 
  Corey Quinn (@QuinnyPig) reported 42 minutes ago

  @samlambert @joshmgross It’s almost impossible to mention a bug in Slack and get anyone at @SlackHQ to fix it.

• 
  New Chapter Reprise Inigo Montoya (@BelmontJockey) reported 45 minutes ago

  AVOID using @SlackHQ at all costs. The UI is TERRIBLE. I get random notifications under "Activity" and it is impossible to find. So there is a red bubble notification that will never goes away. It happens all of the time. FREAKING TERRIBLE! Impossible to track down.

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

• 
  Darcy (@darcy_jpa) reported 54 minutes ago

  @SlackHQ @linear @cursor_ai Slack is a garbage product. Everything about it is trash. The reliability is trash, the support is trash, and the way you handle users is absolute trash. Impressive how consistently terrible you manage to be.

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

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