Linode review
Posted on: 2012-09-01 | Categories:
Uncategorized
We use Xen VPS servers for most of our infrastructure in the UK and US. If you are looking for a reliable UK based Xen VPS look no further and go straight to http://www.xtrahost.co.uk – for the last 24 months their service was excellent. Network and Xen hosts rock stable. I can’t remember contacting their support except for usual matters such as PTR records etc
In the US we use Linode who initially seemed like a very good hosting partner. Unfortunately in recent months their service degraded significantly (at least in the Newark facility which we use). You can find the most serious issues on their status page: http://status.linode.com however as member of Linode support team explained to us:
“[…] If there is an issue that affects the majority of our customers, we will post it to http://status.linode.com. However, as the reboot only affected a couple of host machines, we opted to directly send tickets and emails to customers affected.”
Sadly official status page is just a tip of an iceberg. To give you a flavour of frequency of issues that are never posted on Linode’s status page, below you can find some of the recent Support Ticket:
2012-07-08 12:16:10 PM
|
Hello, We are currently observing 50% packet loss when pinging from us5 (or any other of our Linodes) to us10, see MTR report below: root@us5.xxx.xxx:~# mtr -c 10 -r us10.xxx.xxx HOST: us5.xxx.xxx Loss% Snt Last Avg Best Wrst StDev 1. router1-nac.linode.com 0.0% 10 0.7 0.8 0.5 1.9 0.4 2. us10.xxx.xxx 50.0% 10 657.5 600.2 495.5 667.7 69.7 It would seems there is degraded connectivity to us10 at this time? Regards, Chris |
—
|
Hello, We are currently looking into an issue related to networking to this host. We will update this ticket as soon as we have any additional information. Regards, Lee |
—
2012-07-11 03:26:46 PM
|
Hello, We are currently aware of an issue on the host that your Linode resides on (newark463). This issue requires a reboot to resolve. We do apologize for any inconvenience this issue may cause. Your patience and understanding is greatly appreciated. Please do not hesitate to contact us if you have any questions or concerns. Regards, Lukas |
—
2012-07-11 03:38:52 PM
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
|
We are currently measuring high packet loss and latency to us8, see MTR report from us-noc: root@us-noc.xxx:/# mtr -r -c 10 us8.xxx HOST: us-noc.xxx Loss% Snt Last Avg Best Wrst StDev 1. router1-atl.linode.com 0.0% 10 0.8 0.7 0.6 1.2 0.2 2. 64.22.106.9 0.0% 10 0.6 15.7 0.5 81.1 25.9 3. atl-core-g-g1-6.gnax.net 0.0% 10 0.6 24.2 0.6 88.1 31.3 4. 209.118.220.45 0.0% 10 1.7 7.6 0.8 67.1 20.9 5. ae1d0.mcr2.smyrna-ga.us.xo.n 0.0% 10 1.0 2.5 1.0 16.0 4.7 6. vb1201.rar3.washington-dc.us 0.0% 10 17.1 19.8 16.9 25.0 3.2 7. ae0d1.cir1.ashburn-va.us.xo. 0.0% 10 14.9 14.9 14.8 14.9 0.0 8. 206.111.0.66.ptr.us.xo.net 0.0% 10 16.2 16.4 16.1 17.2 0.3 9. vlan90.csw4.Washington1.Leve 0.0% 10 24.8 20.1 16.4 28.2 4.9 10. ae-92-92.ebr2.Washington1.Le 0.0% 10 16.7 16.7 16.5 17.9 0.4 11. ae-4-4.ebr2.Newark1.Level3.n 0.0% 10 21.5 25.8 20.9 32.1 4.1 12. ae-21-52.car1.Newark1.Level3 0.0% 10 20.7 29.9 20.3 105.2 26.6 13. NETCCESS.car1.Newark1.Level3 0.0% 10 19.9 19.9 19.8 20.3 0.1 14. 0.e3-3.tbr2.mmu.nac.net 0.0% 10 20.0 20.5 20.0 23.0 0.9 15. vlan805.esd1.mmu.nac.net 0.0% 10 20.3 20.3 20.2 20.5 0.1 16. 207.99.53.42 0.0% 10 20.9 21.8 20.2 34.1 4.3 17. us8.xxx.xxx 30.0% 10 363.8 330.7 293.8 363.8 26.2 |
—
|
Hello, Thank you for bringing this to our attention. Our network administrators are working to resolve any issues in our Newark, NJ datacenter at this time. I will pass this MTR report along to our administrators. We apologize for the inconvenience. Your patience and understand is greatly appreciated while we work to resolve this issue. Regards, Lukas |
—
2012-07-13 03:47:55 PM
|
Hello, In the last 30 minutes we experienced intermittent connectivity problems between Linodes in Newark facility. Are you aware of any issue with network/infrastructure at this time? Regards Chris |
—
|
Hello, Thanks for contacting Linode support. There was a transient network issue affecting some of our customers in the Newark datacenter. However, our network engineers were able to resolve the issue quickly. We sincerely apologize for the inconvenience. Please let us know if we may provide any further assistance. Regards, Jon |
2012-07-17 07:54:50 AM
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
|
Hello, Our monitoring systems recorded the following: ------------- Service: Ping Host: us10.xxx.xxx Address: 50.116.59.148 State: WARNING Date/Time: Tue Jul 17 01:54:58 UTC 2012 Additional Info: PING WARNING - Packet loss = 28%, RTA = 181.03 ms --------------- Service: Ping Host: us4.xxx.xxx Address: 50.116.59.210 State: WARNING Date/Time: Tue Jul 17 01:57:38 UTC 2012 Additional Info: PING WARNING - Packet loss = 16%, RTA = 182.57 ms --------------- Service: PING Host: us7.xxx.xxx Address: 50.116.53.144 State: WARNING Date/Time: Tue Jul 17 01:56:38 UTC 2012 Additional Info: PING WARNING - Packet loss = 28%, RTA = 182.48 ms --------------- Service: PING Host: us8.xxx.xxx Address: 50.116.58.215 State: WARNING Date/Time: Tue Jul 17 01:53:28 UTC 2012 Additional Info: PING WARNING - Packet loss = 28%, RTA = 180.92 ms ---------------- Was there a networking issue in Newark facility at around Tue Jul 17 01:53:28 UTC ? Regards, Chris |
—
|
Hello, Thank you for contacting us. There was a slight networking issue in our Newark datacenter at that time. If there's anything else we can do for you, please let us know. Regards, Doug |
2012-07-20 08:58:00 AM
|
Hello, The host your Linode resides on tokyo40 requires emergency maintenance at this time. We're working on bringing your host back online as quickly as possible and will update this ticket as soon as we have more information. Your patience and understanding is greatly appreciated. Regards, Jason |
—
|
Hello, Please accept our most sincere apologies for the continued downtime. The host that your Linode resides on experienced hardware failure. We are currently liaisoning with the datacenter staff to have the hard drives moved to a hot spare within the Tokyo facility. Once we have more information available we'll be certain to update this ticket. We appreciate your patience. Regards, Jason |
2012-08-10 06:41:45 PM
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
|
Hello, We are currently measuring high packet loss to us1 Linode. See MTR reports below: from 109.233.112.91: mtr -c 5 -r us1.xxx.xxx HOST: uk3.xxx.xxx Loss% Snt Last Avg Best Wrst StDev 1. 82.113.153.17 0.0% 5 0.4 0.4 0.4 0.5 0.0 2. linxe.ge-0-2-0.pr1.nac.net 0.0% 5 74.8 74.8 74.7 74.8 0.0 3. 0.lag2.tbr1.tl9.nac.net 40.0% 5 74.1 74.1 74.1 74.1 0.0 4. 0.e1-4.tbr1.mmu.nac.net 40.0% 5 75.1 75.1 75.0 75.2 0.1 5. vlan801.esd1.mmu.nac.net 40.0% 5 76.0 76.1 76.0 76.3 0.2 6. 207.99.53.42 20.0% 5 76.0 87.5 76.0 117.8 20.3 7. us1.xxx.xxx 20.0% 5 76.0 76.0 75.9 76.0 0.0 from: 109.233.112.107: mtr -c 5 -r us1.xxx.xxx HOST: uk5.xxx.xxx Loss% Snt Last Avg Best Wrst StDev 1. 82.113.153.17 0.0% 5 1.2 1.0 0.7 1.2 0.2 2. linxe.ge-0-2-0.pr1.nac.net 0.0% 5 75.2 75.4 75.1 76.0 0.4 3. 0.lag2.tbr1.tl9.nac.net 40.0% 5 74.9 75.5 74.9 75.8 0.5 4. 0.e1-4.tbr1.mmu.nac.net 40.0% 5 75.8 75.7 75.5 75.8 0.2 5. vlan801.esd1.mmu.nac.net 60.0% 5 76.9 78.7 76.9 80.5 2.5 6. 207.99.53.42 40.0% 5 103.2 85.6 76.7 103.2 15.3 7. us1.xxx.xxx 40.0% 5 74.5 74.4 74.2 74.5 0.2 Are you aware of any networking issues in Newark at the moment? Regards, Chris |
—
|
Hello, Thank you for providing the requested information. I've reached out to our upstream data provider (NAC) to see if they are able to identify and resolve this issue. We will update this ticket when we have additional information to provide. If you have any further questions or concerns in the meantime, please do not hesitate to contact us. Regards, Lukas |
—
 2012-08-21 07:58:33 AM
|
Hello, We are currently measuring high packet loss to/from us3, see mtr us1 -> us3 below: us1.xxx.xxx:~$ mtr -c 10 -r us3.xxx.xxx HOST: us1.xxx.xxx Loss% Snt Last Avg Best Wrst StDev 1. router1-nac.linode.com 0.0% 10 0.6 0.7 0.5 1.2 0.3 2. us3.xxx.xxx 70.0% 10 183.4 184.6 164.4 206.2 20.9 Is there a problem with the host and/or network at this time? Regards, Chris |
—
|
Hello, Thank you for contacting us. We're currently investigating an networking issue with newark468, the host that your us3 Linode resides on. We'll let you know once the issue has been resolved. In the meantime, if there's anything else we can do for you, please let us know. Regards, Doug |
2012-08-22 07:41:10 AM
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
|
We are currently experiencing massive packet loss between our US UK VPSs, see below: from uk2.xxx.xxx (82.113.145.109) Xtahost -> us4.xxx.xxx (50.116.59.210) Linode: mtr -c 10 -r us4.xxx.xxx HOST: uk2.xxx.xxx Loss% Snt Last Avg Best Wrst StDev 1. 82.113.153.17 0.0% 10 0.9 0.9 0.5 1.3 0.3 2. lon-ixn-edge-03.xtraordinary 0.0% 10 0.7 2.5 0.7 16.2 4.8 3. linx.peer.nac.net 40.0% 10 209.1 209.1 208.7 209.3 0.2 4. 0.e3-2.tbr2.tl9.nac.net 50.0% 10 208.8 208.8 208.6 209.1 0.2 5. 0.e1-4.tbr2.mmu.nac.net 40.0% 10 210.9 212.0 210.3 218.5 3.2 6. vlan805.esd1.mmu.nac.net 80.0% 10 210.8 210.9 210.8 211.0 0.2 7. 207.99.53.42 70.0% 10 209.4 209.2 209.1 209.4 0.1 8. us4.xxx.xxx 50.0% 10 210.4 210.3 209.8 210.6 0.3 from us4.xxx.xxx (50.116.59.210) Linode -> uk2.xxx.xxx (82.113.145.109) Xtahost: mtr -c 10 -r uk2.xxx.xxx HOST: us4.xxx.xxx Loss% Snt Last Avg Best Wrst StDev 1. router1-nac.linode.com 0.0% 10 0.5 4.7 0.5 13.2 5.3 2. 207.99.53.41 0.0% 10 0.4 1.1 0.4 5.8 1.7 3. vlan805.tbr2.mmu.nac.net 0.0% 10 0.4 0.6 0.3 1.7 0.4 4. 0.e1-1.tbr2.tl9.nac.net 0.0% 10 1.4 1.5 1.4 1.8 0.1 5. 0.ae1.pr3.tl9.nac.net 0.0% 10 1.4 1.6 1.4 2.3 0.3 6. linx-peering-02.xtraordinary 50.0% 10 210.2 209.8 209.5 210.2 0.3 7. uk2-1.xxx.xxx 50.0% 10 210.2 210.0 209.9 210.2 0.1 I don't think this is related to Linode infrastructure but just wanted to confirm there are no known issues on your end at this time? Regards, Chris |
—
|
Hello, Thank you for contacting us. We've received several such reports, and our investigations have identified that the issue is upstream of our network and affecting a subset of connections between Newark and London. We've reached out to our upstream providers in both locations to investigate the loss, and they're working to isolate the issue and get it resolved. Please let us know if there's anything else we can help you with in the meantime! Regards, Les |
—
In next few weeks we will be migrating all our US VPSs to a different Linode’s data centre, so I will keep you updated if Newark facility is a black sheep among other data centres operated by Linode and the company provides more reliable service in other locations. If not, the next step will be to switch to a different hosting partner.
Update: 6th Sep. 2012
In preparation to migration to another Linode’s facility I have analysed all Issues and Maintenance reports published at http://status.linode.com It seems Atlanta will be the facility where we will be moving to,
Issues
|
2012 |
2011 |
2010 |
Newark |
4 |
1 |
7 |
Fremont |
3 |
6 |
9 |
Atlanta |
2 |
2 |
3 |
Dallas |
2 |
1 |
10 |
Maintenance
|
2012 |
2011 |
2010 |
Newark |
2 |
2 |
2 |
Fremont |
2 |
2 |
1 |
Atlanta |
2 |
6 |
1 |
Dallas |
11 |
6 |
3 |
meldgaard
November 8, 2012 11:14
Found this page when googling linode american datacenter 🙂
Did you make the move to atlanta and did it help?!?
Chris
November 8, 2012 18:35
@meldgaard no, we haven’t moved to Atlanta yet. Perhaps a coincident… but since I published this review we haven’t had any more issues with Newark VPSs. It even survived recent hurricane Sandy without a minute of downtime.
Ruben Reyes
December 25, 2012 15:08
I have several Linodes hosted in the Newark datacenter for our client’s websites. The nodes themselves work flawlessly, the Linode Manager is a great tool, and support is very responsive.
However, in 2012 there have been too many major networking issues that blow any kind of decent SLA:
May 23 7:30pm – network completely down, it came back up around 9:30 with intermittent connectivity, and issue fully solved around 10:30pm (3hrs)
August 31, 3:30pm – network down until 4:30pm (1hr)
December 23, around 7pm until December 24 around 10am – high packet loss issues (over 12 hours)
For the time being we are staying using Linode but if this level of issues continue we will be forced to look for another provider.
Ruben