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:

• 
  Ellen DaSilva (@ellenjdasilva) reported 2 minutes ago

  Sketchy behavior: Someone from @SlackHQ joined my company channel last week saying "we're here to help you with the product" (we're not having issues). Then today started pestering me about an overdue invoice (we don't have one). Beyond violating. Shameful behavior @salesforce.

• 
  Domino Mysłowski (@Domino_mys) reported 6 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

• 
  Noah Levin (@nlevin) reported 9 minutes ago

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

• 
  Mutatyo (@kyukxs) reported 13 minutes ago

  New Slack Design is terrible. @SlackHQ can I revert to a previous version just a few updates from this one!

• 
  Jorge Modesto (@jorgemdsto) reported 14 minutes ago

  @peduarte Yes @SlackHQ messed something up recently. Search is terrible now.

• 
  Signal House (@SignalHouseSMS) reported 16 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'

• 
  Amanda (@hey_amandam) reported 17 minutes ago

  @TejasKumar_ @SlackHQ Yes 👏 The issue with this (and all things like it) for me is that there seems to be some idea that anyone sees "AI" and immediately associates that with some value. What user pain of mine are you solving? I literally do not care if you are using AI or not to solve it, I just want the best experience. Explore AI as a cta is a waste of space and my mental energy

• 
  Kitayoshi (@kitayoshi_son) reported 17 minutes ago

  @alphato_o @SlackHQ Even a sticky banner hanging on the workspace saying “Your workspace will be shutting down” on the chat page would be better. They could even use the UI components for the 90-day limit. Today’s behavior makes it seem like they just don’t care.

• 
  Jori Lallo (@jorilallo) reported 17 minutes ago

  @pizzaboy @karrisaarinen @SlackHQ It's still the same agent with capability to access everything as the caller user can. If you're calling it in the channel, it has that as context so it will file issue into the project by default and answer questions about the project without you needing to name it separately. If there's situatons where it's not working as intended, would love to get screenshots

• 
  IT (@IncredibleTrade) reported 19 minutes ago

  Any issues with @SlackHQ

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

  6:30a Getting eMail down to zero. Planning out the work, so I can work out the plan. Loading support and production into @SlackHQ.

• 
  Cathryn (@cathrynlavery) reported 21 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 21 minutes ago

  8:30a Back at my desk, loading the team up in @SlackHQ with today's assignment, getting eMail down to zero.

• 
  SGN (@SGN06380601) reported 28 minutes ago

  @SlackHQ i need customer service help and am not getting a response from your agentforce. can you please help?

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

  @RTFern @SlackHQ Sorry about that, Ryan! I work at slack. Tell me more about what’s not working for you?