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 |
|---|---|
| Creil, Hauts-de-France | 1 |
| New Delhi, NCT | 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:
-
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 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
-
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
-
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)
-
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
-
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.
-
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
-
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
-
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
-
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
-
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
-
Prinfection
(@PrinnyForever) reported
@chhopsky @SlackHQ No real argument can be made against that, though now that I'm thinking about it, not a single API I worked with indicated any standard of what to expect from failed responses, at least at the time It was usually "get failure, google error message" and hope it existed somewhere
-
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
-
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