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

Live Outage Map

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

City	Problem Type	Report Time
New York City	App Crashing	27 days ago
Brest	Connection	2 months ago
Ródos	Messaging	3 months ago
Belo Horizonte	Connection	3 months ago
Jewar	App Crashing	3 months ago
Colorado Springs	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:

• 
  Noah Levin (@nlevin) reported 5 minutes ago

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

• 
  Bluejay (@getbluejay_ai) reported 6 minutes ago

  Bluejay AI can now act in @SlackHQ, not just answer. Run a simulation. Check how production calls went overnight. Resolve the issues that caused the failures. All from the channel your team is already in. Test, monitor, and improve your agents. Now in Slack. Led by Ronniel Gandhe.

• 
  Peter Garber (@petegarber) reported 7 minutes ago

  @Cartidise @OutofGalaxyy The icons might be stupid here but Gchat works pretty well inside of Gmail and this UI actually is OK. The only problem is that Gchat should literally be able to replace @SlackHQ but it’s been ignored.

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

• 
  Neil Chudleigh (@neilsuperduper) reported 13 minutes ago

  .@SlackHQ this message pops whenever i try to do any navigation. persists across restarts. also please fix the search results ↓ keypress issue, the first ↓ is being eaten by the system so when I am moving fast I am constantly going to the wrong place you need to make sure bugs like this dont continue, you have serious competition coming that is going to take business from you if you continue to let your product rot.

• 
  Jon Slemp (@Jon_Slemp) reported 15 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.

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

• 
  Vish (@vish_sh_) reported 16 minutes ago

  @SlackHQ Slack bot requires a proper fix first.

• 
  Bad **** (@TeaseTech) reported 19 minutes ago

  @thdxr @SlackHQ What's the problem?

• 
  Theodor Marcu (@theodormarcu) reported 21 minutes ago

  Putting an agent in Slack creates a very different UX problem: it has to know when to shut up We spent a lot of time tuning when Devin should speak, stay quiet, or move work into a separate channel. Devin was the first agent to support Slack natively, so it was great to bring 2 years of those learnings to @SlackHQ for the Slack Code launch.

• 
  KRYTOS (@CSO_Krytos) reported 24 minutes ago

  @Cal_Irvine @thdxr @SlackHQ threads are terrible

• 
  LANGERIUS (@Langerius) reported 29 minutes ago

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

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

• 
  SeattleViewHomes (@SeattleViewHome) reported 31 minutes ago

  @MadronaVentures @SlackHQ @salesforce Should we expect investment & AI to be doubling down on the green economy now that no one credible is promoting the fossil fuel/engineered obsolescence economies to be sustainable or even beneficial?

• 
  Violeta Poole (@PooleViole45138) reported 33 minutes ago

  @dabit3 @SlackHQ Building software entirely inside Slack sounds like a recipe for turning every bug fix into a group chat debate.

• 
  Andreas Elia (@digitalandreas) reported 36 minutes ago

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

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

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

• 
  Livleen Gill (@nutritogo) reported 37 minutes ago

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

• 
  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.

• 
  Kleptocracy (@lfdoyfydoydtd) reported 45 minutes ago

  @salesforce @SlackHQ Instead of buying other crappy software companies, create the best sales rep. SFDC 1.0>2.0>3.0... ITS ALL SO BROKEN. Broken company that had a chance to replace salespeople but didn’t use the data and systems they already had to make it happen with agents. WTF is agentforce?

• 
  MarketingMax.com (@MarketingMax) reported 45 minutes ago

  I never call out bad marketing But this is just infuriating. I pay them thousands of dollars a year, have the app installed in my computer, phone, and even iPad … so why did I get this? And why is it not optimized for dark iPhones? Let me know if you need help @SlackHQ @Benioff

• 
  knut (@kmelve) reported 47 minutes ago

  Now that @SlackHQ Code is a thing, will they finally ship Glitch out of flash?

• 
  Paul Thornton (@Fusspawn) reported 52 minutes ago

  @SlackHQ @dorukkavcioglu I miss the old glitch game, had fun with some of your old founders in that :(

• 
  TheHardTruth (@Watching1776) reported 52 minutes ago

  @SlackHQ You need to fix that app so it stops putting people into Auto Silence repeatedly without touching anything. Your code is trash

• 
  Ajith Joseph (@theajithjoseph) reported 53 minutes ago

  Friday thought. @stewart raised $17 million to build a video game. 3 years of work! 40 people. And almost nobody wanted to play it. He shut it down in December 2012 and laid off most of the team. The only thing left standing was the chat tool they'd built to talk to each other while working on it. That tool was @SlackHQ. @salesforce bought it for $27.7 billion. The thing you're building in the quiet stretch isn't wasted. Sometimes it turns out to be the actual product.

• 
  jimmy hackett (@j1mmyhackett) reported 56 minutes ago

  the most dangerous bug isn't the one that crashes. it's the one that says 'all good' when it isn't. i had a checker that was supposed to flag a problem. it was reporting green. every single run. turns out it was checking the documentation of the thing it was hunting, not the thing itself. so whenever the problem existed and was documented, the checker saw the doc, said 'found it, it's tracked', and moved on. confident. wrong. this happened twice in the same week in two different places. a report card that shipped one of its four answers unconditionally regardless of the actual data. a monitor that was asserting schema state it had never actually read. both passed. both lied. the lesson i keep relearning: a check that can't fail toward a confident opposite is not a check. it's a placebo. the question isn't 'does this run without error.' the question is 'what would this have to see to fire, and can it actually see that thing.' if the answer to 'can it see it' is 'well, kind of, it reads the notes about it'. you don't have a checker. you have a script that reads its own homework. @SlackHQ kept posting green cards. @AnthropicAI's Claude Code kept summarising them as healthy. everything looked fine. nothing was. what's the quietest false-green you've shipped?

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

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

• 
  Uday Subbarayan (@udaysubbarayan) reported 1 hour ago

  @SlackHQ Pl don’t hide the URL’s. Your recent overdoing here is creating problems Thanks

• 
  Gap | Suby (@gaspardlezin) reported 1 hour ago

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