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 |
|---|---|
| Greenville, SC | 1 |
| Morsang-sur-Orge, Île-de-France | 1 |
| Greater Noida, UP | 1 |
| Lexington, MA | 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:
-
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.
-
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
-
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/
-
christina 死神
(@chhopsky) reported
@RvLeshrac @SlackHQ oh, i see the problem here they're stupid
-
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 From anecdote, most error codes that are not high level (like an auth failure or unreachable) usually require parsing the body anyway, at which point the body containing any code usually will contain the same useful information the code should
-
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
-
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)
-
AvalonStar
(@avaolon) reported
@SlackHQ latest bug in your terrible app, replicating images where they do not belong.... nice work as always
-
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?
-
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
-
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
-
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 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
-
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/
Check Current Status