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	25 days ago
Belo Horizonte	Connection	28 days ago
Jewar	App Crashing	30 days ago
Colorado Springs	Messaging	1 month ago
South Point	Sign in	1 month ago
Bismarck	Messaging	1 month 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:

• 
  RyanMeyer (@RyanDMeyer) reported 6 seconds ago

  @jedcli @SlackHQ HK company, US billing. suddenly shut off and Slack has zero customer service. No phone number, no live chat, nothing... submit an email and wait and pray apparently. What ********.

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

• 
  trent.sol (@trentdotsol) reported 1 minute ago

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

• 
  Asif (@asifmghafoor) reported 2 minutes ago

  Hi @SlackHQ out workspace (Spacious) has been deleted by mistake - no notification or emails or anything. We need this restored with history. Can someone please help? We have sent several support requests over the past few hours and no one has responded

• 
  JIM EVANS (@JEVANSCPM) reported 4 minutes ago

  @SlackHQ @slack_community not sure what happened and on who’s side, but after your recent update I’m having major issues opening your program. (Mac OS)

• 
  Johan Cutych (@johancutych) reported 10 minutes ago

  first you need to fix the rate limits @SlackHQ

• 
  Agustín Ruiz (@aguscruiz) reported 12 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 🫶

• 
  Parker Chun (@parker_chun_) reported 14 minutes ago

  In all seriousness, would love some help debugging an issue @SlackAPI @SlackHQ

• 
  Henry Schuck (@HenryLSchuck) reported 16 minutes ago

  EVERY @ZoomInfo customer can connect @claudeai and ZoomInfo together right now- but how about in @SlackHQ ? With Claude? Here’s how to build a targeted prospect list and account plan without leaving Slack. (In <5 minutes) Step 1: Ask Claude directly inside Slack to build you a list I asked for… “25 CROs and VPs of Sales based in Boston, at software companies between 500–1k employees, with $100M+ in funding. Name, title, email, mobile, total funding.” It taps straight into your Zoominfo database and all comes back right there in the channel. It even flags who is on your do not call list. Step 2: Pick an account. Ask Claude to prep you for the call, directly in Slack. It uses Zoominfo to pull every conversation you've had with them - calls, emails, pain points they've raised, products they use. It comes back with the leadership you NEED to know, what's happening at the account right now and specific angles that could help you win. This works inside Claude too when you connect it up to our MCP server - you can even ask it to build you a custom interface to sort, edit, and work the data however you want. Zoominfo is going to show up EVERYWHERE. Slack, Claude, wherever you're doing GTM work, your data should follow you there.

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

  8a Loading the team in @SlackHQ, getting eMail down to zero and getting Daniel up for school.

• 
  Subrat Prasad (@humbledshuttler) reported 21 minutes ago

  @SlackHQ please fix huddles on android.

• 
  Noah Levin (@nlevin) reported 29 minutes ago

  @SlackHQ mobile unread state bugs continue to be quite a painful and frustrating issue… plz fix 🙏

• 
  mewc (@the_mewc) reported 29 minutes ago

  @SlackHQ lots of bugs and issues right now. Can't create channels and lots of jankyness. This release is a lot.

• 
  kingoftheworld (@4kingtheworld) reported 30 minutes ago

  @antonioventre_ @SlackHQ Hey man, I’d really appreciate help getting Slack restored. I’ve got a company with 40 employees and it’s catastrophic man anything you can do to help Tried dming but it didn’t work

• 
  Shantanu (@shantanughosh) reported 31 minutes ago

  @SlackHQ is the new Webex. Absolutely terrible performance and difficult to use on cellular networks in India now. I was so excited when the company I joined used Zoom instead on that terrible terrible productivity waste that was Webex. That’s slack now.

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

• 
  Giuseppe Skyline (@giskyexplorer) reported 33 minutes ago

  @gustaf @SlackHQ Notifications are the bandaid for broken reliability. WhatsApp stays quiet because it works.

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

• 
  miya (@202409R) reported 35 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.

• 
  Son of Earth (@vasundhar) reported 38 minutes ago

  @SlackHQ there is issue with your cache where you store message send failure and likes

• 
  Ariel Sterman (@ArielSterman) reported 41 minutes ago

  Is @SlackHQ down? heard it here first.

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

• 
  Azmy (@AzmyBlog) reported 46 minutes ago

  @lennysan @SlackHQ @aunder The strobe light thing is so real. The person presenting has been inside the problem for weeks. The reviewer walks in cold. And it's not really a flaw in the exec ..... it's just structural. That gap exists at every level in every review setting. The actual skill is learning to rebuild context for the reviewer quickly, instead of assuming they're already there with you.

• 
  Sophia Yen MD (@teenmd) reported 46 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?

• 
  noah (@noahsolomon) reported 49 minutes ago

  @hiiinternet @SlackHQ It’s a big problem actually

• 
  Cass Anderson (@casspa) reported 50 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?

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

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

  8a On my morning @Zoom with Jbazmine. Planning out the day, so we can work out the plan. Going through and getting eMail down to zero and assigning tasks in @SlackHQ.

• 
  Richard Casimir (@NWFreeZone) reported 57 minutes ago

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

• 
  Barlow Buddy Barrier (@barrier_buddy) reported 59 minutes ago

  @SlackHQ @salesforce I literally have slack and use slack or all the time and it has no clue what this is or how to help