Slack status: messaging issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Slack reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Slack users through our website.

• App Crashing (33%)
• Messaging (33%)
• Connection (33%)

Live Outage Map

The most recent Slack outage reports came from the following cities:

City	Problem Type	Report Time
New York City	App Crashing	21 days ago
Brest	Connection	1 month ago
Ródos	Messaging	3 months ago
Belo Horizonte	Connection	3 months ago
Jewar	App Crashing	3 months ago
Colorado Springs	Messaging	3 months ago

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

• 
  Brandon Karl Webster (@bkwebster) reported 1 minute ago

  @adilmania @SlackHQ Better alternatives exist - it’s used abundantly because of the mindshare and scale. The only replacement would be a totally new and obvious form factor that leads to the same outcome in a better way - not a better alternative to the same problem.

• 
  Karri Saarinen (@karrisaarinen) reported 2 minutes ago

  @gustaf @ycombinator @SlackHQ I’d say Slack. Haven’t really experienced those issues you mention. Unless my internet is very bad. iMessage/whatsapp overly phone and counterparty focused so I’m more often wondering if the message actually got delivered or not and if the problem is me or them. Slack is more of a server and it doesn’t send the message if it doesn’t work.

• 
  Ariel Sterman (@ArielSterman) reported 7 minutes ago

  Is @SlackHQ down? heard it here first.

• 
  Violeta Poole (@PooleViole45138) reported 8 minutes ago

  @dabit3 @SlackHQ Building software entirely inside Slack sounds like a recipe for turning every bug fix into a group chat debate.

• 
  Giuseppe Skyline (@giskyexplorer) reported 10 minutes ago

  @gustaf @SlackHQ Notifications are the bandaid for broken reliability. WhatsApp stays quiet because it works.

• 
  Peval 🇮🇹 🇪🇺 🇬🇧🏳️‍🌈 (@jabawack81) reported 12 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.

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

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 21 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.

• 
  JM (@merklejosh) reported 21 minutes ago

  @SlackHQ There seems to be a bug in your Version 4.50.140 app (Mac) where if you have open a New message and you try to then click in the Search bar, you can't – it just flashes. Can you please fix this. It's very annoying. Thanks!

• 
  gerry🗯 (@Gerry) reported 21 minutes ago

  @zquestz @SlackHQ Ask codex to fix it

• 
  Alex Oppenheimer (@Alexoppenheimer) reported 22 minutes ago

  @SlackHQ I can't login to even contact support. I am in an infinite 2FA loop. And I am being overcharged. Needless to say, I am not happy.

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

  7:30a Getting eMail down to zero and loading up the team in @SlackHQ.

• 
  Jose Urquiza (@hollowvox) reported 24 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.

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

  Cmon @SlackHQ help the tfr

• 
  Mohi (@disismohi) reported 31 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.

• 
  Otto Hilska (@mutru) reported 32 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.

• 
  Mike Rochefort 🐧 (@omenosdev) reported 34 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.

• 
  Neil Chudleigh (@neilsuperduper) reported 37 minutes ago

  .@SlackHQ this message pops whenever i try to do any navigation. persists across restarts. also please fix the search results ↓ keypress issue, the first ↓ is being eaten by the system so when I am moving fast I am constantly going to the wrong place you need to make sure bugs like this dont continue, you have serious competition coming that is going to take business from you if you continue to let your product rot.

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

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

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

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

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

• 
  Andreas Elia (@digitalandreas) reported 43 minutes ago

  @hugorcd @SlackHQ @github It has been broken for so long they probably think it's a feature internally

• 
  Andreas Elia (@digitalandreas) reported 44 minutes ago

  @johnbarker @SlackHQ Doesn't feel like they are. We've had a bunch of pre-existing issues for a while now (I replied to the other fella in the tweet with examples).

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

• 
  Awais alwaisy (@alvaisy) reported 48 minutes ago

  @adilmania @SlackHQ what's wrong with slack. bunch of alternatives. each one made money. slack is still stable and useful. i don't have any issue with slakc except limited message history for free users

• 
  VISHAL (@_THE__FUHRER) reported 49 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

• 
  Ravi (@ravilutionx) reported 51 minutes ago

  @SlackHQ @trq212 And a verbosity problem

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

• 
  Amanda (@hey_amandam) reported 54 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

• 
  Tulip 🌷 ☮️ (@imTulip) reported 59 minutes ago

  Is @SlackHQ down?