Live data from Hacker News

Linode is down again

status.linode.com

21–30 of 39 posts

Re: Linode is down again

#22

Are there clever solutions for routing traffic to other linode datacenters during one of these outages? I'm moving to AWS if I can't do something akin to elastic ip across datacenters. Linode currently only allows you to swap ip addresses within a dc.

use a DNS roundrobin with low TTLs and use monitoring to remove IPs when they go down. if you have 3 hosts in your production app's roundrobin, that makes it much less likely that they'll hit the dead server and if the TTL is 300, then it's only a few minute window anyway.

Re: Linode is down again

#23
post #16

Earlier quoted context omitted.

Linode has a 99.99% uptime guarantee, which amounts to 43 minutes and 12 seconds offline in a 30 day month. While I don't have a Linode in Freemont, their status page appears to indicate, at minimum, 1 hour of downtime. As repayment for the inconvenience, users get the lost time added to their balance.

With 99.99% uptime: .0001 * 30 * 24 * 60 = 4.32 minutes With 99.9% uptime: .001 * 30 * 24 * 60 = 43.2 minutes

I think he just typo'd the %. From the terms[1]:

    Linode.com provides a 99.9% uptime guarantee on all Linode hardware,
    and on network connectivity. In any given month, if your Linode is
    down for more than 0.1%, you may request a pro-rated credit for the
    down-time.
[1]: http://www.linode.com/tos.cfm

Re: Linode is down again

#24
Please change the title to indicate this is just the Fremont datacenter. The current title needlessly scares those of us with linodes in other datacenters.

Re: Linode is down again

#25
This is why Linode is better than many other services I've used. Every data center has outages, but at least Linode makes a point to update the server status promptly and (it seems) implement the fixes as quickly as possible.

rbranson is right: the responsibility for redundancy lies with you.

Re: Linode is down again

#26
post #22

Are there clever solutions for routing traffic to other linode datacenters during one of these outages? I'm moving to AWS if I can't do something akin to elastic ip across datacenters. Linode currently only allows you to swap ip addresses within a dc.

use a DNS roundrobin with low TTLs and use monitoring to remove IPs when they go down. if you have 3 hosts in your production app's roundrobin, that makes it much less likely that they'll hit the dead server and if the TTL is 300, then it's only a few minute window anyway.

That's material for a great blog post. Please write an article wherever you can and share!

Re: Linode is down again

#27

My Linode slice is in Atlanta, not Freemont, and it went down once today and once earlier this week.

I don't think that was the entire Atlanta data center, for what it's worth. Mine's in Atlanta too and I haven't had any recent downtime.

Re: Linode is down again

#28
Can anyone recommend good documentation on load balancing a LAMP app across multiple independent VPS providers?

We've had a high profile site affected by these Fremont outages so I'm thinking the only real solution is to have VPSs at Linode, Slicehost and EC2 then load balance among them. Of course, then the question is, what do you do when the load balancer goes down?

Re: Linode is down again

#29
post #17

Earlier quoted context omitted.

Care to enumerate a few of them?

More than one server across multiple datacenters is the only way. The use either a load balancer (which brings its own problems) or some kind of status aware DNS scheme to route traffic to live servers. I wish linode would offer some kind of high availability load balancing like amazon ec2 does, that really is a killer feature.

I wouldn't be so sure that ELB's are actually failing whole IP addresses across availability zones. Given the current ELB architecture is heavily dependent on dynamic DNS resolution, I am pretty suspicious that they are using DNS for failover. The separate set of DNS servers specifically for elb.amazonaws.com and the 60 second TTLs on the CNAMEs they generate seem to indicate this. Of course, there is no documentation to either confirm, or deny this. Amazon simply states in vague terms that it's highly available, but doesn't state how it's designed, or even possible failure outcomes.

Re: Linode is down again

#30
post #17

Remember guys & gals: this can happen to you. I am a fanatical Linode customer, and they are, in general, an extremely rock solid service, but that doesn't alleviate my responsibility to ensure my application is available regardless of datacenter outage. Power outages happen to EVERY datacenter. There are some very well documented and understood ways to alleviate this problem.

Care to enumerate a few of them?

DNS
Post reply on HN