amuck-landowner

[Miami KVM VPS @ Virtovo] 2GB KVM only $7/mo

Virtovo

Virtovo

New Member
Verified Provider
Virtovo was formed in December 2013.  Virtovo is a registered business in England and Wales. Virtovo is a very young company and doesn't have a long story to tell. We are committed to writing a successful story going forward through good quality hardware and a commitment to customer service.

We currently only offer services out of Coresite, Miami. IPv6 is available in this location but IPv6 is not currently offered with these plans. We are investigating the best way to allocate /64s to customers instead of fragmented addresses which SolusVM allocates by default. We hope to have a solution to this before the end of February.

We use Blesta for our billing/support and SolusVM for our VPS control.  We've made modifications to our client area to enable near full control of your VPS from within the client area (including mounting ISOs, change boot priority, VNC console access, enabling PAE etc)

35b87ix.png

Node specifications

* Dual E5-2620v2 (2.1Ghz)

* 128GB RAM

* Minimum 8 Disk LSI Raid 10 Array

* Redundant 1Gbps uplinks at the node level

Please find the below benchmark shared by of our clients:  



CPU model :  QEMU Virtual CPU version (cpu64-rhel6)
Number of cores : 6
CPU frequency :  2099.998 MHz
Total amount of ram : 2016 MB
Total amount of swap : 0 MB
System uptime :   1 min,
Download speed from CacheFly: 45.5MB/s
Download speed from Coloat, Atlanta GA: 13.0MB/s
Download speed from Softlayer, Dallas, TX: 38.0MB/s
Download speed from Linode, Tokyo, JP: 9.45MB/s
Download speed from i3d.net, Rotterdam, NL: 8.32MB/s
Download speed from Leaseweb, Haarlem, NL: 10.5MB/s
Download speed from Softlayer, Singapore: 6.39MB/s
Download speed from Softlayer, Seattle, WA: 20.6MB/s
Download speed from Softlayer, San Jose, CA: 18.5MB/s
Download speed from Softlayer, Washington, DC: 51.2MB/sI/O speed :  782 MB/s

Important info

Terms of service

Acceptable use policy

Privacy policy

Public Status

List of operating systems

Test IP/Files

mia.virtovo.com

http://mia.virtovo.com/100MB.zip

http://mia.virtovo.com/1GB.zip

We're offering a very special recurring discount offer on our 2GB and 4GB KVM plan. Use code: 2GBfor7USD at checkout for the discounted pricing. This is an extremely limited offer and is only good while stock lasts.

KVMH3

2048MB RAM

6 Cores

100GB HDD

4TB Transfer

1 IPv4 Address

SolusVM

$7/mo | Order Remember, click 'Have a coupon' on the right of the order form and enter 2GBfor7USD

KVMH3

4096MB RAM

8 Cores

200GB HDD

8TB Transfer

1 IPv4 Address

SolusVM

$14/mo | Order Remember, click 'Have a coupon' on the right of the order form and enter 2GBfor7USD

We have a number of other plans at our website: http://www.virtovo.com. You may use discount code: LAUNCH40OFF on any other plan for a 40% recurring discount. Plans start from $3/mo (discounted).
 
Last edited by a moderator:
T

TheLinuxBug

New Member
Ok, so I broke down and got one to test out (the 512Mb actually not the 2GB).  Servers nice and fast, it seems like pure cogent in US and some nlayer to international destinations. However, the most confusing part is trying to access he.net to setup an ipv6 tunnel is hilarious:



root@mia:~# traceroute 209.51.161.58
traceroute to 209.51.161.58 (209.51.161.58), 30 hops max, 60 byte packets
1 126.44.188.64.static.ipv4.dnsptr.net (64.188.44.126) 0.159 ms 0.149 ms 0.118 ms
2 1.32.188.64.static.ipv4.dnsptr.net (64.188.32.1) 0.198 ms 0.130 ms 0.191 ms
3 gi3-4.ccr01.mia05.atlas.cogentco.com (38.122.220.41) 1.082 ms 1.098 ms 1.125 ms
4 te2-8.ccr01.mia08.atlas.cogentco.com (154.54.83.149) 0.977 ms 0.967 ms 1.049 ms
5 te0-2-0-5.ccr21.mia01.atlas.cogentco.com (154.54.83.21) 1.042 ms 1.081 ms 1.119 ms
6 be2069.ccr21.iah01.atlas.cogentco.com (66.28.4.237) 28.308 ms be2070.mpd21.iah01.atlas.cogentco.com (154.54.0.142) 28.245 ms 28.544 ms
7 be2065.ccr21.lax01.atlas.cogentco.com (154.54.5.66) 64.876 ms 64.563 ms be2067.mpd21.lax01.atlas.cogentco.com (154.54.7.162) 64.501 ms
8 be2181.ccr23.lax05.atlas.cogentco.com (154.54.41.114) 64.890 ms be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58) 64.088 ms 64.402 ms
9 telia.lax05.atlas.cogentco.com (154.54.12.218) 63.870 ms telia.lax05.atlas.cogentco.com (154.54.10.10) 64.448 ms 64.351 ms
10 dls-bb1-link.telia.net (213.155.136.40) 68.577 ms dls-bb1-link.telia.net (80.91.254.168) 68.499 ms 68.435 ms
11 atl-bb1-link.telia.net (80.91.254.164) 82.637 ms atl-bb1-link.telia.net (213.155.137.74) 83.915 ms atl-bb1-link.telia.net (213.155.133.127) 80.765 ms
12 hurricane-ic-129712-atl-bb1.c.telia.net (213.248.79.70) 78.296 ms hurricane-ic-138358-atl-bb1.c.telia.net (213.248.71.66) 71.905 ms hurricane-ic-129712-atl-bb1.c.telia.net (213.248.79.70) 78.303 ms
13 10ge4-1.core1.mia1.he.net (72.52.92.54) 72.977 ms 72.882 ms 78.994 ms



So, Miami -> TX -> LAX -> ATL -> MIAMI ??!?

 

Whats also strange is the closest location at 61ms is in fact he.net's LAX tunnel server, all of the East Coast servers including New York come in at over 70ms.  Is this normal? Do you have some strange tuning in place that prefers west coast routing or is this some goof from Cogent?

 

Shortest route to he.net tunnel server (LAX):


Code: 
traceroute to 66.220.18.42 (66.220.18.42), 30 hops max, 60 byte packets
 1  126.44.188.64.static.ipv4.dnsptr.net (64.188.44.126)  0.238 ms  0.725 ms  0.654 ms
 2  1.32.188.64.static.ipv4.dnsptr.net (64.188.32.1)  0.500 ms  0.446 ms  0.347 ms
 3  gi3-4.ccr01.mia05.atlas.cogentco.com (38.122.220.41)  0.710 ms  1.612 ms  1.515 ms
 4  te2-7.ccr01.mia08.atlas.cogentco.com (154.54.83.145)  3.121 ms  3.016 ms  2.964 ms
 5  te0-1-1-1.ccr21.mia01.atlas.cogentco.com (154.54.83.17)  1.193 ms  1.145 ms  0.976 ms
 6  be2069.ccr21.iah01.atlas.cogentco.com (66.28.4.237)  28.148 ms  28.272 ms  28.685 ms
 7  be2065.ccr21.lax01.atlas.cogentco.com (154.54.5.66)  64.480 ms be2067.mpd21.lax01.atlas.cogentco.com (154.54.7.162)  63.995 ms  64.212 ms
 8  be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  64.755 ms  65.238 ms be2181.ccr23.lax05.atlas.cogentco.com (154.54.41.114)  64.119 ms
 9  telia.lax05.atlas.cogentco.com (154.54.10.10)  63.707 ms telia.lax05.atlas.cogentco.com (154.54.12.218)  63.642 ms  63.722 ms
10  hurricane-ic-138362-las-bb1.c.telia.net (213.248.67.142)  62.112 ms  62.111 ms  62.582 ms
11  tserv1.lax1.he.net (66.220.18.42)  61.854 ms  62.374 ms  61.895 ms

I was going to open a ticket but was more so curious if this is normal or just part of some routing growing pains?

P.S.  The pure Cogent isn't what is bothering me, just the crazy routes all across the USA to reach destinations that should be about 10-20ms away.  

Cheers!
 
Last edited by a moderator:
Virtovo

Virtovo

New Member
Verified Provider
TheLinuxBug said:
Ok, so I broke down and got one to test out (the 512Mb actually not the 2GB).  Servers nice and fast, it seems like pure cogent in US and some nlayer to international destinations. However, the most confusing part is trying to access he.net to setup an ipv6 tunnel is hilarious:



root@mia:~# traceroute 209.51.161.58
traceroute to 209.51.161.58 (209.51.161.58), 30 hops max, 60 byte packets
1 126.44.188.64.static.ipv4.dnsptr.net (64.188.44.126) 0.159 ms 0.149 ms 0.118 ms
2 1.32.188.64.static.ipv4.dnsptr.net (64.188.32.1) 0.198 ms 0.130 ms 0.191 ms
3 gi3-4.ccr01.mia05.atlas.cogentco.com (38.122.220.41) 1.082 ms 1.098 ms 1.125 ms
4 te2-8.ccr01.mia08.atlas.cogentco.com (154.54.83.149) 0.977 ms 0.967 ms 1.049 ms
5 te0-2-0-5.ccr21.mia01.atlas.cogentco.com (154.54.83.21) 1.042 ms 1.081 ms 1.119 ms
6 be2069.ccr21.iah01.atlas.cogentco.com (66.28.4.237) 28.308 ms be2070.mpd21.iah01.atlas.cogentco.com (154.54.0.142) 28.245 ms 28.544 ms
7 be2065.ccr21.lax01.atlas.cogentco.com (154.54.5.66) 64.876 ms 64.563 ms be2067.mpd21.lax01.atlas.cogentco.com (154.54.7.162) 64.501 ms
8 be2181.ccr23.lax05.atlas.cogentco.com (154.54.41.114) 64.890 ms be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58) 64.088 ms 64.402 ms
9 telia.lax05.atlas.cogentco.com (154.54.12.218) 63.870 ms telia.lax05.atlas.cogentco.com (154.54.10.10) 64.448 ms 64.351 ms
10 dls-bb1-link.telia.net (213.155.136.40) 68.577 ms dls-bb1-link.telia.net (80.91.254.168) 68.499 ms 68.435 ms
11 atl-bb1-link.telia.net (80.91.254.164) 82.637 ms atl-bb1-link.telia.net (213.155.137.74) 83.915 ms atl-bb1-link.telia.net (213.155.133.127) 80.765 ms
12 hurricane-ic-129712-atl-bb1.c.telia.net (213.248.79.70) 78.296 ms hurricane-ic-138358-atl-bb1.c.telia.net (213.248.71.66) 71.905 ms hurricane-ic-129712-atl-bb1.c.telia.net (213.248.79.70) 78.303 ms
13 10ge4-1.core1.mia1.he.net (72.52.92.54) 72.977 ms 72.882 ms 78.994 ms



So, Miami -> TX -> LAX -> ATL -> MIAMI ??!?

 

Whats also strange is the closest location at 61ms is in fact he.net's LAX tunnel server, all of the East Coast servers including New York come in at over 70ms.  Is this normal? Do you have some strange tuning in place that prefers west coast routing or is this some goof from Cogent?

 

Shortest route to he.net tunnel server (LAX):


Code: 
traceroute to 66.220.18.42 (66.220.18.42), 30 hops max, 60 byte packets
 1  126.44.188.64.static.ipv4.dnsptr.net (64.188.44.126)  0.238 ms  0.725 ms  0.654 ms
 2  1.32.188.64.static.ipv4.dnsptr.net (64.188.32.1)  0.500 ms  0.446 ms  0.347 ms
 3  gi3-4.ccr01.mia05.atlas.cogentco.com (38.122.220.41)  0.710 ms  1.612 ms  1.515 ms
 4  te2-7.ccr01.mia08.atlas.cogentco.com (154.54.83.145)  3.121 ms  3.016 ms  2.964 ms
 5  te0-1-1-1.ccr21.mia01.atlas.cogentco.com (154.54.83.17)  1.193 ms  1.145 ms  0.976 ms
 6  be2069.ccr21.iah01.atlas.cogentco.com (66.28.4.237)  28.148 ms  28.272 ms  28.685 ms
 7  be2065.ccr21.lax01.atlas.cogentco.com (154.54.5.66)  64.480 ms be2067.mpd21.lax01.atlas.cogentco.com (154.54.7.162)  63.995 ms  64.212 ms
 8  be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  64.755 ms  65.238 ms be2181.ccr23.lax05.atlas.cogentco.com (154.54.41.114)  64.119 ms
 9  telia.lax05.atlas.cogentco.com (154.54.10.10)  63.707 ms telia.lax05.atlas.cogentco.com (154.54.12.218)  63.642 ms  63.722 ms
10  hurricane-ic-138362-las-bb1.c.telia.net (213.248.67.142)  62.112 ms  62.111 ms  62.582 ms
11  tserv1.lax1.he.net (66.220.18.42)  61.854 ms  62.374 ms  61.895 ms

I was going to open a ticket but was more so curious if this is normal or just part of some routing growing pains?

P.S.  The pure Cogent isn't what is bothering me, just the crazy routes all across the USA to reach destinations that should be about 10-20ms away.  

Cheers!
Click to expand...
That shouldn't be right.  If you can open a ticket or drop a PM with your name so I can open a ticket on your behalf we can chase this up and provide a response to you. 
 
T

TheLinuxBug

New Member
FYI it is looking better now, Much much better.

traceroute to 209.51.161.58 (209.51.161.58), 30 hops max, 60 byte packets

 1  126.44.188.64.static.ipv4.dnsptr.net (64.188.44.126)  0.221 ms  0.129 ms  0.173 ms

 2  1.32.188.64.static.ipv4.dnsptr.net (64.188.32.1)  0.255 ms  0.220 ms  0.214 ms

 3  ae5-1912.cr1.mia1.us.nlayer.net (63.141.207.129)  35.797 ms  0.477 ms  35.588 ms

 4  nota.he.net (198.32.124.176)  0.556 ms  0.961 ms  0.881 ms

 

it looks to be routing over nlayer and taking closest hop now.  I will update you again if I see further route weirdness.  For now it is looking much better though.  Thanks for your quick attention to this.

 

Cheers!
 
You must log in or register to reply here.
Top
amuck-landowner