Hacker News Reader

Comment by Maxious | Hacker News Reader

  curl: (7) couldn't connect to host

Doesn't look like an SSL issue...

  Tracing the route to joyent.com (165.225.132.33)

[...]

  8  *  *  *

  9 65.125.14.38 [AS 209] 312 msec 316 msec 308 msec

  10

  command timed-out

All I know is I get a time-out when connecting to joyent with https-everywhere running, and a normal webpage when it's disabled!

  It's not just you! http://joylent.com looks down from here.

edit: 11:12 UTC it's back up again.

It's joyent, not joylent.

    joyant.com is up. [...] ip of 208.91.197.128

Although the spelling was wrong, it clearly was having a few issues.

It is not joyant.com, it is joyent.com.

Well that was stupid of me :/

Joylent? No L, Joyent.com