4 ms·
> curl http://joyent.com/ http://joyent.com/ curl: (7) couldn't connect to host Doesn't look like an SSL issue... Tracing the route to joyent.com (165.22
by Maxious 14y ago
> curl http://joyent.com/ http://joyent.com/
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
- Tim-Boss 14y agoAll I know is I get a time-out when connecting to joyent with https-everywhere running, and a normal webpage when it's disabled!
- Maxious 14y agohttp://www.downforeveryoneorjustme.com/joylent.com http://www.downforeveryoneorjustme.com/joylent.com It's not just you! http://joylent.com looks down from here. edit: 11:12 UTC it's back up again.
- fredsted 14y agoIt's joyent, not joylent.
- Gilly_LDN 14y agoJoylent? No L, Joyent.com
- sparkinson 14y ago> http://isitup.org/joyant.com http://isitup.org/joyant.com joyant.com is up. [...] ip of 208.91.197.128 Although the spelling was wrong, it clearly was having a few issues.
- punjabisingh 14y agoIt is not joyant.com, it is joyent.com.
- sparkinson 14y agoWell that was stupid of me :/