Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Joyent: 54+ hours of downtime

news.ycombinator.com

Post reply on HN
Print view View original

101–110 of 130 posts

Re: Joyent: 54+ hours of downtime

#101

Post by visakhcr »

Digging Techcrunch got me this story: Twitter and Joyent splits (Circa Jan 31, 2008)

http://techcrunch.com/2008/01/31/twitter-and-joyent-split-am...

Twitter moved to Verio and here's Biz Stone's reply to Techcrunch:

We’re still very much engaged in our efforts to bring solid reliability to Twitter. Achieving our goals is a sustained effort, not an overnight fix. Performance is our most important measure of success and we appreciate both the patience and frustration folks are sharing with us.

With regard to discussing technical specifics about last night’s efforts, we’ll be more keen to do that once we have a chance to come up for air and cover it with some perspective.

Re: Joyent: 54+ hours of downtime

#102

Post by prodigal_erik »

jasonhoffman wrote: post #35
tastybites wrote: post #23

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.

"Some products are better" isn't tenable. Regardless of whatever market segmentation you care to do, this extended outage is going to affect customers' perceptions of the diligence of your entire technical staff. If it's impractical to meet these obligations with the same quality as your other products, the thing to do is to buy the obligations out or sell off the unit delivering on them.

Re: Joyent: 54+ hours of downtime

#103

Post by ZeroGravitas »

sayrer wrote: post #40
jasonhoffman wrote: post #18

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 :)

Not till they move mine too, but this thread has reminded me to get the migration done.

Re: Joyent: 54+ hours of downtime

#104

Post by gexla »

Klinky wrote: post #84
jasonhoffman wrote: post #20

Earlier quoted context omitted.

Hi. This is Jason Hoffman, Dean's co-founder of Textdrive and current founder at Joyent. If you're worried about your sites on the old Pendrell, then go over to support and take the upgrade that's been offered and migrate off.

Wow, a comment like this makes me glad I am with Linode. Way to not value all of your customers.

What's wrong with offering a solution? If you are having problems with that server, allow us to migrate you to another one. Sounds fair enough to me.

Re: Joyent: 54+ hours of downtime

#105

Post by jacques_chester »

dotBen wrote: post #98
jacques_chester wrote: post #86

Earlier quoted context omitted.

I had a server go down twice due to outages at their Fremont data centre, but otherwise I've been very pleased.

I'm also a massive Linode fan, but here's my monthly HE-Fremont Data Center rant... don't run anything out of there (regardless of whether it is through Linode or a 3rd party). The overal quality of their (Hurricane Electric, not Linode) operation is poor, historically they have been lax on shady people colo'ing rack space in Fremont (google hurricane electric mccolo ), HE-1 is full and so little room for expansion a…

So I've learnt since the first time things went kerflooie.

However I chose Fremont because it's the closest datacentre they have to Australia. Most of my readers are here.

Re: Joyent: 54+ hours of downtime

#106

Post by swombat »

enduser wrote: post #63
swombat wrote: post #60

Earlier quoted context omitted.

Seems like the lesson for you here is: never give free hosting, people feel terribly entitled once they have it and their negative feedback may cause trouble in your actual products.

The hosting is not free. It was paid for in advance.

Paid in advance is still free on a month-to-month basis. That's what I meant.

Paying for a service forever in advance is a devious mis-alignment of incentives. The customer will feel that they are owed everything. The business of it won't work out.

As I said, the lesson is, don't give shit for free - even for an initial payment. Ongoing services need to be paid for in an ongoing manner.

Re: Joyent: 54+ hours of downtime

#107

Post by josephb »

jacques_chester wrote: post #86
jefe78 wrote: post #12

Earlier quoted context omitted.

+1 for Linode. I've literally never had a problem. I'm a huge fan and I'm picky as hell.

I had a server go down twice due to outages at their Fremont data centre, but otherwise I've been very pleased.

For those of us in AU, the Fremont DC is the best choice for us Linode customers.

However, I've learnt, and hopefully have others, that having everything in one basket isn't the best option, even with how excellent Linode are, they are at the mercy of HE etc.

So now we have a split between Fremont, Dallas & Newark.

It's worked pretty well, we are most happy.

Anyone running a large app or site would do well to run multiple systems with Linode across multiple sites where possible.

Re: Joyent: 54+ hours of downtime

#108

Post by jacques_chester »

josephb wrote: post #107
jacques_chester wrote: post #86

Earlier quoted context omitted.

I had a server go down twice due to outages at their Fremont data centre, but otherwise I've been very pleased.

For those of us in AU, the Fremont DC is the best choice for us Linode customers. However, I've learnt, and hopefully have others, that having everything in one basket isn't the best option, even with how excellent Linode are, they are at the mercy of HE etc. So now we have a split between Fremont, Dallas & Newark. It's worked pretty well, we are most happy. Anyone running a large app or site would do well to run mul…

It's just a pity Australian bandwidth is so ruinous, or I'd move my servers here.

Re: Joyent: 54+ hours of downtime

#109

Post by Klinky »

gexla wrote: post #104
Klinky wrote: post #84

Earlier quoted context omitted.

Wow, a comment like this makes me glad I am with Linode. Way to not value all of your customers.

What's wrong with offering a solution? If you are having problems with that server, allow us to migrate you to another one. Sounds fair enough to me.

No, it sounds more like "you're costing us money now, so we don't give a crap about maintaining those servers anymore. If you really care about stability then pay us more money for our other service."

They should pull up the old contract, find out exactly what can be done to either terminate or transition people to the new services and get it over with. This seems like they're just letting the issue run off the rails and then when people complain that a server is down an extended period of time, a server that they paid a lifetime membership fee for, they start spouting off that these people are whiny freeloaders.

If the servers are old and rickety, migrate them to the lowest level of your new service for the same cost as what the person paid for initially, given that they've already paid in full, this would put the customer cost at $0. If you don't want to do that, then maintain the old servers and give them as much love as you would your other customers. That love includes not getting pissy in public about people whining over "free" servers, especially when they _weren't free_.

Re: Joyent: 54+ hours of downtime

#110

Post by dotBen »

jacques_chester wrote: post #105
dotBen wrote: post #98

Earlier quoted context omitted.

I'm also a massive Linode fan, but here's my monthly HE-Fremont Data Center rant... don't run anything out of there (regardless of whether it is through Linode or a 3rd party). The overal quality of their (Hurricane Electric, not Linode) operation is poor, historically they have been lax on shady people colo'ing rack space in Fremont (google hurricane electric mccolo ), HE-1 is full and so little room for expansion a…

So I've learnt since the first time things went kerflooie. However I chose Fremont because it's the closest datacentre they have to Australia. Most of my readers are here.

Are the ping times and connectivity noticiably different for you between Linode's Fremont DC vs Linode's Dallas DC?

(see http://www.linode.com/speedtest/ for pingable hostnames of servers in each DC + speedtests)

If you do want to move, you can put in a ticket and they can move you between DC's with no downtime I believe or just replicate your instance and switch IP's.

Post reply on HN