Yep, It's been down since 5:58 PDT according to their status page and Tweets. Status page was throwing 500's in the first 10 minutes of outage but seems to have recovered.
> Status page was throwing 500's in the first 10 minutes of outage but seems to have recovered.
It's still doing that.
Serving static images (and who knows what else) with "Cache-Control: max-age=1" is probably not a good idea if a million frustrated customers are going to reload your status site every minute.
It's funny to imagine how Slack employees communicate when slack itself is down! Hopefully they have an internal instance separate from the public facing one.
I wanted to post a humourous image of the comments here...on Slack. So instead I went to each of my coworkers announcing that I have a humourous image...
Everyone is free to host their own IRC server using one of countless IRCds and connecting using one of countless clients And since it's an open protocol, you're free to write your own.
This is what happens when you decide to go with a closed, proprietary alternative.
18 comments
[ 1.8 ms ] story [ 18.4 ms ] threadIt's still doing that.
Serving static images (and who knows what else) with "Cache-Control: max-age=1" is probably not a good idea if a million frustrated customers are going to reload your status site every minute.
However, It doesn't explain my attempt to send a slack message asking if slack was down though. I guess I need to take the blame for that one.
2. Check HN to see if Slack is down, find this post
3. Attempt to slack this post to team
4. Facepalm
5. Remove headphones and shout "Slack is down!"
This is what happens when you decide to go with a closed, proprietary alternative.