Live data from Hacker News

Joyent: 54+ hours of downtime

news.ycombinator.com

41–50 of 130 posts

Re: Joyent: 54+ hours of downtime

#41
post #37

Earlier quoted context omitted.

If you're on an old textdrive server, then you need to move, like we've been saying.

[deleted]

Just can't win.

I am reading all the comments, and I'm not spamming the thread. I'm having a conversation on a site that I frequent everyday. This is called being responsive.

Re: Joyent: 54+ hours of downtime

#42

Earlier quoted context omitted.

The way to make the pain stop No, the way to make the pain stop (and when I say pain, I mean hours and hours of downtime) is to work with a real managed hosting vendor that cares about your servers and your business, and to move your mission critical software off of commodity shared servers where it will get lost in a sea of customers, none of whom have an account executive, a sales representative, or assigned engine…

This has absolutely nothing to do with "Joyent Cloud". Nothing. The IaaS product has had 99.999-100% uptime this year. This is a 6 year old sharing hosting product that's currently free.

[deleted]

Re: Joyent: 54+ hours of downtime

#43
post #40

I get the frustration. I really do and I apologize for any bump like this. I'm the founder of those old textdrive "share hosting" servers (they really have nothing to do with Joyent's current product line). These servers are ~6 years old and they're largely populated by "lifetime" customers who have tricked out various bits of their accounts enough that an automated migration has been basically impossible. We've been…

oh dude, I have one of those lifetime accounts. Last summer, I looked into how to migrate, but I got lost in outdated pages. Can you drop some links in this thread? Maybe you can shut down jervis.textdrive.com if I migrate my account :)

Yes, you can contact support at help.joyent.com and they'll move your old textdrive account from jervis.

Re: Joyent: 54+ hours of downtime

#45
post #13

joyent had this sort of failure regularly about 4 years ago and continues to do so. Avoid.

Also incorrect. "About 4 years ago" we always did >99.99% uptimes even on the old textdrive stuff. I'd be happy to show all the old stats and graphs, we still have them.

Jason, you're experiencing a PR hiccup; it's not a big deal but it's also not clear that responding to every message in this thread is going to help you. Instead, why not (1) make things right for the OP and everyone else on Howe and (2) put a response on the blog?

You Joyent folks will never get a subset of your customers to migrate off textdrive hardware (so it's no use to keep yelling "just migrate!"). However, if you let those older servers fall apart you'll only get more negative PR.

Re: Joyent: 54+ hours of downtime

#46
post #3

I remember that chunkhost has really aggressive pricing.. And I remember there service being pretty good...

He's currently at "free", so get any more aggressive than that.

Paid for lifetime service in advance to help bootstrap your company, not "free".

Re: Joyent: 54+ hours of downtime

#47

Earlier quoted context omitted.

The way to make the pain stop No, the way to make the pain stop (and when I say pain, I mean hours and hours of downtime) is to work with a real managed hosting vendor that cares about your servers and your business, and to move your mission critical software off of commodity shared servers where it will get lost in a sea of customers, none of whom have an account executive, a sales representative, or assigned engine…

This has absolutely nothing to do with "Joyent Cloud". Nothing. The IaaS product has had 99.999-100% uptime this year. This is a 6 year old sharing hosting product that's currently free.

it's currently free? I pay $15 a month for it.

Re: Joyent: 54+ hours of downtime

#48
I have a lifetime account as well. Joyent's tech support has always been excellent. I take this as a wakeup call to get my stuff off of the old severs beyond that I can see little fault with Joyent.

Re: Joyent: 54+ hours of downtime

#49
post #29

Earlier quoted context omitted.

Offering a transition from FreeBSD to Solaris that requires the effort of the customer is not free. Asking a customer who knows FreeBSD to take on administration of a Solaris virtual server for your convenience is not reasonable. You are offering an unacceptable level of service to customers who have supported and recommended you from your early days. You were paid in advance for a lifetime of service. I took you on…

To even call this "Joyent" is misleading. The packing system is the same, it's BSD userland. The paths are the same. Everything is the same. The kernel shouldn't matter. And if you had told support that you wanted us to just migrate you because nothing was out of the ordinary, what would they have done? They would have migrated you .... And this has been quite a good deal for you. The logic of moving from something t…

I don't think that there's anything weird or "interesting" about the logic of moving from unreliable hosting to something more costly but more reliable. (Also, in the context of hosting service, I don't really think it's accurate to say it "costs you nothing" if it suffers a multi-day outage while you have customer servers hosted on it...)

Re: Joyent: 54+ hours of downtime

#50

I get the frustration. I really do and I apologize for any bump like this. I'm the founder of those old textdrive "share hosting" servers (they really have nothing to do with Joyent's current product line). These servers are ~6 years old and they're largely populated by "lifetime" customers who have tricked out various bits of their accounts enough that an automated migration has been basically impossible. We've been…

Is the personal account information for the submitting individual really necessary for your point? Did the submitter give you permission to tell us about his ticket history and account actions?

Although relatively harmless, it seems like planting the seed to a disregard for privacy.

Post reply on HN