Slack

Is Slack down?

No problems detected

If you are having issues, please submit a report below.

Slack is a cloud-based set of proprietary collaboration tools and services. It's meant for teams and workplaces, can be used across multiple devices and platforms.

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.

Slack Outage Chart 01/21/2026 05:45

At the moment, we haven't detected any problems at Slack. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

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

  1. App Crashing (50%)

    App Crashing (50%)

  2. Sign in (25%)

    Sign in (25%)

  3. Connection (25%)

    Connection (25%)

Live Outage Map

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

Loading map, please wait...
City Problem Type Report Time
FranceCreil Connection
IndiaNew Delhi App Crashing
United StatesSalt Lake City Sign in
United StatesMiami App Crashing
United KingdomBath Sign in
IndiaNoida App Crashing
Map 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:

  • FadilaOum Listening to my bones (@FadilaOum) reported

    Is @SlackHQ down or is it just me?

  • pgonzaleznet Pablo__HappySoup__c (@pgonzaleznet) reported

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

  • cjhuts CJ Hutsenpiller (@cjhuts) reported

    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.

  • Rdzinieks1 Rīdzinieks (@Rdzinieks1) reported

    @SlackHQ Why you again removed latest version? Please fix MSI version for 4.31 so it stays as well in program files, not fully in appdata

  • chhopsky christina 死神 (@chhopsky) reported

    @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

  • chhopsky christina 死神 (@chhopsky) reported

    @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

  • PrinnyForever Prinfection (@PrinnyForever) reported

    @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"

  • StagedGames Staged (@StagedGames) reported

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

  • RashtheDude Rashid (@RashtheDude) reported

    @SlackHQ seems to be down.

  • kanstin David C 🐺🚀🛰️📡 (@kanstin) reported

    @slackhq how do I report a bug in slack? I have an easy reproducible test case that demonstrates the problem.

  • rfhow Rob Howard (@rfhow) reported

    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!

  • RashtheDude Rashid (@RashtheDude) reported

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

  • kingdomfantasy6 Olivia Wertheimer (@kingdomfantasy6) reported

    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.

  • madx François Vaux (@madx) reported

    @SlackHQ unread indicators are broken on Android 😔

  • zastavropoulos Stavropoulos Zacharias (@zastavropoulos) reported

    @ArjanCodes Yep! Something isn't right today. I faced lots of issues with @SlackHQ today :/

  • Tigershout2 Tigershout (@Tigershout2) reported

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

  • johnsmallmtn John Small Mountain (@johnsmallmtn) reported

    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.

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

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

  • jasonkarns Jason Karns (@jasonkarns) reported

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

  • kkrishnanand Kartik Krishnanand (@kkrishnanand) reported

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

  • LiatBenZur liat benzur (she/her) (@LiatBenZur) reported

    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.

  • mejumba Panthère Noire (@mejumba) reported

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

  • kzeillmann Kevin Zeillmann (@kzeillmann) reported

    @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

  • lavishsaluja Lavish (@lavishsaluja) reported

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

  • jammykam Kamruz Jaman (@jammykam) reported

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

  • ____guerra Federico Guerinoni (@____guerra) reported

    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

  • isugimpy Jayme "Danger" Howard (@isugimpy) reported

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

  • mypuchd MyPU (@mypuchd) reported

    @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

  • PrinnyForever Prinfection (@PrinnyForever) reported

    @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

  • ayoImNotTrippin Rahul Chetia (@ayoImNotTrippin) reported

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