Live data from Hacker News

Slack is down

slack.com

31–40 of 65 posts

Re: Slack is down

#33
post #15

I didn't notice an interruption on the desktop client and it's been logged in for about 7 hours now and slack.com looks fine. Interestingly enough https://status.slack.com is currently down while curling status.slack.com returns a page that says it's moved to https://status.slack.com

I'm getting SSL errors from httpie:

http: error: SSLError: hostname 'status.slack.com' doesn't match either of '2015-06-25.dev.slack.com', 'slack.com', 'slack-files.com', 'slack-redir.com', 'slack-redir.net', 'dev.slack.com', '.dev.slack.com', '.enterprise.dev.slack.com', 'dev.slack-files.com', 'dev.slack-redir.com', 'dev.slack-redir.net'

Re: Slack is down

#34

Earlier quoted context omitted.

Wow, that is a fail hosting your status page in the same datacenter/environment as production. Honestly, a bit surprised, since Slack has always seemed on top of things.

If you can't get to the status page, it's probably a good indication the service is down :)

You're missing the point. It is for communication to your customers. Give them an outline of what is happening and an estimated eta to being back up.

Re: Slack is down

#35

I can't even get to status.slack.com ... I really hope that isn't on production infrastructure! GET https://slack.com/favicon.ico 503 Service Unavailable: Back-end server is at capacity

| "Back-end server is at capacity" DDoS?

503 = at capacity, default response an ELB returns when all the servers in the ELB are OutOfService (or missing).

Re: Slack is down

#36

I can't even get to status.slack.com ... I really hope that isn't on production infrastructure! GET https://slack.com/favicon.ico 503 Service Unavailable: Back-end server is at capacity

| "Back-end server is at capacity" DDoS?

Also AWS's error code for no healthy nodes in elb.

Re: Slack is down

#38

Just another reason for OSS projects to never trust closed (centralized!) protocols: no recourse when it (inevitably) hits the fan.

Except when you have to manage it yourself and something breaks or the infrastructure you have to manage needs managing.

Re: Slack is down

#39

Ironically, everyone at our company is heads down and working uninterruptedly. Productivity seems to have gone up without the interruptions!

Aside a jaunt over to HackerNews? ;)

I agree. As an aside, Slack has been getting so much usage internally (and everyone learned about @notifications) that it's turned into a massive source of interrupts. It's hard to idle in a number of channels without eventually getting @channel notifications. Perhaps it's a cultural thing here, but there's an expectation that questions are answered immediately unlike email.

I've taken to turning off Slack for periods every day to get work done.

Post reply on HN