clojurebridge 2017-05-27

It's back up now. Waiting to hear for the ClojureBridge folks about what caused it (since the fix was a DNS update).