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

Loading map, please wait...

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:


slack Hero Image

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.

Map Check Current Status

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Paris, Île-de-France 4
Bogotá, Distrito Capital de Bogotá 2
Bakersfield, CA 2
Chennai, TN 2
Montpellier, Occitanie 2
Ribeirão Preto, SP 1
Mexico City, CDMX 1
Sant Cugat del Vallès, Catalunya 1
Quito, Provincia de Pichincha 1
San Carlos, CA 1
Matlock, England 1
Trowbridge, England 1
Lyon, Auvergne-Rhône-Alpes 1
London, England 1
Zagreb, Grad Zagreb 1
Sydney, NSW 1
Moralzarzal, Comunidad de Madrid 1
Bradford, England 1
Vigneux-sur-Seine, Île-de-France 1
Edgware, England 1
Hässelby, Stockholm 1
Lutterbach, ACAL 1
Newcastle upon Tyne, England 1
Ruislip, England 1
Bègles, Nouvelle-Aquitaine 1
Sandefjord, Vestfold fylke 1
Uxbridge, England 1
East Hanover, NJ 1
Savigny-sur-Orge, Île-de-France 1
Antibes, Provence-Alpes-Côte d'Azur 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:

  • accidentalflyer I watched C-beams glitter in the dark 🇺🇦🇨🇦🇹🇼 (@accidentalflyer) reported

    @SlackHQ desktop app having lots of issues refreshing messages since latest update. Weird not the iOS app though.

  • RvLeshrac RvLeshrac (@RvLeshrac) reported

    @chhopsky @SlackHQ Yeah. They almost never respond with an error, and if they do respond with an error code, it *NEVER* includes **ANY** information about why there was an error. This is because a shitload of "security" ""trainers"" say you should never return errors, especially not informative.

  • BoredWallaby Melbalorean ࿗ (@BoredWallaby) reported

    @PaulHM55 @SlackHQ I completely agree with Paul. It's a bloody disaster. It's a total mess. It's slowing me down significantly.

  • JordiFun Jordi (@JordiFun) reported

    @SlackHQ Hi. Do you have any update on this issue? Or other reports? I'm unable to fix this issue on my side so far. Can I provide more info?

  • emwizzle Emily White (@emwizzle) reported

    @johnnyrodgersis @SlackHQ Would it be possible for the row to light up when we hover over "Complete," the mini clock or 3 dots? It's a little hard to line up when using a massive monitor like I do. Privileged monitor problems, but I'm already concerned about snoozing or deleting the wrong task. 5/

  • PrinnyForever Prinfection (@PrinnyForever) reported

    @chhopsky @SlackHQ Yeah, no, I agree, I said I had to background process on this point, because the nominal position I started with doesn't seem to actually have any value anywhere except "bad framework workaround" Even if you completely ignore the error code, it doesn't benefit you to not have it

  • emwizzle Emily White (@emwizzle) reported

    @johnnyrodgersis @SlackHQ That said, when we snooze something, Slack now scrolls all the way down and I have to scroll back up to continue to plough through reminders. I guess I should start at the bottom to do so to avoid this extra step? 2/

  • chhopsky christina 死神 (@chhopsky) reported

    @PrinnyForever @SlackHQ when you talk about being required to parse the body to handle the error, i honestly have no idea what you're talking about. generally that stuff is only useful if i, a human, am inspecting the response to tell how to write my program

  • chhopsky 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

  • martinkonicek Martin Konicek 🇺🇦 (@martinkonicek) reported

    With so much progress in NLP it's incredible how terrible @SlackHQ is at search. It looks like Slack might be using ElasticSearch and just matching words.

  • chhopsky christina 死神 (@chhopsky) reported

    @PrinnyForever @SlackHQ 200 > i trust everything worked 207 > i trust some things worked, data issues 400 > dont retry, request was incorrect 429 > back off using header info 503 > dead letter queue, retry sooner 502 > dead letter queue, retry later

  • chhopsky christina 死神 (@chhopsky) reported

    @PrinnyForever @SlackHQ i just described a bunch of main scenarios before that could be universally handled based on error code alone people dont do that. thats what im saying. if they do they tend to get fired. i dont know anyone who would hire someone who argued for overriding them

  • PrinnyForever Prinfection (@PrinnyForever) reported

    @chhopsky @SlackHQ within the realm of a 200 with error, we would individually learn what those meant, but any other error code was not documented as to what the expectation was for the consumer

  • martinbohman Martin Bohman (@martinbohman) reported

    @SlackHQ With the new "Later" replacing "Saved items", is there any way I can still show the Later/Saved in the right sidebar like before (where a thread opens from a channel)? Also: The "Later" view is broken, when navigating there messages don't show up until you switch tabs.

  • PR3SIDENT Cory Niblett (@PR3SIDENT) reported

    @SlackHQ "@ everyone can someone fix this?"

Map Check Current Status