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 (42%)
• Messaging (33%)
• Connection (17%)
• Sign in (8%)

Live Outage Map

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

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

• 
  LoopGantt (@loopgantt) reported 56 seconds ago

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

• 
  Bhuvanesh Sridharan (@_bhuvanesh_) reported 2 minutes ago

  as much hate @MicrosoftTeams gets, at least the meeting chat and other chats are on the same platform. Absence of synergy between @SlackHQ chat and Google meet is such a pet peeve. Non issue in grand scheme but still bothering whenever people send links in gmeet.

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

  7:30a Back home, getting the boys up, getting eMail down to zero, loading the team up with today's support and production website work (in @SlackHQ).

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

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

• 
  KRYTOS (@CSO_Krytos) reported 5 minutes ago

  @Cal_Irvine @thdxr @SlackHQ threads are terrible

• 
  Fluorine (@FluorineHQ) reported 7 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.

• 
  wanderingwanderer (@iceman_ome) reported 10 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?

• 
  Domino Mysłowski (@Domino_mys) reported 15 minutes ago

  There was Pay by Eye, by Ring, by Watch… time to Pay by Juice? 🧃💳 Okay, this one was just a joke created by Callum (FrostyTrollz). But 10 years ago, paying with your watch or ring also sounded ridiculous. A great example of how today’s joke can become tomorrow’s product is.. @SlackHQ The team behind Slack was actually building an online game called Glitch. As the founders later mentioned: “The game was absolutely preposterous.” Eventually, the game failed and was shut down. However, the internal chat tool they built to communicate became more valuable than the game itself. That tool became Slack, now used by millions of teams. 🌱 Follow for more wild growth-hacks

• 
  Jose Urquiza (@hollowvox) reported 17 minutes ago

  We're about to start letting our employees fix their own bugs with @v0 and @SlackHQ. Why report a bug to another system when you can send it straight to v0? All I have to do is review the PR and merge it in. So confident in the models and the platform that I can go hands off.

• 
  LANGERIUS (@Langerius) reported 17 minutes ago

  @BarknTuncer @SlackHQ yeah notification sync issues are still surprisingly common

• 
  mewc (@the_mewc) reported 20 minutes ago

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

• 
  Corey Quinn (@QuinnyPig) reported 30 minutes ago

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

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

• 
  Peter Dedene (@dedene) reported 32 minutes ago

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

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

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

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

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

• 
  Gap | Suby (@gaspardlezin) reported 38 minutes ago

  Can someone please buy @SlackHQ and shut it down? This platform is horrible.

• 
  matt taylor (@mattployed) reported 41 minutes ago

  slack going down for 30 minutes was like the apocalypse for tech startups @SlackHQ PLEASE dont scare me like that again

• 
  mr.tipton (@mrtipton_art) reported 42 minutes ago

  @pizzaboy @SlackHQ Nah, I’m that guy. Gotta fix it

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

• 
  kingoftheworld (@4kingtheworld) reported 45 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

• 
  Björne 🇸🇪🏋️‍♂️ (@SilchQuatch) reported 46 minutes ago

  @QuinnyPig @SlackHQ Every single unwarranted notification births months of hate inside of me. Literally anti-ads for me, any pattern of it and I immediately remove the service. I guess it has to work or it wouldn't be done?

• 
  y - alex ⚔️ (@onelonesabre) reported 48 minutes ago

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

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

  @kurushdubash @patriciosainzr @SlackHQ 👋I work at Slack. Could you share a screenshot or more details on what's not working?

• 
  Caro (@CarolinaLaLopez) reported 52 minutes ago

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

• 
  Asif (@asifmghafoor) reported 53 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

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

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

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

• 
  PatrickUllrich (@ItsPatrickU) reported 58 minutes ago

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