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:

• 
  Krazed 🇵🇸 (@Krazed) reported 2 minutes ago

  @SlackHQ you have a degradation rn? unable to create channels and getting intermittent issues with events

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

  6:30a Quickly getting eMail down to zero, loading the team up in @SlackHQ before a full morning of appointments.

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

  8a Loading the team in @SlackHQ, getting eMail down to zero and getting Daniel up for school.

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

• 
  VISHAL (@_THE__FUHRER) reported 5 minutes ago

  @SlackHQ @stewart Stewart Butterfield and his team were developing a game called "Glitch" in 2011 The Glitch was an ambitious and creative multiplayer game, but it struggled to find a large enough playerbase. They had to shut it down on 2012

• 
  Jose Urquiza (@hollowvox) reported 6 minutes ago

  We're about to start letting our employees fix their own bugs with @v0 and @SlackHQ. Why report a bug to another system when you can send it straight to v0? All I have to do is review the PR and merge it in. So confident in the models and the platform that I can go hands off.

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

  6a Getting eMail down to zero, loading up the team is @SlackHQ. Planning the day, so I can work the plan.

• 
  Pavel Zagorodnikh (@pavzagor) reported 13 minutes ago

  @SlackHQ you should really fix your reactions search its such a pain to remember the names of emojis. Look at what folks at @raycast and @telegram do 👀

• 
  tulumpo (@tulumpo) reported 14 minutes ago

  $IOND still in pre-launch. second delay message, 10:31 and now 10:39. this is normal. "All NASDAQ systems are fully operational" is in the message. nothing is broken. direct listings open when price discovery settles, not on a clock. @coinbase, @SlackHQ and @Spotify all opened late too.

• 
  Lalbee (@rebeurebel) reported 14 minutes ago

  @SlackHQ you guys are mental. You barely warn your users about migration and delete 20% of your slack active orgs without repeated warnings? You guys think everyone reads your cute email newsletters? What about BIG RED WARNINGS daily on the slack app itself? Ridiculous. Please help us get our accounts back.

• 
  Otto Hilska (@mutru) reported 17 minutes ago

  @SlackHQ The new Activity view is an amazing improvement. One thing that would make it better: the same thread can appear multiple times (for example the original post and a reply). It would help to allow deduplicating threads from the list.

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

• 
  jimmy hackett (@j1mmyhackett) reported 22 minutes ago

  the scariest bugs in an agent system aren't the ones that crash loudly. they're the ones that succeed. quietly. and then stop. and you don't find out for three days. this week i shipped `fix(daily): heartbeat + agent-health for the daily-report jobs` (commit 10c954a). the cron had been running. the launchd plist was registered. no errors in the log. but the report wasn't landing in @SlackHQ. it took me longer than i want to admit to realize the job had silently stopped delivering. no crash, no alert, just absence. the mental model i pulled from it: a job that runs is not the same as a job that works. completion and correctness are two different signals, and most infra only monitors the first one. heartbeats fix this. you instrument the output, not just the process. if the report doesn't land by 8:05am, something fires. you stop trusting the scheduler and start verifying the result. this applies way past cron jobs. any pipeline where you only watch for failure will eventually drift silently into uselessness. the absence of an error is not evidence of health. once i wired heartbeats into the @AnthropicAI-powered agent fleet, i found two other jobs that had the same problem. they looked fine. they weren't. if you're running automated jobs and you're not monitoring outputs, you're not monitoring. what's the longest a silent failure ran in your system before you caught it?

• 
  Peval 🇮🇹 🇪🇺 🇬🇧🏳️‍🌈 (@jabawack81) reported 24 minutes ago

  @gabsmashh Once nearly turned down a job interview because the invite came through @MicrosoftTeams. Spent the whole call trying to casually work out if they used @SlackHQ instead. They did.

• 
  Kleptocracy (@lfdoyfydoydtd) reported 25 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?