Slack down or not working? Current app problems and status

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	22 days ago
Greenville	Messaging	1 month ago
Morsang-sur-Orge	App Crashing	1 month ago
Greater Noida	App Crashing	2 months ago
Lexington	Sign in	2 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:

• 
  John Small Mountain (@johnsmallmtn) reported 3 minutes ago

  Is @SlackHQ not working for anyone else? Mobile app is fine. Browser is fine. Mac client is not responsive even after a restart. It’s there but can click on communities, threads, or even scroll in a conversation.

• 
  Federico Guerinoni (@____guerra) reported 3 minutes ago

  Can't signin into @SlackHQ workspace, if I try to join -> account has already use this mail (clearly me, long time ago) If i want to reset my pwd (because last time I deleted account) -> I receive "Is this the right email?" I don't want use another mail for this :O

• 
  Rashid (@RashtheDude) reported 5 minutes ago

  @SlackHQ No error, just not able to connect on the Mac OS desktop and Android mobile.

• 
  Kevin Zeillmann (@kzeillmann) reported 7 minutes ago

  @isugimpy @chhopsky @SlackHQ I don't love that either. One consideration is that one part of the request could succeed and another could fail and you need to represent that somehow. I wish that was a 207 multistatus though rather than needing to check the errors JSON each time

• 
  Tigershout (@Tigershout2) reported 10 minutes ago

  @SlackHQ @superhabboboy This issue is back again for Android users for a couple of weeks now

• 
  Prinfection (@PrinnyForever) reported 10 minutes ago

  @chhopsky @SlackHQ if success, process normally, if error, put into error pipeline, good to go. Instead of "where ******** is my request, why is it being handled by this interceptor over here, why did it throw an exception"

• 
  christina 死神 (@chhopsky) reported 13 minutes ago

  @PrinnyForever @SlackHQ i'm gonna be honest i have no idea what you're talking about. sounds like user error or misunderstanding not using correct http codes is inting. "we just decided we're going to ignore the RFCs and do something that looks compatible but isnt" always ends up ******* people

• 
  Lavish (@lavishsaluja) reported 21 minutes ago

  @SlackHQ I had sent an email however did not get any response, sent another now - can you please help get it checked?

• 
  christina 死神 (@chhopsky) reported 21 minutes ago

  @PrinnyForever @SlackHQ in order for this to increase problems, a terrible number of things need to have gone horribly wrong already

• 
  christina 死神 (@chhopsky) reported 22 minutes ago

  @PrinnyForever @SlackHQ they all come with their own tooling but i've never come across one that fundamentally breaks if you attempt to use correct error codes. you map your exceptions to the right codes and let them bubble back up and if you're doing request validation in middleware 400 is built in?

• 
  Jason Karns (@jasonkarns) reported 23 minutes ago

  @SlackHQ i'm a little concerned that nobody on your team uses @1Password . I assume they don't because if they did, your cute "we not going to use a normal text input" 2fa code screen wouldn't be broken. Super lame.

• 
  Listening to my bones (@FadilaOum) reported 25 minutes ago

  Is @SlackHQ down or is it just me?

• 
  Panthère Noire (@mejumba) reported 28 minutes ago

  @CrnaGoraOne @SlackHQ Sorry to hear that. But what's the issue here? Connectivity?

• 
  Hawk, Max, and Sid Rao (@SamAndHawk) reported 30 minutes ago

  @slipdexic @SlackHQ @amazon Wait. Slack Calls didn’t have quality issues? But Huddles did? Slack Calls also use the SDK. We need to really dig in. Look forward to connecting after Easter break.

• 
  Kamruz Jaman (@jammykam) reported 33 minutes ago

  @nearmint90 @SlackHQ @rrecavar Same issue for me too, tried clearing cache and even reinstalling. Seems to work in some workspaces, but not others 😕

• 
  Prinfection (@PrinnyForever) reported 36 minutes ago

  @chhopsky @SlackHQ I've worked with frameworks that will hijack any non-success response into its own error handling pipe instead of having a request->response pipe and you then parse error Having a 200: {ok: false, *, errors:...} skips that and still contains the relevant info

• 
  MyPU (@mypuchd) reported 37 minutes ago

  @SlackHQ it should show error if max length is 10 and on click if image it should show which image i have selected and if i want to send single photo one by one, like whatsapp

• 
  Jayme "Danger" Howard (@isugimpy) reported 37 minutes ago

  @StagedGames @chhopsky @SlackHQ 4xx is not for when you can't establish communication. 4xx is a client-originated problem that causes the request to not complete as expected. Bad payload, lack of auth, incorrect method, rate limiting, etc. Returning a 200 with an error payload is incorrect by the RFC.

• 
  Kartik Krishnanand (@kkrishnanand) reported 42 minutes ago

  @SlackHQ dear Slack, please fix the iOS bug in which you mark the threads as read after they have been marked as read.

• 
  Prinfection (@PrinnyForever) reported 43 minutes ago

  @chhopsky @SlackHQ This third post is specifically with respect to "regardless of how malformed the request is" So there's a bifurcation of the handling into 1) We can parse your request enough to tell you you did something wrong, return 200, fail, errors 2) This is ******* nonsense, 500

• 
  Olivia Wertheimer (@kingdomfantasy6) reported 47 minutes ago

  Hey @SlackHQ, I haven't used your service in a hot minute, but please note for your higher ups that many of your users do not have IT people, do not understand words like "infrastructure", and shouldn't have to install certificates to use your service.

• 
  Rob Howard (@rfhow) reported 48 minutes ago

  I used GPT-4 to help me write some functions for a new @SlackHQ app for @_EveryAlt. It seems to have hallucinated some endpoints that didn’t exist — but overall saved me some time and mental energy. Also I freakin’ love building Slack apps!

• 
  christina 死神 (@chhopsky) reported 49 minutes ago

  @PrinnyForever @SlackHQ yeah i mean i've seen people use the recycle bin as 'easy access' storage shortcut too. people do things that are terrible ideas all the time if someone told me the company did stuff like that while i was interviewing i'd nod politely and decline to continue

• 
  Staged (@StagedGames) reported 50 minutes ago

  @chhopsky @isugimpy @SlackHQ I've seen them go both ways. I prefer having errors shown in response instead of via http codes, when possible, if I'm consuming an api. But you're probably right with respect to layers, I slept through networking.

• 
  CJ Hutsenpiller (@cjhuts) reported 50 minutes ago

  So to start, my service team gets asked many random questions. It's a safe bet that if I have a client asking this question, someone online is asking it as well. So I started by creating a @SlackHQ channel and... When someone asks a question, they post it in the channel.

• 
  Rahul Chetia (@ayoImNotTrippin) reported 52 minutes ago

  @SlackHQ @pxwhittle This seems to have been fixed. We are no longer seeing any problems with messages

• 
  Pablo__HappySoup__c (@pgonzaleznet) reported 52 minutes ago

  @SlackHQ @rrecavar This issue is happening again on Android. Are you aware?

• 
  liat benzur (she/her) (@LiatBenZur) reported 53 minutes ago

  I'm very impressed with @Anthropic's #Claude chatbot integration with @SlackHQ. But I hate that you cannot copy and paste the responses from Slack. Feels broken.

• 
  François Vaux (@madx) reported 55 minutes ago

  @SlackHQ unread indicators are broken on Android 😔

• 
  Rashid (@RashtheDude) reported 58 minutes ago

  @SlackHQ seems to be down.