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:

• 
  matt taylor (@mattployed) reported 59 seconds ago

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

• 
  Drew Hirschi (@ashirsc) reported 1 minute ago

  @SlackHQ pls never ask me again if I want to DM a thread when I tag someone with no text. This is a terrible feature.

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

• 
  Ariel Sterman (@ArielSterman) reported 3 minutes ago

  Is @SlackHQ down? heard it here first.

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

• 
  Douglas Liscano (@douglas2428) reported 6 minutes ago

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

• 
  Mike Rochefort 🐧 (@omenosdev) reported 7 minutes ago

  @SlackHQ I've sent a message in via the feedback address, but for 4.50.136 either there's been an undisclosed change of GPG keys used in signing Linux packages or the wrong key was used accidentally. For environments with strict package verification this leads to install errors.

• 
  Greg Boyd / WGBOYD (@gregboyd) reported 8 minutes ago

  @SlackHQ What are the chances we can cut down the number of clicks to start a huddle from four to say… one? Driving me crazy. 🙏🏻

• 
  noah (@noahsolomon) reported 9 minutes ago

  @hiiinternet @SlackHQ It’s a big problem actually

• 
  Gustaf Alströmer (@gustaf) reported 10 minutes ago

  @karrisaarinen @ycombinator @SlackHQ I'm experiencing reliability issues with Slack. Message's aren't sent. Messages can't be deleted. App not loading properly. I haven't had any of those issues with Whatsapp ever to be honest. Messages on iPhone is even worse. It's nearly unusable for me.

• 
  Mohi (@disismohi) reported 12 minutes ago

  @SlackHQ: 40% less merge queue time, CI type-checking down from 7.5 minutes to 1.25 minutes. Canva: 58s to first error in the editor down to 4.8s.

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

  8a On my morning @Zoom with Jbazmine. Planning out the day, so we can work out the plan. Going through and getting eMail down to zero and assigning tasks in @SlackHQ.

• 
  Chimene | Dantown (@AgentC_006) reported 13 minutes ago

  @thdxr @SlackHQ It’s always weird that you cannot actively reply to messages on Slack. The experience feels broken.

• 
  Jori Lallo (@jorilallo) reported 16 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

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 26 minutes ago

  Its really disappointing that @SlackHQ status page suggests its up, when it's clearly down and you can get up to date status from X users who are reporting the same issues.