Pingdom.com has a free one site monitoring service which is awesome

This *really* sucks.

I would like to hear from Linode how they plan on mitigating this ugliness that is apparently becoming quite common at Freemont. Given what I'm reading here and at webhostingtalk.com, this is becoming a bit of a joke. That is, unless you have a site at HE.

well linode can do any of these moving forward:

1) move out of HE - expensive and painful
2) add another upstream independent of HE's infra (linode owns the IP's afterall) - will add overhead to HE DC but will probably be worth it...
3) do 2 first while moving out and doing a 1.

Anybody know what carriers are at FMT1/FMT2? (And which is linode? I seem to have seen both ...)

HE peers with people, but I'm not sure if it's at those facilities. Not a lot of info on their website.



This I really do wonder about. fremont1.linode.com is in HE's ASN.

All great ideas, but to me, the travesty here is that Linode is continuing to sell bandwidth and space on the Fremont datacenter. That's kind of like saying "hey, we're going to charge you 100%, but you'll have uptime in the 90% range".

It's unethical.

If Linode was truly sorry about this situation, and was willing to fix it, they would at least stop offering Fremont as an option to NEW customers. What existing customers do (either moving to another DC or not) is a secondary concern.

it could be that the existing setup with HE means that the linodes servers has less upstream routes than what HE has available. By putting the API hosts on HE's network range they can get more redundancy. So even if the servers themselves are inaccessible due to a dos on the upstream(s) they're using or against linodes known IP ranges, the app servers for the API will still be accessible.

is everyone stable now? we're seeing occasional drops, but nothing like today.

The outage periods seem to be getting less frequent and not quite as long. I wasn't time stamping pings before so I don't know how long ago the last one was but it was out for at least a few minutes.

I don't really understand this.

The ASN says who owns the IP address block and who is going to announce it via BGP. (I think ... my understanding of BGP is high level only). As far as I could find, Linode doesn't have their own ASN so they always get their IP address ranges from their upstream provider and can't (1) move them across providers or (2) announce them to another transit provider.

But I could be wrong ...

well looks like the blocks Linode's (http://whois.arin.net/rest/net/NET-74-207-224-0-1/pft) but they've decided to chop it up, assign some to their HE DC and announce the blocks using HE's ASN.

Yup, I missed that.

Its back.

http://status.linode.com/

Network issue in Fremont

02:18AM (EDT): The network upstream of our Fremont facility appears to be experiencing stability issues once again at this time. We've alerted the network operation center at the Fremont facility to have them investigate. We'll provide more information once it is available.

While I agree with you, it's Caker's business, and it's up to him to run it to make money, which doesn't always make a good bed-fellow with ethics....

I've not had any issues in Dallas. Not that I know about anyway

You know, users who don't research have no one but themselves to blame. It's not like Linode has tried to hide the past fremont issues from the public.