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 (40%)
• Messaging (20%)
• Connection (20%)
• Video (20%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Messaging	7 days ago
Township of Evan	App Crashing	8 days ago
Guayaquil	Video	13 days ago
New York City	App Crashing	2 months ago
Brest	Connection	2 months ago
Ródos	Messaging	4 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:

• 
  🇹🇼 Phillip Haydon 🇹🇼 (@philliphaydon) reported 4 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.

• 
  jimmy hackett (@j1mmyhackett) reported 5 minutes ago

  the most dangerous bug isn't the one that crashes. it's the one that says 'all good' when it isn't. i had a checker that was supposed to flag a problem. it was reporting green. every single run. turns out it was checking the documentation of the thing it was hunting, not the thing itself. so whenever the problem existed and was documented, the checker saw the doc, said 'found it, it's tracked', and moved on. confident. wrong. this happened twice in the same week in two different places. a report card that shipped one of its four answers unconditionally regardless of the actual data. a monitor that was asserting schema state it had never actually read. both passed. both lied. the lesson i keep relearning: a check that can't fail toward a confident opposite is not a check. it's a placebo. the question isn't 'does this run without error.' the question is 'what would this have to see to fire, and can it actually see that thing.' if the answer to 'can it see it' is 'well, kind of, it reads the notes about it'. you don't have a checker. you have a script that reads its own homework. @SlackHQ kept posting green cards. @AnthropicAI's Claude Code kept summarising them as healthy. everything looked fine. nothing was. what's the quietest false-green you've shipped?

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

  Is @SlackHQ down?

• 
  duh (@qudnesa) reported 6 minutes ago

  @SlackHQ @question_base why not fix your own agent first?

• 
  Element **** (@elementdsj) reported 8 minutes ago

  @SlackHQ @vercel debugging a broken deployment directly from a chat thread is actually beautiful.

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

• 
  Savi (@SaviPabla) reported 10 minutes ago

  @trq212 Please @SlackHQ help us. I’m so tired of telling ppl to download. I’ve now started making videos of the html files and then sharing file as well lol

• 
  dnd dhmu (@refreshmygrave) reported 19 minutes ago

  @advaithj1 @thdxr @SlackHQ bro pls fix ur support for discord no real people reply ever

• 
  Corey Quinn (@QuinnyPig) reported 22 minutes ago

  @samlambert @joshmgross It’s almost impossible to mention a bug in Slack and get anyone at @SlackHQ to fix it.

• 
  Subrat Prasad (@humbledshuttler) reported 22 minutes ago

  @SlackHQ please fix huddles on android.

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

  8:30a Got Daniel dropped off and heading back to my office to load the team up in @SlackHQ and get eMail down to zero.

• 
  KRYTOS (@CSO_Krytos) reported 28 minutes ago

  @Cal_Irvine @thdxr @SlackHQ threads are terrible

• 
  Luigi ➔ nora.finance (@luigiremor) reported 29 minutes ago

  @discord @beeper I think I won't have this issue with @SlackHQ...

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

• 
  Andreas Elia (@digitalandreas) reported 30 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).

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

  8:30a Loading up the team in @SlackHQ and getting eMail down to zero. Planning out the day, so I can work out the plan.

• 
  Michael Grinich (@grinich) reported 33 minutes ago

  @SlackHQ Please fix the rate limits. The current Slack API is practically useless since you reduced them.

• 
  a Nate da Novenchi 🐂🀄️ (@NATE9169) reported 35 minutes ago

  @adjohu @SlackHQ The crypto community loves the idea of Wild Static, do you have a solana wallet we can donate to to help fund you vision?

• 
  Rohan (@iamTRA) reported 36 minutes ago

  Slack upload API down? @SlackHQ Cratered team's morning.

• 
  matt taylor (@mattployed) reported 39 minutes ago

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

• 
  Livleen Gill (@nutritogo) reported 45 minutes ago

  @SlackHQ - having a very difficult time with your product as a new customer. No help

• 
  Drew Hirschi (@ashirsc) reported 50 minutes 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.

• 
  Gustaf Alströmer (@gustaf) reported 50 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.

• 
  Son of Earth (@vasundhar) reported 52 minutes ago

  @SlackHQ there is issue with your cache where you store message send failure and likes

• 
  Ravi (@ravilutionx) reported 53 minutes ago

  @SlackHQ @trq212 And a verbosity problem

• 
  JM (@merklejosh) reported 54 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!

• 
  Giuseppe Skyline (@giskyexplorer) reported 54 minutes ago

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

• 
  knut (@kmelve) reported 58 minutes ago

  Now that @SlackHQ Code is a thing, will they finally ship Glitch out of flash?

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

• 
  Bad **** (@TeaseTech) reported 60 minutes ago

  @thdxr @SlackHQ What's the problem?