Updated Linode Plans / New Larger Linodes(blog.linode.com)
blog.linode.com
Updated Linode Plans / New Larger Linodes
https://blog.linode.com/2018/05/17/updated-linode-plans-new-larger-linodes/
19 comments
Seems like these have been priced to compete with Digital Ocean.
damn, still no Australian DC.
I'm stuck on Vultr still, since they're cheap and they have an Australian datacenter.
AU routing to JP is really bad (I get faster connections and better ping to TX-US servers on a lot of providers), and SG is like 120-160 ping which still kinda sucks.
I'm stuck on Vultr still, since they're cheap and they have an Australian datacenter.
AU routing to JP is really bad (I get faster connections and better ping to TX-US servers on a lot of providers), and SG is like 120-160 ping which still kinda sucks.
Are the cloud hosting services profitable at these very low prices or are they reducing the prices just to gain market share? If it is the latter, sooner or later they have to increase prices, no?
Linode has been around long enough (15 years) that I can't imagine they're operating at a loss. Their prices also haven't been nearly as dirt-cheap as other providers.
I would imagine most clouds will have to be pushing towards primitives (store, compute, network) being lost leaders. margins are on value-add services (software), deploy, monitor, scale etc.
OVH, Scaleway, Online.net have less expensive options usually with better hardware or dedicated servers.
OVH is not good at reliability. Entire data centers go down and there is no communication about it.
Scaleway has terrible hardware and is not reliable at all. You can turn off an instance and not be able to turn it on again because they've run out of resources. IPv6 addresses change every time your instance is stopped and started.
Online.net owns scaleway so I assume their level of service is similar but with better hardware.
Scaleway has terrible hardware and is not reliable at all. You can turn off an instance and not be able to turn it on again because they've run out of resources. IPv6 addresses change every time your instance is stopped and started.
Online.net owns scaleway so I assume their level of service is similar but with better hardware.
My experience with online.net/scaleway from just yesterday: their peering is quite bad, and their IPv6 is broken out of the box.
First, you only get a /127. Second, IPv6 is not activated by default, and for a good reason: when you do activate it, basic things like a apt-get update of a their vanilla distribution are broken.
Basically, their IPv6 peering seems so bad you can't even ping6 some ASN.
Practical example: on their Amsterdam DC, I couldn't even reach ftp.nl.debian.org (and before you ask, DNS worked just fine - I got the correct AAAA records)
When I asked for explanations and provided them a detailed ping6 and traceroute analysis showing where the problem was (and the same analysis from another server I had nearby that confirmed the problem was on online.net end), I was told to try the "rescue mode".
Lol no. I tried another company instead.
First, you only get a /127. Second, IPv6 is not activated by default, and for a good reason: when you do activate it, basic things like a apt-get update of a their vanilla distribution are broken.
Basically, their IPv6 peering seems so bad you can't even ping6 some ASN.
Practical example: on their Amsterdam DC, I couldn't even reach ftp.nl.debian.org (and before you ask, DNS worked just fine - I got the correct AAAA records)
When I asked for explanations and provided them a detailed ping6 and traceroute analysis showing where the problem was (and the same analysis from another server I had nearby that confirmed the problem was on online.net end), I was told to try the "rescue mode".
Lol no. I tried another company instead.
BTW a good read on the general "quality" of the IPv6 services offered at OVH/kimsufi but that I personally found to apply to at Online/scaleway is https://otacon22.com/2016/02/21/two-hosting-providers-ipv6-s...
I swear Linode came up with an excuse to reboot my servers at least once a month.
I've had numerous VM's with Linode for several years. I am also on DO and Vultr. The only reboots I get are for hardware failures and the recent Spectre patches. I would say on average, 1 reboot every 2 years. I could be lucky though.
Same.
I've had a handful of nodes on their $20 tier for 10+ years, and I think I've had two or three unannounced reboots in that time.
I've had a handful of nodes on their $20 tier for 10+ years, and I think I've had two or three unannounced reboots in that time.
I think mileage can vary. I had a couple of Linode VPSes get up into several hundred days until the Spectre/Meltdown upgrades..
Yes, That's what sticks out to me, time to patch, 6-9 months with a know, un-patched, vulnerability with no notice to customers. I wouldn't run a honey pot on Linode, their security record is abysmal and that's only the stuff we've found out about.
Check out Hetzner Cloud, too. Found performance and services much nicer than Scaleway, although in some places less functionality like firewalls
Still no word on renewable energy.
In my experience as a non-American, non-European developer, Vultr still beats them all for accepting crypto currency payments.