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%)
• Sign in (20%)
• Connection (20%)

Live Outage Map

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

City	Problem Type	Report Time
Birmingham	Connection	1 month ago
Greenville	Messaging	2 months ago
Morsang-sur-Orge	App Crashing	2 months ago
Greater Noida	App Crashing	2 months ago
Lexington	Sign in	3 months ago
Creil	Connection	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:

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

  7a Planning out the day in Google Calendar and loading the team in @SlackHQ. Getting email down to zero.

• 
  Zev Zoldan (@ZevZoldan) reported 4 minutes ago

  Hot take for the AI founders knocking @SlackHQ: Slack doesn’t have a “communication problem.” Teams do. Most “ignored messages” aren’t about noise, attention spans, or channel chaos. It’s because Slack messages have zero structure. No timing. No follow-through. No visibility. Just text thrown into the void and a prayer. The second you add structure — forms, confirmations, simple logic — everything changes. People actually respond. Leaders stop guessing. Teams stop resending the same message 12 times. Slack doesn’t need fewer messages. It needs smarter ones. That’s what we’re building with @TryThreadly.

• 
  BitcoinCPA (@bitcpa) reported 7 minutes ago

  I am never going to use @SlackHQ again unless they fix the issue on the iPhone app where it doesn’t auto scroll to the latest message in a thread. You have to scroll down for 2 mins to get to the latest message. Not working for me on OpenClaw. Like if you know what I mean.

• 
  josh (@JoshCaughtFire) reported 12 minutes ago

  @peduarte @SlackHQ I like how the proposed community note is like ‘no they can’t’ then you read the slack docs and there is a self service export tool for org owners

• 
  Josh Jackson (@IamJoshJackson) reported 13 minutes ago

  @scott_peterson4 @SlackHQ I wonder if they intentionally don't fix it so you keep opening the app to try and clear it

• 
  Pavan Pal (@Pavan_Kumar_Pal) reported 14 minutes ago

  @SlackHQ Always good to see Slack doubling down on productivity, not noise.

• 
  Steini (@67steinip) reported 16 minutes ago

  @kitayoshi_son @SlackHQ We've sent 2 emails so far nothing, they arent going to respond to you because this is a MASS event, you arent alone, we didnt even get the email people talk about and some others say that as well, we just got wiped. I don't think they will help you.

• 
  JP (@jmp2431) reported 17 minutes ago

  @SlackHQ is the system having trouble saving changes to a workflow? I can’t get anything to save.

• 
  Disky.eth (@OxDisky) reported 19 minutes ago

  I just learned you can basically see all @SlackHQ profile images publicly without the need for authenticated request. Isn't this both a #privacy issue and security issue? I mean, you can basically fetch them from ca.slack-edge dot com. #slack #privacyprotection

• 
  David Rose (@david_navigator) reported 19 minutes ago

  @SlackHQ If it's based on Salesforce's support AI, then we're off. It's terrible and ends up taking twice as long to do what we want.

• 
  Oliver Pitsch (@ot) reported 20 minutes ago

  @AmenaiSabuwala @SlackHQ If Slack would not need the Splash Loader they would surely remove it and dive directly to login. Please understand the basic, before posting such stuff. 😫

• 
  Shantanu (@shantanughosh) reported 26 minutes ago

  @SlackHQ is the new Webex. Absolutely terrible performance and difficult to use on cellular networks in India now. I was so excited when the company I joined used Zoom instead on that terrible terrible productivity waste that was Webex. That’s slack now.

• 
  Carlos Valentin (@CarlosBBuild) reported 28 minutes ago

  @AmenaiSabuwala @SlackHQ I feel like people are at the login screens for not that long, I see why they only have their logos

• 
  Darcy (@darcy_jpa) reported 28 minutes ago

  @SlackHQ @linear @cursor_ai Slack is a garbage product. Everything about it is trash. The reliability is trash, the support is trash, and the way you handle users is absolute trash. Impressive how consistently terrible you manage to be.

• 
  Deepak Jadhav (@jadhavdeepak93) reported 30 minutes ago

  Sometimes you slow things down on purpose to preserve coherence. Example: @SlackHQ shows typing indicators. Not because it must, but because humans need temporal context. Elevators do the same thing in spatial context.

• 
  RyanMeyer (@RyanDMeyer) reported 36 minutes ago

  @jedcli @SlackHQ HK company, US billing. suddenly shut off and Slack has zero customer service. No phone number, no live chat, nothing... submit an email and wait and pray apparently. What ********.

• 
  Antonio Ventre (@antonioventre_) reported 39 minutes ago

  A lot of companies in Hong Kong today got kicked out from shared @SlackHQ channels with clients etc However, Slack sent multiple emails to everyone back in February to move to Alibaba Cloud We did the migration in March, for 2 of our companies, and forced to do yearly plans (can’t do monthly subs with Alibaba Cloud) No major issues faced, apart from the fact that we doubled paid, since after the yearly payment they charged monthly again (but said that they will refund) If anyone has problems DM me, I have direct phone access with a representative and could fix this potentially asap

• 
  Kristal Met Dejmon (@i_cirkovic) reported 39 minutes ago

  Soo.. @Zoom @SlackHQ @canva down.. what else?

• 
  Jason Robinson (@voideng) reported 42 minutes ago

  @QuinnyPig @awscloud I would agree, but I had a number of workloads fail over to other regions without issue, all of them used DynamoDB. I am thankful that @SlackHQ is multi-region.

• 
  Josh Woods (he/him) (@sdoowhsoj) reported 42 minutes ago

  Not a single day passes when using @SlackHQ on mobile where uploading multiple images, causes me to tap on the "record an audio clip" button, because "attach" button appears *after* selecting an image and slides the entire sheet up. @SlackHQ please for the love of god fix this!!

• 
  Caroline Thompson (@cthompson297) reported 44 minutes ago

  @c1r3n @SlackHQ there’s a huge internet outage going on rn, it’s impacting several major companies!

• 
  Eric Novak (@EricRNovak) reported 45 minutes ago

  @SlackHQ is down fyi @downrightnow

• 
  KC (@exPUNISHER) reported 47 minutes ago

  @salesforce @MrBeast @SlackHQ Jimmy texted Pyramid! Write that down, it won't be in the code though.

• 
  AK (@MohschinoKhan) reported 47 minutes ago

  @daveamsterdam20 @SlackHQ Same issue here wtf is going on!! @SlackHQ

• 
  New Chapter Reprise Inigo Montoya (@BelmontJockey) reported 49 minutes ago

  AVOID using @SlackHQ at all costs. The UI is TERRIBLE. I get random notifications under "Activity" and it is impossible to find. So there is a red bubble notification that will never goes away. It happens all of the time. FREAKING TERRIBLE! Impossible to track down.

• 
  F. Fernández-Beltrán (@franferbel) reported 49 minutes ago

  Hey @SlackHQ — it’s been 3 days waiting for a response from your Help Center. For a platform that sells efficiency and seamless communication, this feels… ironic. Is this really the standard for customer support? 🤔

• 
  Maverick_Reports (@MaverickReports) reported 50 minutes ago

  Anyone using clawdbot? Seeing loads of videos on how its so easy to use - 8 hrs in & still can't get @xai to run. Grok has give me an amended .json file which fails. Tried to run Clawdbot in @SlackHQ (too complicated, gave up) switched to @discord now working & getting the following error - any help would be really appreciated: Agent failed before reply: No API key found for provider "xai". Auth store: C:\Users\NAME.clawdbot\agents\main\agent\auth-profiles.json (agentDir: C:\Users\NAME.clawdbot\agents\main\agent). Configure auth for this agent (clawdbot agents add <id>) or copy auth-profiles.json from the main agentDir. Logs: clawdbot logs --follow

• 
  Matthew Gattozzi 📷 Ads/Videos/Photos for Brands (@MatthewGattozzi) reported 53 minutes ago

  @RomanEcom @SlackHQ My HK clients dealing with the same issue

• 
  Matt Slotnick (@matt_slotnick) reported 57 minutes ago

  hello @SlackHQ team there’s a very annoying bug that makes agents in slack significantly worse UX and is probably crushing engagement. can someone help

• 
  Aayush Desai (@Aayush0994) reported 57 minutes ago

  @SlackHQ can you please fix the unread notification that does not go away even after reading the message? Thanks!