Slack Outage Map
The map below depicts the most recent cities worldwide where Slack users have reported problems and outages. If you are having an issue with Slack, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Slack users affected:
Check Current Status
Multimedia
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.
Check Current Status
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Suzano, SP | 1 |
| Curitiba, PR | 1 |
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:
-
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.
-
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.
-
Tigershout
(@Tigershout2) reported
@SlackHQ @superhabboboy This issue is back again for Android users for a couple of weeks now
-
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.
-
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
-
Pablo__HappySoup__c
(@pgonzaleznet) reported
@SlackHQ @rrecavar This issue is happening again on Android. Are you aware?
-
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
-
Rashid
(@RashtheDude) reported
@SlackHQ No error, just not able to connect on the Mac OS desktop and Android mobile.
-
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.
-
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.
-
Panthère Noire
(@mejumba) reported
@CrnaGoraOne @SlackHQ Sorry to hear that. But what's the issue here? Connectivity?
-
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
-
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.
-
François Vaux
(@madx) reported
@SlackHQ unread indicators are broken on Android 😔
-
christina 死神
(@chhopsky) reported
@PrinnyForever @SlackHQ in order for this to increase problems, a terrible number of things need to have gone horribly wrong already
Check Current Status