Slack 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:

• 
  SeattleViewHomes (@SeattleViewHome) reported 4 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?

• 
  Riley Read-Only (@HotForMoot) reported 5 minutes ago

  Cmon @SlackHQ help the tfr

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

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

• 
  Rohan (@iamTRA) reported 6 minutes ago

  Slack upload API down? @SlackHQ Cratered team's morning.

• 
  Peter Dedene (@dedene) reported 9 minutes ago

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

• 
  Michael Grinich (@grinich) reported 12 minutes ago

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

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

• 
  Douglas Liscano (@douglas2428) reported 15 minutes ago

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

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

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

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

• 
  LANGERIUS (@Langerius) reported 17 minutes ago

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

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 18 minutes ago

  @purionx @SlackHQ @salesforce tables in slack would genuinely help, wild that it took this long to even be a request

• 
  Ajith Joseph (@theajithjoseph) reported 18 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.

• 
  Ken Liao (@YukanL) reported 23 minutes ago

  It's been almost 2 days since @SlackHQ deleted our company workspace without warning. Aside from a vague email a few months ago about migrating to a different reseller in our region, there was no communication at all leading up to the deletion. Support only responds with the same message template telling us to reach out to sales and hasn't responded to followups since yesterday. Some of the worst SaaS customer service I've ever experienced. What are the best alternatives to Slack?

• 
  matt taylor (@mattployed) reported 25 minutes ago

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