According to their update site (now functioning): Between 08:38am PST and 08:47am PST Slack was serving errors for all requests to slack.com. This was caused by a code change that has now been reverted. The status.slack.com was also overloaded during this time and it may have been inaccessible. Looks like someone tested in Prod! On Tue, Mar 7, 2017 at 12:01 PM, Nathan Copeland via Outages < outages@outages.org> wrote:
Slack is responding again (OKC), albeit slowly.
On Tue, Mar 7, 2017 at 10:49 AM, Aaron via Outages <outages@outages.org> wrote:
No problems here in Kansas City.
On 3/7/2017 10:45 AM, Justin Head via Outages wrote:
Sorry! Something went wrong, but we're looking into it.
Their status page isn’t loading: https://status.slack.com
https://twitter.com/SlackHQ/status/839154497704321024
_______________________________________________ Outages mailing listOutages@outages.orghttps://puck.nether.net/mailman/listinfo/outages
-- ================================================================ Aaron Wendel Chief Technical Officer Wholesale Internet, Inc. (AS 32097)(816)550-9030 <(816)%20550-9030>http://www.wholesaleinternet.com ================================================================
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Regards, Nicole J. Miller