Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If this is gloating about the EC2 outage, then ugh. I can't find out if it is because the whole of joyent.com is actually down for me (net::ERR_CONNECTION_TIMED_OUT)


Yep, same for me. Delicious irony in my opinion


If a company is actually stupid enough to say "If I was your cloud provider, I'd never let you down" then I immediately lose all interest in working with that company. Childish and they obviously have no appreciation for how hard it is to properly run a hosting company.


They don't want reddit's business. They know it's not real. But they also know reddit's general user wants reddit to be have better uptime. And that the user will upvote a story offering that (with cats at that).

This is just a PR stunt to gain some customers. Simple, but apparently working (even here on HN, which is quite sad).


I'm pretty sure they have a decent idea of what's involved running a hosting company being as how they're a huge hosting company.

I think what they've done is great, they're appealing to the users by showing they are users and they'll probably get a crapload of traffic because of it whether they land Reddit or not. It's already landed them the #1 slot on HN, a site where AWS staff post AWS updates!


In the professional tech world, not ALL exposure is good exposure. With this post they look like immature kids, and then when their post and entire site goes down, they look incompetent in front of the very people they want to convince.

An informative post explaining the hardships of uptime and reliability in simple words, and how they do their best to keep adding 9's, would have been so much better.



Exactly, they should have done more of that.


Down for me too. Rather embarrassing if I do say so.


Try disabling https-everywhere for joyent.com. Worked for me!


Apparently they're having some SSL issues, try disabling "https everywhere" or any other similar browser addons I presume you're running!


> curl 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


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!


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.


It's joyent, not joylent.


> 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.


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


Well that was stupid of me :/


Joylent? No L, Joyent.com


Uh, no, this is how about switching to the main supporters of node.js would immediately remove a problem that the #1 vps provider can't handle.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: