• Announcements

    • MannDude

      Current state of vpsBoard   02/04/2017

      Dear vpsBoard members and guests:

      Over the last year or two vpsBoard activity and traffic has dwindled. I have had a change of career and interests, and as such am no longer an active member of the web hosting industry.

      Due to time constraints and new interests I no longer wish to continue to maintain vpsBoard. The web site will remain only as an archive to preserve and showcase some of the great material, guides, and industry news that has been generated by members, some of which I remain in contact to this very day and now regard as personal friends.

      I want to thank all of our members who helped make vpsBoard the fastest growing industry forum. In it's prime it was an active and ripe source of activity, news, guides and just general off-topic banter and fun.

      I wish all members and guests the very best, whether it be with your business or your personal projects.

      -MannDude
dave

SecureDragon VPS 1+ Year Review

25 posts in this topic

I’ve used SecureDragon for over a year now (since November 2012), and I wanted to give them credit for providing a great service. I’ve used many different services, and I think this is one of the best.

SecureDragon became popular for providing small VPS’s with even less than 128MB RAM, and my first one was a 64MB OpenVZ VPS at their Florida location. After they began offering service in Denver, I picked up another 64MB OpenVZ VPS in Denver. I’ve used both of these mostly as VPNs.

The network quality for VPN use out of their Denver location (at Handy Networks) is the best I’ve ever used. Of course this can change over time, but so far so good.

The test for a VPN isn’t just connectivity from you to the VPN, but also from the VPN to various CDNs. The speed test from your VPN server may be great, but trying to stream over it may be a challenge if the network quality is poor. If you want a VPS for VPN use, my advice is to get a Dragon in Denver.

I recently picked up a new 1GB OpenVZ VPS with SecureDragon in Denver to try to use for web hosting, and a second one in Los Angeles for monitoring, DNS, and backups.

I usually prefer to use 512MB Xen or KVM VPS’s for web hosting. I last tried OpenVZ many years ago for web hosting and found it using way more RAM than it did on my Xen server, and I’ve avoided it since then. But a good deal on the SecureDragon VPS came up (tweet), and with the memory management changes and introduction of VSWAP for OpenVZ, I thought I’d give it another try.

I’m finding that a similar setup on OpenVZ is using a bit more than twice as much RAM as on Xen or KVM. Whereas I’m using around 250MB RAM on Xen or KVM, OpenVZ is consuming around 530MB. Everything is nice and snappy so far, though, so I’ll continue to use it. It’s a good thing it’s 1GB for OpenVZ instead of 512MB!

I’ve only had to contact support once, for a simple matter, but the response was very quick and polite. Everything else just works.

They also offer KVM VPS’s, DDOS protected OpenVZ VPS’s, backup servers, and CPanel hosting, though I haven’t used their other services.

They just sent out an email announcing that they’ll be adding four new locations: Atlanta GA, Dallas TX, Phoenix AZ, and Weehawken NJ to add to their five existing locations (Tampa FL, Denver CO, Los Angeles CA, Chicago IL, and Portland OR). I wish them lots of success–they deserve it.
 

1 person likes this

Share this post


Link to post
Share on other sites

nice review  :)

 

The real question is: What is your budget?

1 person likes this

Share this post


Link to post
Share on other sites

Thanks dave!

 

Living in Colorado myself, I'm a bit biased when it comes to my favorite location and network (I'm connected to my VPN in Denver all of the time and Amazon VOD, Xfinity VOD, and Netflix are indeed smoother than when I was in FL). I'm glad others are getting to enjoy it as much as I do.

 

Those 1GB plans were selling fast and were mostly bought by current clients who had a <128MB VPS with us originally so I'm sure a lot of people are in the same boat as you so I'm very happy to hear you're expanding to hosting other services with us.

 

In addition to the locations you mentioned we're hoping to add an Oregon and Ohio location this month also (we were hoping talks would go better with a Virginia data center but at the moment it's not looking so good).

 

Thanks again for taking the time to write such a detailed review about us. :)

Share this post


Link to post
Share on other sites

As a SD customer myself (Since June 2012), I agree with you. I absolutely love their service and the way Joe runs things. It's great!

Share this post


Link to post
Share on other sites

Yep, Joe runs a tight ship. Good service. :)

Share this post


Link to post
Share on other sites

I've sent in a few tickets and every time I've been surprised by the fast and accurate response that I received.

Every time there was a helpful tone and a will to solve the problem, even in the cases where it was my fault and I shouldn't contact the support.

Currently using one as vpn and the other as a cPanel dns-only.

Share this post


Link to post
Share on other sites

In addition to the locations you mentioned we're hoping to add an Oregon and Ohio location this month also (we were hoping talks would go better with a Virginia data center but at the moment it's not looking so good).

 

Thanks again for taking the time to write such a detailed review about us. :)

 

Kinda curious to see how the Ohio location works out, last time I tested my latency from southern Indiana was better to my Tampa ovz than Denver, but that probably has something to do with E-Solution's DC now being owned by my ISP

 

Are you shipping single servers to E-sol in Ohio and the other new DCs?

Share this post


Link to post
Share on other sites

Kinda curious to see how the Ohio location works out, last time I tested my latency from southern Indiana was better to my Tampa ovz than Denver, but that probably has something to do with E-Solution's DC now being owned by my ISP

 

Are you shipping single servers to E-sol in Ohio and the other new DCs?

The Ohio location is still up in the air. We got a quote and are still in talks to see what we can and can't do.

 

All new locations are getting a single OpenVZ node for now. We've decided to move away from getting cabinets since they are not cost effective for us (the shared bandwidth in particular doesn't meet our needs).

Share this post


Link to post
Share on other sites

(the shared bandwidth in particular doesn't meet our needs).

 

Isn't this exactly what you get with shared colocation thought,, shared bandwidth from their BGP blend?

Share this post


Link to post
Share on other sites

Isn't this exactly what you get with shared colocation thought,, shared bandwidth from their BGP blend?

I mean us having multiple servers sharing the same bandwidth pool. We like having the ability to adjust bandwidth commits on a per server basis.

Share this post


Link to post
Share on other sites

From my experience SD has always provided stable servers (the vps was from a friend).

And just one complain, damint I couldn't get the promo, it was a very nice offer.

Keep it up KuJoe.

Share this post


Link to post
Share on other sites

Just wanted to update those who were interested in our Ohio location. We've negotiated a better price and hope to have an OpenVZ node online by the end of the month. :)

 

Additionally the nodes have arrived in New Jersey and Georgia already and we're just waiting for our new IPs from ARIN to get these rolling. The nodes for Arizona and Texas should be shipping out soon also.

2 people like this

Share this post


Link to post
Share on other sites

Hulu started blocking all 4 of my securedragon IP addresses today (2 in Denver, plus Los Angeles and Florida) -- both the older 198.57. addresses and the newer 162.211. addresses.

 

So that's kind of sad.  The servers themselves are still running well, though.

 

Share this post


Link to post
Share on other sites

That sucks. I just tried to watch Hulu with some of my VPNs (Secure Dragon IPs and one of my dedicated servers with another provider) and they're blocked also. I guess Hulu started cracking down or updated a database recently since they even have our new IPs blocked also.

Share this post


Link to post
Share on other sites

Hulu started blocking all 4 of my securedragon IP addresses today (2 in Denver, plus Los Angeles and Florida) -- both the older 198.57. addresses and the newer 162.211. addresses.

 

So that's kind of sad.  The servers themselves are still running well, though.

We've found a workaround for this and will be implementing it shortly. It won't be ideal for everybody but it's better than nothing.

1 person likes this

Share this post


Link to post
Share on other sites

We've found a workaround for this and will be implementing it shortly. It won't be ideal for everybody but it's better than nothing.

 

That's good news.  Does it involve making some changes to the vps, or should it just start working?

Share this post


Link to post
Share on other sites

We're still looking into how to implement the workaround. I have a few ideas but I won't be able to test them until tonight or tomorrow. One will require some modification while the other should be seemless.

Edited by KuJoe

Share this post


Link to post
Share on other sites

I don't understand why Hulu would bother to block the IPs. Don't you need to pay hulu subscription to watch it? So they want to have less subscriptions?

Share this post


Link to post
Share on other sites

I don't have a paid Hulu account so I only tested their free version. I wonder if the IPs are blocked for Hulu Plus. Either way, we're getting IPs from a residential ISPs for our clients to use for Hulu and other sites that block "anonymous" IPs. I'm a bit medicated at the moment so I'll have more details later.

Share this post


Link to post
Share on other sites

  • Similar Content

    • By wlanboy
      Provider: VirtWire 
      Plan: OpenVZ 512 MB VPS
      Price: $6 per year
      Location: Miama, FL
      Purchased: 09/2015

      Hardware information:
      cat /proc/cpuinfo (1x) processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz stepping : 3 microcode : 28 cpu MHz : 3501.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt bogomips : 7000.24 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management:  
      cat /proc/meminfo MemTotal: 524288 kB MemFree: 436212 kB Cached: 23984 kB Buffers: 0 kB Active: 39992 kB Inactive: 39420 kB Active(anon): 30536 kB Inactive(anon): 27548 kB Active(file): 9456 kB Inactive(file): 11872 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 262144 kB SwapFree: 234448 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 58084 kB Shmem: 2656 kB Slab: 8656 kB SReclaimable: 2316 kB SUnreclaim: 6340 kB  
      dd 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, 0.668 s, 201 MB/s  
      Network:
      1 IPv4 /64 IPv6 Subnet 1024 GB Transfer traceroute dvhn.nl
      traceroute to dvhn.nl (52.30.49.180), 30 hops max, 60 byte packets 2 173.44.32.253.static.quadranet.com (173.44.32.253) 0.189 ms 0.215 ms 0.182 ms 3 xe-0-2-0-1.r05.miamfl02.us.bb.gin.ntt.net (129.250.203.9) 0.728 ms 0.749 ms 0.785 ms 4 ae-4.r20.miamfl02.us.bb.gin.ntt.net (129.250.2.184) 0.492 ms 0.558 ms 0.593 ms 5 ae-4.r23.asbnva02.us.bb.gin.ntt.net (129.250.2.86) 30.780 ms 30.798 ms 30.839 ms 6 ae-2.r25.amstnl02.nl.bb.gin.ntt.net (129.250.6.163) 113.280 ms 121.894 ms 111.328 ms 7 ae-1.r03.amstnl02.nl.bb.gin.ntt.net (129.250.2.147) 120.284 ms 114.583 ms 118.774 ms 8 ae-3.r03.londen05.uk.bb.gin.ntt.net (129.250.6.26) 111.775 ms 108.220 ms 116.006 ms 9 ae-5.r02.londen05.uk.bb.gin.ntt.net (129.250.6.229) 129.447 ms 121.353 ms 121.542 ms 10 82.112.115.190 (82.112.115.190) 108.184 ms 107.653 ms 82.112.115.162 (82.112.115.162) 113.662 ms 11 * * * 12 * * 176.32.106.36 (176.32.106.36) 125.399 ms 13 178.236.0.225 (178.236.0.225) 125.679 ms 176.32.106.36 (176.32.106.36) 117.054 ms 178.236.0.225 (178.236.0.225) 123.190 ms 14 178.236.0.191 (178.236.0.191) 126.639 ms 178.236.0.208 (178.236.0.208) 132.311 ms 135.978 ms 15 178.236.0.208 (178.236.0.208) 126.500 ms 178.236.0.210 (178.236.0.210) 134.000 ms 178.236.0.213 (178.236.0.213) 126.301 ms 16 * * 178.236.1.189 (178.236.1.189) 131.358 ms traceroute sueddeutsche.de
      traceroute to sueddeutsche.de (46.189.56.88), 30 hops max, 60 byte packets 2 173.44.32.253.static.quadranet.com (173.44.32.253) 0.204 ms 0.196 ms 0.223 ms 3 xe-3-1-5-51-grtmiana2.net.telefonicaglobalsolutions.com (5.53.1.32) 1.767 ms 1.793 ms 1.786 ms 4 xe2-1-3-0-grtmiabr4.red.telefonica-wholesale.net (213.140.36.90) 13.630 ms te0-5-0-6-grtmiabr6.net.telefonicaglobalsolutions.com (94.142.122.254) 2.205 ms te0-0-0-9-grtmiabr5.red.telefonica-wholesale.net (94.142.121.146) 4.627 ms 5 xe10-0-0-0-grtrpaopx2.net.telefonicaglobalsolutions.com (84.16.13.65) 68.400 ms 67.987 ms xe0-0-0-0-grtpaopx2.net.telefonicaglobalsolutions.com (176.52.254.253) 64.439 ms 6 213.140.55.70 (213.140.55.70) 90.781 ms 86.340 ms 86.331 ms 7 217.239.42.186 (217.239.42.186) 168.826 ms 213.140.53.174 (213.140.53.174) 105.583 ms 217.239.42.186 (217.239.42.186) 172.519 ms 8 213.140.55.70 (213.140.55.70) 105.565 ms 217.239.42.202 (217.239.42.202) 188.288 ms 213.140.53.174 (213.140.53.174) 107.452 ms 9 10g-9-4.esn001isp005.versatel.de (62.214.110.234) 165.907 ms 170.032 ms 10g-9-4.esn001isp006.versatel.de (62.214.110.238) 168.310 ms 10 ge-05-01-803.dor002isp005.versatel.de (62.214.111.26) 163.609 ms 62.214.105.126 (62.214.105.126) 168.818 ms 87.128.232.54 (87.128.232.54) 179.409 ms 11 62.214.106.34 (62.214.106.34) 351.274 ms dor2is2.versatel.de (62.214.104.170) 351.012 ms 351.252 ms 12 62.214.106.38 (62.214.106.38) 165.606 ms 10g-9-4.hhb002isp005.versatel.de (62.214.110.110) 166.429 ms 166.004 ms 13 62.214.35.138 (62.214.35.138) 173.626 ms 173.356 ms 173.457 ms 14 212.93.14.114 (212.93.14.114) 175.773 ms 174.723 ms 175.221 ms 15 62.214.147.122 (62.214.147.122) 171.947 ms 172.509 ms 290.386 ms traceroute washingtonpost.com
      traceroute to washingtonpost.com (192.33.31.56), 30 hops max, 60 byte packets 2 173.44.32.253.static.quadranet.com (173.44.32.253) 0.194 ms 0.177 ms 0.182 ms 3 ae3-98.mia10.ip4.gtt.net (77.67.71.145) 0.279 ms 0.287 ms 0.233 ms 4 xe-0-2-1.mia12.ip4.gtt.net (141.136.109.130) 0.301 ms xe-4-2-6.mia12.ip4.gtt.net (89.149.131.174) 0.383 ms xe-4-2-4.mia12.ip4.gtt.net (89.149.131.202) 0.334 ms 5 instart-logic-gw.ip4.gtt.net (216.221.156.90) 0.393 ms 0.423 ms 0.412 ms 6 a-vip07.insnw.net (192.33.31.56) 0.263 ms 0.301 ms 0.272 ms What services are running?
      Postfix Nginx Php MongoDB VPN Support:
      No tickets needed.

      Overall experience:
      CPU is sometimes slow, I/O ok and a good network connection.
      Did not have to send a single ticket.
      Update status:

      19 hours 18 minutes of network downtime since the first four months.
      The node did have some rough times during the first month, network itself is solid. 
      Uptime of the vps itself is 26 days.
      CPU and I/O are ok.
      Network is great.
      wget cachefly.cachefly.net/100mb.test -O /dev/null converted 'http://cachefly.cachefly.net/100mb.test' (ANSI_X3.4-1968) -> 'http://cachefly.cachefly.net/100mb.test' (UTF-8) --2016-01-05 00:21:34-- 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' /dev/null 100%[================================================>] 100.00M 73.9MB/s in 1.4s 2016-01-05 00:21:35 (73.9 MB/s) - '/dev/null' saved [104857600/104857600] I will refresh the uptime report every two months.
    • By sammasri85
      Hi ,this is my review on hudsonvalleyhost.com  , two months ago i got a managed VPS from them and here is my results :    - first ,there entire IP range is blacklisted on Spamhaus SBL , not for sending SPAM but for sending ALL kinds of viruses and malware ,as Spamhaus said  here :  https://www.spamhaus.org/sbl/query/SBL228367    means that ,ALL emails coming from there ip's will be marked as SPAM (even if they are not ) and even ALL domains hosted on there ip's will be blacklisted too . the funny thing is that you cannot do anything about it ,because hudsonvalleyhost have to contact spamhaus directly ,and you have nothing to do with that .   - second , there sales team said that they allow email marketing activities on the server ,but , after i paid for it ,the support team said NO they do not allow email marketing on there servers ,and guess what ,they don't offer a refund too .   so ,basically i paid for the VPS ,spend more than 300 $ to setup my mailer and finally i got a blacklisted ip's with a very bad customer support and no refund .   this hosting provider is a wast of time and money ,so ,buyers BE AWARE !!!  
    • By wlanboy
      Provider: NanoVZ
      Plan: OpenVZ 256 MB VPS
      Price: € 3 per year
      Location: Falkenstein, Germany
      Purchased: 01/2015

      Hardware information:
       
      cat /proc/cpuinfo (1x)
      processor : 0 vendor_id : Genu cpu family : 6 model : 58 model name : Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz stepping : 9 microcode : 23 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 6800.62 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: cat /proc/meminfo
      MemTotal: 262144 kB MemFree: 236652 kB Cached: 19944 kB Buffers: 0 kB Active: 10828 kB Inactive: 11328 kB Active(anon): 3980 kB Inactive(anon): 836 kB Active(file): 6848 kB Inactive(file): 10492 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 262144 kB SwapFree: 259280 kB Dirty: 4 kB Writeback: 0 kB AnonPages: 4816 kB Shmem: 2604 kB Slab: 3324 kB SReclaimable: 1368 kB SUnreclaim: 1956 kB dd
      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, 1.80004 s, 74.6 MB/s wget
      wget cachefly.cachefly.net/100mb.test -O /dev/null --2015-03-22 06:39:43-- 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 53.1M/s in 1.9s 2015-03-22 06:39:45 (53.1 MB/s) - `/dev/null' saved [104857600/104857600] Network:
      20 NAT IPv4 Ports /80 IPv6 Subnet 500 GB Transfer traceroute dvhn.nl
      2 hos-tr4-juniper4.rz16.hetzner.de (213.239.233.97) 0.240 ms hos-tr6-juniper4.rz16.hetzner.de (213.239.247.97) 0.211 ms hos-tr3-juniper4.rz16.hetzner.de (213.239.233.65) 0.202 ms 3 core21.hetzner.de (213.239.245.105) 0.217 ms 0.244 ms core22.hetzner.de (213.239.245.145) 0.232 ms 4 core1.hetzner.de (213.239.245.218) 4.823 ms core1.hetzner.de (213.239.245.177) 4.824 ms core1.hetzner.de (213.239.245.218) 4.823 ms 5 juniper1.ams.hetzner.de (213.239.203.158) 10.579 ms 10.578 ms 10.554 ms 6 amsix-501.xe-0-0-0.jun1.bit-1.network.bit.nl (80.249.208.200) 12.275 ms 12.499 ms 12.430 ms traceroute theguardian.co.uk
      2 hos-tr1-juniper3.rz16.hetzner.de (213.239.230.1) 0.208 ms 0.231 ms hos-tr4-juniper4.rz16.hetzner.de (213.239.233.97) 17.155 ms 3 core21.hetzner.de (213.239.245.105) 0.249 ms 0.255 ms core22.hetzner.de (213.239.245.145) 0.740 ms 4 core12.hetzner.de (213.239.245.214) 2.784 ms core12.hetzner.de (213.239.245.29) 2.795 ms core12.hetzner.de (213.239.245.214) 2.794 ms 5 juniper4.rz2.hetzner.de (213.239.245.26) 2.883 ms juniper4.rz2.hetzner.de (213.239.203.138) 2.851 ms 2.808 ms 6 ae51.bar2.Munich1.Level3.net (62.140.25.101) 5.599 ms 17.905 ms ae55.edge7.Frankfurt1.Level3.net (195.16.162.253) 7.347 ms 7 ae-11-51.car1.London1.Level3.net (4.69.139.66) 100.511 ms 100.513 ms 100.737 ms 8 ae-11-51.car1.London1.Level3.net (4.69.139.66) 100.782 ms 100.807 ms 115.422 ms 9 GUARDIAN-UN.car1.London1.Level3.net (212.113.8.30) 17.101 ms 19.110 ms 19.147 ms traceroute sueddeutsche.de
      2 hos-tr1-juniper3.rz16.hetzner.de (213.239.230.1) 0.179 ms hos-tr3-juniper4.rz16.hetzner.de (213.239.233.65) 0.215 ms 0.180 ms 3 core21.hetzner.de (213.239.245.105) 0.465 ms core22.hetzner.de (213.239.245.145) 0.225 ms 0.253 ms 4 core4.hetzner.de (213.239.245.14) 4.894 ms core1.hetzner.de (213.239.245.177) 4.848 ms 4.928 ms 5 juniper1.ffm.hetzner.de (213.239.245.5) 6.329 ms 4.858 ms juniper4.ffm.hetzner.de (213.239.245.1) 4.985 ms 6 ec-r7604-hro-01.ediscom.de (80.81.193.73) 115.008 ms 164.183 ms 164.199 ms 7 212.204.40.54 (212.204.40.54) 22.298 ms 22.144 ms 22.361 ms 8 94.55.204.212-static.ediscom.de (212.204.55.94) 29.183 ms 29.315 ms 29.482 ms traceroute washingtonpost.com
      2 hos-tr1-juniper3.rz16.hetzner.de (213.239.230.1) 0.137 ms hos-tr3-juniper4.rz16.hetzner.de (213.239.233.65) 0.191 ms hos-tr1-juniper3.rz16.hetzner.de (213.239.230.1) 0.159 ms 3 core22.hetzner.de (213.239.245.145) 0.226 ms 0.208 ms 0.245 ms 4 core12.hetzner.de (213.239.245.214) 2.780 ms core12.hetzner.de (213.239.245.29) 2.777 ms core12.hetzner.de (213.239.245.214) 2.790 ms 5 juniper4.rz2.hetzner.de (213.239.245.26) 2.822 ms 2.833 ms juniper4.rz2.hetzner.de (213.239.203.138) 2.886 ms 6 r1nue2.core.init7.net (82.197.163.29) 3.046 ms r1nue1.core.init7.net (77.109.135.101) 2.914 ms r1nue2.core.init7.net (82.197.163.29) 3.059 ms 7 r1lon1.core.init7.net (77.109.140.253) 17.194 ms r1ams2.core.init7.net (77.109.140.157) 53.511 ms r1ams1.core.init7.net (77.109.140.25) 25.195 ms 8 ae-15.r02.amstnl02.nl.bb.gin.ntt.net (80.249.208.36) 19.875 ms r1muc1.core.init7.net (77.109.128.231) 7.392 ms ae-15.r02.amstnl02.nl.bb.gin.ntt.net (80.249.208.36) 20.065 ms 9 ae-15.r02.amstnl02.nl.bb.gin.ntt.net (80.249.208.36) 15.684 ms ae-2.r22.amstnl02.nl.bb.gin.ntt.net (129.250.2.112) 18.386 ms ae-2.r03.londen01.uk.bb.gin.ntt.net (129.250.3.8) 26.441 ms 10 ae-1.r02.londen01.uk.bb.gin.ntt.net (129.250.3.36) 27.145 ms ae-15.r02.amstnl02.nl.bb.gin.ntt.net (80.249.208.36) 14.428 ms ae-5.r23.londen03.uk.bb.gin.ntt.net (129.250.5.197) 32.894 ms 11 62.73.179.186 (62.73.179.186) 25.374 ms ae-5.r23.londen03.uk.bb.gin.ntt.net (129.250.5.197) 18.976 ms 62.73.179.186 (62.73.179.186) 17.573 ms 12 ae-2.r02.londen01.uk.bb.gin.ntt.net (129.250.3.1) 25.938 ms * 24.876 ms 13 * * * 14 * * * What services are running?
      OpenVPN Nginx (both behind CloudFlares IPv4 Proxy) Ruby workers Support:
      No tickets needed.

      Overall experience:
      CPU ok, I/O could be better and a good network connection.
      Did not have to send a single ticket.

      Update status:

      0 minutes of network downtime since the first month.
      The node did have some rough times during the first weeks, I/O itself does have some spikes but is quite solid. 
      Uptime of the vps itself is 56 days.
      CPU is ok and I/O could be better.
      Network is good within the EU.
      wget cachefly.cachefly.net/100mb.test -O /dev/null --2015-03-22 06:39:43-- 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 53.1M/s in 1.9s 2015-03-22 06:39:45 (53.1 MB/s) - `/dev/null' saved [104857600/104857600] I will refresh the uptime report every two months.
    • By GIANT_CRAB
      Hey all, 
       
      So it has almost been a year since I have been with Cloudshards. So here's my experience with them: 
       
      I've heard a lot of good things about Cloudshards and the prices are really amazing so I decided to spin up a 2GB OpenVZ with them on 27/03/2014. As of now, I have 2 VPS with Cloudshards and they are working really great. Although the company name has the word 'cloud' in it, Cloudshards doesn't provide Cloud Hosting services yet. 
       
      Uptime: 10/10
       
      So far, no downtime in terms of both network and hardware. They have some downtime once every few months due to scheduled network maintenance or upgrade but they gave a good window of 3 to 5 days before carrying it out so that all the customers will be well prepared for the scheduled downtime. 
       
      Network: 10/10
       
      Their network connectivity worldwide has very low latency and is really superb! Connectivity to Asia was especially great and I've gotten only 160ms from Singapore. :) 
       
      Here's a ping to my Los Angeles Cloudshards VPS

       
      Support: 9/10
       
      Their support team replied within 4 hours and they read through my issues carefully. I've once experienced unreliable network connectivity and opened a support ticket with them. Within a few hours, they replied to me and told me it was because there was a DDoS on the node and offered to transfer me to another node. I accepted the transfer and it was done within minutes! :)
       
      Prices: 10/10
       
      I spun up a few VPS with lots of RAM and they only cost $7 for 2GB. For the price and service offered, it is a really great deal! They also offer KVM storage with lots of space and it is very affordable too. I've also asked for a customized upgrade from 2GB to 4GB and they did so without much hesitation. 
       
      Overall, their VPS offer very smooth performance with great network speeds and latency at really affordable price. 
       
      Thank you Cloudshards for giving me such a memorable experience! :)
    • By wlanboy
      Provider: NanoVZ
      Plan: OpenVZ 128 MB VPS
      Price: € 3 per year
      Location: Roubaix, France
      Purchased: 01/2015

      Hardware information:

      cat /proc/cpuinfo (1x)
      processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU W3530 @ 2.80GHz stepping : 5cpu MHz : 2800.140 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpidbogomips : 5600.28 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: cat /proc/meminfo
      MemTotal: 131072 kB MemFree: 100784 kB Cached: 18156 kB Buffers: 0 kB Active: 17320 kB Inactive: 8908 kB Active(anon): 5152 kB Inactive(anon): 2920 kB Active(file): 12168 kB Inactive(file): 5988 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 131072 kB SwapFree: 125448 kB Dirty: 4 kB Writeback: 0 kB AnonPages: 8072 kB Shmem: 2604 kB Slab: 4048 kB SReclaimable: 1124 kB SUnreclaim: 2924 kB dd
      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.47973 s, 54.1 MB/s wget
      wget cachefly.cachefly.net/100mb.test -O /dev/null --2015-02-25 00:21:23-- http://cachefly.cachefly.net/100mb.testResolving 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 OKLength: 104857600 (100M) [application/octet-stream] Saving to: `/dev/null' 100%[========================================================>] 104,857,600 31.8M/s in 4.0s2015-02-25 00:21:27 (25.0 MB/s) - `/dev/null' saved [104857600/104857600] Network:
      20 NAT IPv4 Ports /80 IPv6 Subnet 100 GB Transfer
      traceroute dvhn.nl
      2 rbx-g1-a9.fr.eu (213.186.32.253) 0.874 ms 1.045 ms 1.026 ms 3 ams-1-6k.nl.eu (94.23.122.186) 5.531 ms * * 4 amsix-501.xe-0-0-0.jun1.bit-2a.network.bit.nl (80.249.208.35) 7.341 ms 6.905 ms 7.282 ms traceroute theguardian.co.uk
      2 rbx-g1-a9.fr.eu (213.186.32.253) 0.837 ms 1.042 ms 1.071 ms 3 th2-g1-a9.fr.eu (91.121.215.132) 4.607 ms th2-g1-a9.fr.eu (91.121.131.210) 4.227 ms 4.600 ms 4 * * gsw-1-6k.fr.eu (91.121.215.135) 13.906 ms 5 * * * 6 ae-15-51.car5.London1.Level3.net (4.69.139.70) 7.661 ms 8.227 ms 7.977 ms 7 ae-15-51.car5.London1.Level3.net (4.69.139.70) 8.100 ms 8.618 ms 8.390 ms 8 GUARDIAN-UN.car5.London1.Level3.net (217.163.45.90) 7.910 ms 7.982 ms 7.925 ms traceroute sueddeutsche.de
      2 rbx-g1-a9.fr.eu (213.186.32.253) 0.874 ms 1.038 ms 1.038 ms 3 ams-1-6k.nl.eu (94.23.122.114) 5.646 ms * * 4 AMDGW1.arcor-ip.net (80.249.209.123) 6.443 ms 6.381 ms 10.108 ms 5 bln-145-254-5-158.arcor-ip.net (145.254.5.158) 19.876 ms 19.829 ms 19.747 ms 6 82.82.24.142 (82.82.24.142) 19.131 ms 19.200 ms 19.218 ms 7 212.204.41.194 (212.204.41.194) 26.180 ms 26.155 ms 26.101 ms traceroute washingtonpost.com
      2 rbx-g1-a9.fr.eu (213.186.32.253) 0.850 ms 0.996 ms 1.050 ms 3 th2-g1-a9.fr.eu (91.121.131.210) 4.471 ms th2-g1-a9.fr.eu (91.121.215.132) 4.488 ms th2-g1-a9.fr.eu (91.121.131.210) 4.374 ms 4 * * * 5 * * * 6 NEUSTAR-INC.edge3.Paris1.Level3.net (212.73.242.130) 4.416 ms 4.375 ms 4.316 ms What services are running?
      Postfix Nginx (both behind CloudFlares IPv4 Proxy) Php Redis Support:
      No tickets needed.

      Overall experience:
      CPU ok, I/O ok and a good network connection.
      Did not have to send a single ticket.

      Update status:

      3 hours 29 minutes 35 seconds of network downtime since the first month.
      The node did have some rough times during the first weeks, network itself does have some spikes but is quite solid. Hoping for some calm weeks.
      Uptime of the vps itself is 30 days.
      CPU and I/O are ok.
      Network is good within the EU.

      I will refresh the uptime report every two months.