Live data from Hacker News

Linode Fremont servers are down

status.linode.com

1–10 of 32 posts

Re: Linode Fremont servers are down

#6
Networking outage again. Sigh. So glad I just moved my prod servers to gcloud last week...

To be fair to Linode, the Fremont outages always seem to be caused by HE.net (the "upstream provider"). Used to co-lo in the same datacenter and had issues like this constantly. Not sure what HE's problem is.

Re: Linode Fremont servers are down

#9
post #6

Networking outage again. Sigh. So glad I just moved my prod servers to gcloud last week... To be fair to Linode, the Fremont outages always seem to be caused by HE.net (the "upstream provider"). Used to co-lo in the same datacenter and had issues like this constantly. Not sure what HE's problem is.

The right solution is to get two upstreams and BGP.

...

which is unfortunately rather more difficult when you are in a datacenter owned by he.net :( It's possible, though, and I thought linode had done so, I think XO communications is in that building (that could be the other fremont he.net data center, it's been a while. Who owns XO these days? Verizon. I have been out for a while.)

I was in that same datacenter for a while, and I left due to power outages rather than network issues. (this was... man, almost a decade back now; most of that power equipment should have aged out by now.) - but he.net is a budget provider; I used them in my bgp mix for a lot longer...and usually they are fine. But I wouldn't use them without a backup. (he.net and cogent or whatever other cheap bandwidth is available usually is cheaper, and in aggregate, more reliable than a top tier provider on it's own.)

Re: Linode Fremont servers are down

#10
This is kinda what a status page is for, not the HN front page - linked being down is nothing new - it’s why we moved our stack away to AWS, what, seven years ago? Well, that and the horribly overloaded switches and poor implementation of the Xen packet scheduler that caused unacceptable latency spikes to memcached.

It’s great for hosting toy sites that sit on a single box and don’t have an uptime SLA - and people saying “well it’s cheap” - moving to AWS saved money, as we had to run big linodes for the workload purely for the additional internode bandwidth.

Post reply on HN