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:

• 
  Assaf Kipnis (@Kipnis_a) reported 26 seconds ago

  Claude is the best corporate CYA buddy I used to have full CYA files with records of messages, emails and things I did - I was terrible at keeping those and people took advantage of that. With Claude and @meetgranola - I have canonical record of all conversations, @SlackHQ messages, emails, canonical decisions - everything Oh, you say I didnt do something? I didnt respond? Here come the receipts

• 
  Peter Garber (@petegarber) reported 1 minute 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.

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

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

• 
  Noah Levin (@nlevin) reported 11 minutes ago

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

• 
  Signal House (@SignalHouseSMS) reported 12 minutes ago

  @SlackHQ @notion the only repetitive question saved here that matters is 'is the otp service still down.' second only to 'is the otp service still down for everyone or just me'

• 
  Johan Cutych (@johancutych) reported 13 minutes ago

  first you need to fix the rate limits @SlackHQ

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

• 
  Dhruv (@dhruv2038) reported 19 minutes ago

  Is @SlackHQ broken today - I am using Focus mode - seems like the emoticons are breaking.

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

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

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

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

  6:30a Back at the home office. Getting eMail down to zero. Planning the day so I can work out the plan. Passing work into @SlackHQ.

• 
  GosuCoder (@GosuCoder) reported 30 minutes ago

  Slackbot legit might be one of my favorite uses of AI outside of coding. I use this thing constantly to find past conversations, summarize entire chats, help write responses, look for things I might be forgetting, or even look up past context on a decision or topic. Seriously @SlackHQ this legit improves my life

• 
  PatrickUllrich (@ItsPatrickU) reported 30 minutes ago

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

• 
  Kit Langton (@kitlangton) reported 33 minutes ago

  @ferran9908 @SlackHQ Alas, this one is broken on desktop 😭 Every time a user responds, it disappears.