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.
Full Outage Map
MultimediaProblems 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.
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.
-
App Crashing (43%)
-
Sign in (29%)
-
Connection (29%)
Live Outage Map
The most recent Slack outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Creil |
Connection | |
 New Delhi |
App Crashing | |
 Salt Lake City |
Sign in | |
| Miami |
App Crashing | |
 Bath |
Sign in | |
| Noida |
App Crashing |
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:
-
christina 死神
(@chhopsky) reported
@PrinnyForever @SlackHQ were they rolling their own http clients by hand? is this a 'we painted ourselves into a corner because we didnt know what we were doing and this is the only way out of the problem we created' ?
-
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.
-
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.
-
Rashid
(@RashtheDude) reported
@SlackHQ seems to be down.
-
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.
-
christina 死神
(@chhopsky) reported
@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?
-
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
-
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.
-
Prinfection
(@PrinnyForever) reported
@chhopsky @SlackHQ lol fair, but I never experienced a problem either maintaining the server or working as the client in that paradigm Not that I might not _now_, that was my first job, but I was responsible integrations with Intuit, Shopify, Stampsdotcom, and that pattern was the easiest
-
Prinfection
(@PrinnyForever) reported
@chhopsky @SlackHQ Yes, that's something I've experienced lol Granted, your primary intuition of > in order for this to increase problems, a terrible number of things need to have gone horribly wrong already is probably cogent The more I think about it the more it's starting to feel like CSS
-
Prinfection
(@PrinnyForever) reported
@chhopsky @SlackHQ Sure, and that's all great for expectations and high level, but what if you want to actively interface with the response of the error? Some of those would absolutely go into the diagrams bottom normal path, others frequently would return actionable data
-
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"
-
christina 死神
(@chhopsky) reported
@PrinnyForever @SlackHQ i'm struggling to understand what this problem is so you do something like await response = body=body, headers=headers) and then you just? dont. get the response. something eats it, because the server returned a 400?
-
Prinfection
(@PrinnyForever) reported
@chhopsky @SlackHQ Regardless of how your API works, I have to interface with the response body, so your "yellow light" still requires me to to read your doc and parse it If you have some internal custom error code, I still have to write the handler for that, regardless of the HTTP code
-
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.
-
Prinfection
(@PrinnyForever) reported
@chhopsky @SlackHQ To the best of my recollection, all issues that reach a level of "this is a pain to deal with" have been caused by client frameworks. Server rarely does anything more than make it harder to control the error code (500 codes are almost always automatic from other layers)
-
christina 死神
(@chhopsky) reported
@PrinnyForever @SlackHQ in order for this to increase problems, a terrible number of things need to have gone horribly wrong already
-
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
-
christina 死神
(@chhopsky) reported
@PrinnyForever @SlackHQ i suppose the important thing here is that "easy" isn't necessarily "good" because some problems are complex and ignoring their complexity doesn't make it go away
-
christina 死神
(@chhopsky) reported
@PrinnyForever @SlackHQ i mean i know not to retry a 400 because my request is bad, i know auth issue with 403, i know to back off with a 429, i know maybe retry a little later with a 503, service having bigger problems in 502 if 200 i know the request i had was actioned as intended
-
christina 死神
(@chhopsky) reported
@PrinnyForever @SlackHQ i'm struggling to understand what this problem is so you do something like await response = body=body, headers=headers) and then you just? dont. get the response. because the server returned a 400
-
Prinfection
(@PrinnyForever) reported
@chhopsky @SlackHQ Being able to differentiate if the API was responding properly or royally ******* up without having to parse individual error messages has generally been easier to work with and debug as far as integrations is concerned
-
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
-
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
-
Prinfection
(@PrinnyForever) reported
@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
-
Prinfection
(@PrinnyForever) reported
@chhopsky @SlackHQ The place my understanding exists in is that more granular responses are easier to more granularly respond to, especially if the API has some idiomatic stuff behind it that either you can or have to consider, instead of "it's an error and I still need to parse it anyway"
-
Rashid
(@RashtheDude) reported
@SlackHQ No error, just not able to connect on the Mac OS desktop and Android mobile.
-
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
-
Pablo__HappySoup__c
(@pgonzaleznet) reported
@SlackHQ @rrecavar This issue is happening again on Android. Are you aware?
-
Panthère Noire
(@mejumba) reported
@CrnaGoraOne @SlackHQ Sorry to hear that. But what's the issue here? Connectivity?