I have ordered and bought the service in Saturday, May 31st, 2014 an HVM in UK.
Specification: 1GB Ram 55GB Raid10 disk 1 IPV4,5 IPV6 Quad Core (Fair Shared)
Uptime:
Uptime was a bit problematic. I think they had some issue with UK node back in june and july, i was informed in Client Page. And also i rebooted some time.
Ticket Response: I had opened some tickets regarding network support, network resolver from solusvm thing and IPV6 not reachable... They replied and helped me quite nicely ! :)
Disk Test:
dd if=/dev/zero of=test bs=16k count=8k conv=fdatasync && rm -rf test 8192+0 records in 8192+0 records out 134217728 bytes (134 MB) copied, 2.84822 s, 47.1 MB/s
dd if=/dev/zero of=test bs=16k count=8k conv=fdatasync && rm -rf test 8192+0 records in 8192+0 records out 134217728 bytes (134 MB) copied, 2.10908 s, 63.6 MB/s
dd if=/dev/zero of=test bs=16k count=8k conv=fdatasync && rm -rf test 8192+0 records in 8192+0 records out 134217728 bytes (134 MB) copied, 2.90431 s, 46.2 MB/s
NetworkTest:
I have been very happy with response to the vps from my country. This is very good than other EU and USA locations.
traceroute theguardian.co.uk
3 610.core1.hex.as20860.net (62.233.127.181) 48.324 ms 48.328 ms 48.515 ms 4 ae5.lon25.ip4.gtt.net (46.33.94.1) 1.695 ms 1.931 ms 1.927 ms 5 xe-7-3-0.lon11.ip4.gtt.net (89.149.186.21) 1.474 ms xe-7-2-0.lon11.ip4.gtt.net (89.149.180.101) 1.472 ms xe-3-2-0.lon11.ip4.gtt.net (89.149.187.126) 1.676 ms 6 be3008.ccr21.lon01.atlas.cogentco.com (130.117.15.21) 2.405 ms 2.349 ms 2.617 ms 7 te1-1.mag02.lon01.atlas.cogentco.com (154.54.74.110) 1.448 ms 1.475 ms 1.696 ms 8 149.11.142.74 (149.11.142.74) 2.224 ms 2.213 ms 2.208 ms
** traceroute vk.ru**
3 593.core1.thn.as20860.net (62.233.127.173) 2.055 ms 2.058 ms 2.053 ms 4 195.66.225.24 (195.66.225.24) 4.005 ms 4.015 ms 4.005 ms 5 se-tug2.nordu.net (109.105.102.45) 34.762 ms 34.770 ms 34.765 ms 6 ndn-gw.runnet.ru (109.105.102.46) 34.769 ms 37.007 ms 33.498 ms 7 m9-3-gw.msk.runnet.ru (194.85.40.133) 59.625 ms 59.466 ms 59.697 ms 8 gpt.msk.runnet.ru (194.190.254.66) 74.764 ms 74.728 ms 74.943 ms 9 89.111.161.129 (89.111.161.129) 84.819 ms 81.418 ms 82.213 ms
traceroute airtel.in
3 593.core1.thn.as20860.net (62.233.127.173) 1.314 ms 1.314 ms 1.533 ms 4 195.66.225.109 (195.66.225.109) 1.342 ms 1.561 ms 1.598 ms 5 203.101.95.89 (203.101.95.89) 160.385 ms 182.79.248.193 (182.79.248.193) 1 60.711 ms 160.709 ms
traceroute washingtonpost.com
3 610.core1.hex.as20860.net (62.233.127.181) 13.843 ms 14.057 ms 14.054 ms 4 202.core1.thn.as20860.net (62.233.127.11) 35.391 ms 35.616 ms 35.611 ms 5 40ge1-3.core1.lon2.he.net (195.66.224.21) 1.410 ms 7.656 ms 7.656 ms 6 100ge1-1.core1.nyc4.he.net (72.52.92.166) 67.132 ms 67.115 ms 67.095 ms 7 10ge4-1.core1.nyc5.he.net (184.105.213.218) 67.290 ms 67.517 ms 67.295 ms 8 lightower-fiber-networks.10gigabitethernet3-2.core1.nyc5.he.net (216.66.50.106) 67.256 ms 67.474 ms 67.244 ms 9 ae12.nycmnyzrj91.lightower.net (64.72.64.110) 67.291 ms 67.299 ms 67.288 ms 10 xe-0-3-0.nycmny83j41.lightower.net (72.22.160.132) 67.750 ms 67.552 ms 67.544 ms 11 xe-7-3-0.nwrknjmdj91.lightower.net (72.22.160.146) 67.991 ms 88.357 ms 88.310 ms 12 xe-3-1-1-asbnvacyj41.lightower.net (64.72.64.26) 73.156 ms 73.157 ms 73.335 ms 13 66.37.33.198.lightower.net (66.37.33.198) 75.841 ms 75.838 ms 75.832 ms 14 198.72.14.34 (198.72.14.34) 74.986 ms 74.967 ms 74.955 ms
Cachefly:
wget cachefly.cachefly.net/100mb.test -O /dev/null --2014-09-21 19:26:47-- http://cachefly.cachefly.net/100mb.test Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175 Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 104857600 (100M) [application/octet-stream] Saving to: ‘/dev/null’ 100%[================================================================>] 104,857,600 10.9MB/s in 9.2s
2014-09-21 19:26:57 (10.8 MB/s) - ‘/dev/null’ saved [104857600/104857600]
My View: I am ok with it and they know their business. I am quite happy. But disk and network could be better.