OneAsiaHost: 512MB OVZ in Singapore – Review

 

Traceroutes:

 

To BuyVM (SJC, CA, US):

[code]

2  edge-2.v71.com3.sg.gs (203.175.175.130) [AS24482]  2.132 ms  2.247 ms  2.574 ms
3  202.176.211.33 (202.176.211.33) [AS9911]  2.835 ms  3.115 ms  3.108 ms
4  203.208.145.237 (203.208.145.237) [AS7473]  3.490 ms  3.498 ms  3.493 ms
5  ge-0-1-2-0.sngc3-dr1.ix.singtel.com (203.208.172.117) [AS7473]  3.390 ms ge-0-1-0-0.sngc3-dr1.ix.singtel.com (203.208.172.113) [AS7473]  3.414 ms ge-1-1-1-0.sngc3-dr1.ix.singtel.com (203.208.172.121) [AS7473]  3.376 ms
6  203.208.153.241 (203.208.153.241) [AS7473]  3.413 ms ge-0-1-8-0.sngtp-dr2.ix.singtel.com (203.208.151.193) [AS7473]  47.624 ms 203.208.166.201 (203.208.166.201) [AS7473]  2.379 ms
7  203.208.153.122 (203.208.153.122) [AS7473]  173.212 ms so-2-0-3-0.laxow-cr1.ix.singtel.com (203.208.149.238) [AS7473]  181.612 ms  181.613 ms
8  ge-1-1-2-0.sngtp-dr1.ix.singtel.com (203.208.149.214) [AS7473]  186.475 ms ge-2-1-0-0.sngc3-ar4.ix.singtel.com (203.208.152.106) [AS7473]  184.186 ms 203.208.153.142 (203.208.153.142) [AS7473]  186.205 ms
9  203.208.186.82 (203.208.186.82) [AS7473]  197.068 ms  195.513 ms  199.668 ms
10  ae1-50g.cr1.lax1.us.nlayer.net (69.31.127.129) [AS26627]  184.353 ms  176.993 ms  177.111 ms
11  xe-4-2-0.cr1.sjc1.us.nlayer.net (69.22.142.9) [AS4436]  195.358 ms xe-2-0-0.cr1.sjc1.us.nlayer.net (69.22.142.125) [AS4436]  180.295 ms  181.052 ms
12  ae1-40g.ar2.sjc1.us.nlayer.net (69.22.143.118) [AS4436]  187.664 ms  177.358 ms  186.595 ms
13  as18779.xe-4-0-4.ar2.sjc1.us.nlayer.net (69.22.153.94) [AS4436]  199.696 ms  199.448 ms  199.810 ms
14  173.245.86.18 (173.245.86.18) [AS18779]  181.055 ms  183.317 ms  195.003 ms

[/code]

 

Same Host, but via IPV6:

[code]

1  2405:4200:202::241 (2405:4200:202::241) [AS24482]  0.017 ms  0.006 ms  0.004 ms
2  edge-1.v75.ntp.sg.gs (2405:4200:0:ff05::11) [AS24482]  1592.279 ms * *
3  * * hurricaneelectric1-RGE.hkix.net (2001:7fa:0:1::ca28:a19e) [*]  48.424 ms
4  gige-g3-7.core1.lax1.he.net (2001:470:0:16b::1) [AS6939]  206.909 ms  206.787 ms  206.782 ms
5  10gigabitethernet1-3.core1.pao1.he.net (2001:470:0:34::1) [AS6939]  204.754 ms  209.094 ms  209.089 ms
6  * * *
7  * * *
8  2607:f358:1a:4::2 (2607:f358:1a:4::2) [AS18779]  206.374 ms  206.370 ms  206.669 ms
9  2607:f358:1:fed5:20::3 (2607:f358:1:fed5:20::3) [AS18779]  248.786 ms  248.759 ms  214.122 ms

[/code]

The v6 route is quite a bit slower due to going over HKIX, from the looks of it.

To OCN (Tokyo, Japan):

v4:

[code]

2  ge-3-2-0-110.a00.sngpsi02.sg.ra.gin.ntt.net (116.51.17.237) [AS2914]  0.869 ms  0.955 ms  1.029 ms
3  ae-1.r02.sngpsi02.sg.bb.gin.ntt.net (116.51.16.245) [AS2914]  0.656 ms  0.707 ms  0.696 ms
4  as-1.r23.tokyjp01.jp.bb.gin.ntt.net (129.250.6.120) [AS2914]  68.931 ms  68.932 ms as-1.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.5.20) [AS2914]  103.602 ms
5  ae-4.r25.tokyjp01.jp.bb.gin.ntt.net (129.250.3.165) [AS2914]  69.099 ms  69.100 ms ae-3.r25.tokyjp01.jp.bb.gin.ntt.net (129.250.3.157) [AS2914]  69.216 ms
6  ae-9.r20.tokyjp01.jp.bb.gin.ntt.net (129.250.2.92) [AS2914]  68.838 ms  69.907 ms  69.897 ms
7  ae-2.ocn.tokyjp01.jp.bb.gin.ntt.net (129.250.12.198) [AS2914]  69.148 ms ae-1.ocn.tokyjp01.jp.bb.gin.ntt.net (129.250.11.114) [AS2914]  70.245 ms  70.246 ms
8  60.37.27.147 (60.37.27.147) [AS4713]  84.908 ms 118.23.168.18 (118.23.168.18) [AS4713]  85.922 ms  84.784 ms
9  118.23.176.130 (118.23.176.130) [AS4713]  70.841 ms  69.913 ms  69.701 ms
10  * * *
11  118.23.176.158 (118.23.176.158) [AS4713]  69.565 ms  70.838 ms  69.623 ms
12  61.126.89.222 (61.126.89.222) [AS4713]  74.412 ms  73.477 ms  75.244 ms

[/code]

v6:

[code]

2  edge-1.v75.ntp.sg.gs (2405:4200:0:ff05::11) [AS24482]  1.508 ms * *
3  * * ntt2-RGE.hkix.net (2001:7fa:0:1::ca28:a1db) [*]  51.200 ms
4  po-1.r00.newthk01.hk.bb.gin.ntt.net (2001:218:6000:2000::2) [AS2914]  90.569 ms  90.564 ms  90.730 ms
5  xe-0-3-0.r20.newthk02.hk.bb.gin.ntt.net (2001:218:0:2000::6) [AS2914]  51.371 ms  51.126 ms  51.325 ms
6  as-2.r21.newthk02.hk.bb.gin.ntt.net (2001:218:0:2000::11e) [AS2914]  35.466 ms  36.236 ms  36.508 ms
7  as-1.r25.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::13d) [AS2914]  80.645 ms  79.832 ms  79.213 ms
8  ae-9.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::1c5) [AS2914]  79.593 ms  79.080 ms  79.571 ms
9  ae-1.ocn.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:5000::e) [AS2914]  79.438 ms  79.434 ms  79.987 ms
10  2001:380:8130:12::16 (2001:380:8130:12::16) [AS4713]  79.759 ms 2001:380:8150:f::16 (2001:380:8150:f::16) [AS4713]  80.260 ms 2001:380:8130:12::16 (2001:380:8130:12::16) [AS4713]  79.716 ms
11  2001:380:8290:7::2 (2001:380:8290:7::2) [AS4713]  79.701 ms  80.076 ms  80.042 ms
12  2001:380:0:2529::2 (2001:380:0:2529::2) [AS4713]  84.017 ms  84.002 ms  84.078 m

[/code]

They have a NTT pipe which they seem to use, which is nice (awesome more like :P), but the same issue as the one we encountered in the BuyVM test for IPV6 exists. Going over HKIX slows things down by around 9ms or so, from the above trace.

 

SCNET (Tokyo, Japan):

v4:

[code]

2  ge-3-2-0-110.a00.sngpsi02.sg.ra.gin.ntt.net (116.51.17.237) [AS2914]  0.840 ms  0.917 ms  0.979 ms
3  ae-1.r02.sngpsi02.sg.bb.gin.ntt.net (116.51.16.245) [AS2914]  0.663 ms  0.716 ms ae-1.r20.sngpsi02.sg.bb.gin.ntt.net (116.51.16.249) [AS2914]  0.712 ms
4  as-1.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.5.20) [AS2914]  70.385 ms  69.258 ms  69.254 ms
5  ae-4.r24.tokyjp01.jp.bb.gin.ntt.net (129.250.3.159) [AS2914]  86.954 ms  71.538 ms  71.539 ms
6  ae-4.r20.tokyjp03.jp.bb.gin.ntt.net (129.250.4.126) [AS2914]  69.770 ms  69.758 ms  70.278 ms
7  ge-0-1-9.r20.tokyjp03.jp.ce.gin.ntt.net (203.105.73.98) [AS2914]  71.659 ms  71.909 ms g3-43.ar1.tko1.servercentral.net (203.105.73.94) [AS2914]  86.394 ms
8  as32780.ge3-42.ar1.tko1.jp.scnet.net (75.102.60.22) [AS23352]  71.850 ms  87.559 ms  71.998 ms
9  cloud1.japan.so.cm (50.31.254.105) [AS32780]  71.440 ms  71.893 ms  72.138 ms

[/code]

We can see the NTT pipe in use this time too, which is good. This trace goes to Equinix TY2, I’ve got some stuff there 🙂

 

Chinaunicom (CN):

v4:

[code]

2  edge-1.v71.com3.sg.gs (203.175.175.129) [AS24482]  3.302 ms  3.306 ms  3.295 ms
3  edge-1.v73.ntp.sg.gs (203.175.175.148) [AS24482]  24.193 ms  24.593 ms  24.296 ms
4  63.216.152.185 (63.216.152.185) [AS3491]  5.075 ms  5.162 ms  5.268 ms
5  cnc.pos2-1.br01.hkg05.pccwbtn.net (63.218.145.146) [AS3491/AS24077]  92.306 ms  92.320 ms  92.261 ms
6  219.158.96.213 (219.158.96.213) [AS4837]  91.783 ms  90.655 ms  90.652 ms
7  219.158.11.73 (219.158.11.73) [AS4134/AS4837]  91.844 ms  91.881 ms  91.878 ms
8  219.158.15.13 (219.158.15.13) [AS4134/AS4837]  358.853 ms  358.921 ms  358.895 ms
9  123.126.0.10 (123.126.0.10) [AS4134]  374.268 ms  359.892 ms *
10  61.148.153.50 (61.148.153.50) [AS4808/AS4814]  102.930 ms  103.007 ms  103.004 ms
11  61.148.158.10 (61.148.158.10) [AS4808/AS4814]  104.007 ms  104.009 ms  103.795 ms
12  61.148.158.102 (61.148.158.102) [AS4808/AS4814]  361.515 ms  361.516 ms  358.596 ms
13  61.135.113.2 (61.135.113.2) [AS4808]  106.461 ms  104.136 ms  105.254 ms

[/code]

Sure is ICMP deprioritization in CNC routers, welp. But as you can see, it manages okay routes to China as well.

 

Internode (Sydeny, AU):

v4:

[code]

2  edge-1.v71.com3.sg.gs (203.175.175.129) [AS24482]  2.814 ms  2.941 ms  3.606 ms
3  edge-1.v73.ntp.sg.gs (203.175.175.148) [AS24482]  4.764 ms  4.732 ms  4.730 ms
4  internode-RGE.hkix.net (202.40.161.74) [AS2687/AS4862/AS9498/AS10026/AS1221]  42.803 ms  42.975 ms  42.499 ms
5  * * *
6  * * *
7  * * *
8  te7-2.cor1.adl6.internode.on.net (150.101.225.230) [AS4739]  152.534 ms  152.736 ms  152.794 ms
[/code]

Going over HKIX this time too, but 150ms to AU is okay enough.

 

IInet and Exetel (AU):

v4:

[code]

traceroute to www.exetel.com.au (220.233.0.9), 30 hops max, 60 byte packets
1  116.251.210.241 (116.251.210.241) [AS24482]  0.021 ms  0.006 ms  0.006 ms
2  edge-1.v71.com3.sg.gs (203.175.175.129) [AS24482]  3.405 ms  3.391 ms  3.439 ms
3  202.176.211.34 (202.176.211.34) [AS9911]  3.158 ms  3.332 ms  3.333 ms
4  203.208.255.197 (203.208.255.197) [AS9911]  3.383 ms  3.406 ms  3.388 ms
5  203.208.145.245 (203.208.145.245) [AS7473]  3.381 ms  3.371 ms  3.367 ms
6  ge-1-0-0-0.sngc3-ar2.ix.singtel.com (203.208.172.158) [AS7473]  3.354 ms  2.773 ms  2.952 ms
7  ge-1-0-0-0.sngtp-dr1.ix.singtel.com (203.208.173.133) [AS7473]  3.220 ms  2.592 ms  2.588 ms
8  GigabitEthernet2-1-1.sngtp-ar4.ix.singtel.com (203.208.183.122) [AS7473]  2.788 ms  2.788 ms GigabitEthernet1-1-1.sngtp-ar4.ix.singtel.com (203.208.183.114) [AS7473]  2.779 ms
9  so3-1-3.phbr2.global-gateway.net.nz (202.50.234.177) [*]  51.205 ms so2-1-2.phbr2.global-gateway.net.nz (202.50.238.249) [*]  50.830 ms  50.800 ms
10  so1-2-3.sebr1.global-gateway.net.nz (203.96.120.121) [AS9901]  96.825 ms  96.579 ms  96.985 ms
11  xe7-1-0-10.sebr1.global-gateway.net.nz (203.96.120.202) [AS9901]  171.838 ms ae1-10.sebr2.global-gateway.net.nz (202.50.232.242) [*]  101.675 ms  111.423 ms
12  ae1-10.sebr2.global-gateway.net.nz (202.50.232.242) [*]  111.421 ms aapt-int.sebr2.global-gateway.net.nz (202.50.238.214) [*]  250.592 ms ae1-10.sebr2.global-gateway.net.nz (202.50.232.242) [*]  106.483 ms
13  aapt-int.sebr2.global-gateway.net.nz (202.50.238.214) [*]  106.708 ms  106.574 ms  106.691 ms
14  te2-4.sglebdist01.aapt.net.au (202.10.14.6) [AS2764]  111.928 ms te2-1-110.sglebdist02.aapt.net.au (202.10.12.131) [AS2764/AS1221]  103.146 ms  103.262 ms
15  te0-3-1-0.sclarcore01.aapt.net.au (202.10.12.9) [AS2764/AS1221]  103.382 ms te2-1-110.sglebdist02.aapt.net.au (202.10.12.131) [AS2764/AS1221]  111.852 ms te0-3-1-0.sclarcore01.aapt.net.au (202.10.12.9) [AS2764/AS1221]  103.230 ms
16  te0-3-1-0.sclarcore01.aapt.net.au (202.10.12.9) [AS2764/AS1221]  111.839 ms te2-2.sclardist01.aapt.net.au (202.10.12.2) [AS2764/AS1221]  99.047 ms te0-3-1-0.sclarcore01.aapt.net.au (202.10.12.9) [AS2764/AS1221]  111.806 ms
17  1-1-1.sclarinte01.aapt.net.au (203.131.60.31) [*]  98.514 ms te2-2.sclardist01.aapt.net.au (202.10.12.2) [AS2764/AS1221]  102.232 ms 1-1-1.sclarinte01.aapt.net.au (203.131.60.31) [*]  98.669 ms
18  ipll-5017319-154.gw.aapt.com.au (203.174.185.154) [*]  99.007 ms  98.908 ms  98.989 ms
19  ipll-5017319-154.gw.aapt.com.au (203.174.185.154) [*]  102.834 ms  102.808 ms 139.6.96.58.static.exetel.com.au (58.96.6.139) [AS10143]  98.950 ms
20  candlenut-web.exetel.com.au (220.233.0.9) [AS10143/AS4826]  102.186 ms  102.285 ms  102.388 ms

[email protected]:~# t -A www.iinet.net.au
traceroute to www.iinet.net.au (203.173.50.132), 30 hops max, 60 byte packets
1  116.251.210.241 (116.251.210.241) [AS24482]  0.021 ms  0.007 ms  0.005 ms
2  edge-1.v71.com3.sg.gs (203.175.175.129) [AS24482]  2.730 ms  2.741 ms  3.089 ms
3  edge-1.v73.ntp.sg.gs (203.175.175.148) [AS24482]  4.109 ms  4.106 ms  4.163 ms
4  internode-RGE.hkix.net (202.40.161.74) [AS2687/AS4862/AS9498/AS10026/AS1221]  44.420 ms  44.417 ms  43.895 ms
5  * * *
6  po0-1-1.cor1.per1.internode.on.net (203.16.211.230) [AS9942]  121.930 ms  120.086 ms  120.083 ms
7  gi2-24.per-qv1-bdr1.iinet.net.au (203.16.212.202) [AS4739/AS14172/AS1221]  120.071 ms  120.069 ms  120.067 ms
8  * * *
[/code]

IINET and Internode are technically the same network now, but leaving that aside, the vps is fine for AU users too.

 

PCCW (HK):

v4:

[code]

2  edge-2.v71.com3.sg.gs (203.175.175.130) [AS24482]  1.661 ms  1.890 ms  1.947 ms
3  edge-1.v73.ntp.sg.gs (203.175.175.148) [AS24482]  3.460 ms  3.461 ms  3.450 ms
4  ims2-RGE.hkix.net (202.40.161.17) [AS2687/AS4862/AS9498/AS10026/AS1221]  41.057 ms  41.062 ms  41.044 ms
5  202.153.96.114 (202.153.96.114) [AS24207]  42.138 ms  41.510 ms  42.120 ms

[/code]

Most HKG connections will be handled by the HKIX, which almost all larger backbones in HK connect to. You can expect sub 40ms to anywhee HK, I guess. Which is really nice, imo.

 

KDDI (DHK, BD):

v4:

[code]

2  edge-2.v71.com3.sg.gs (203.175.175.130) [AS24482]  2.501 ms  2.495 ms  2.508 ms
3  202.176.211.33 (202.176.211.33) [AS9911]  2.614 ms  2.605 ms  2.600 ms
4  203.208.145.237 (203.208.145.237) [AS7473]  2.622 ms  2.744 ms  2.746 ms
5  ge-0-1-0-0.sngc3-dr1.ix.singtel.com (203.208.172.113) [AS7473]  2.559 ms ge-0-1-2-0.sngc3-dr1.ix.singtel.com (203.208.172.117) [AS7473]  2.547 ms ge-1-1-4-0.sngc3-dr1.ix.singtel.com (203.208.172.169) [AS7473]  2.545 ms
6  203.208.171.214 (203.208.171.214) [AS7473]  2.505 ms ge-1-0-0-0.sngtp-dr1.ix.singtel.com (203.208.173.133) [AS7473]  2.214 ms  2.301 ms
7  203.208.152.53 (203.208.152.53) [AS7473]  2.419 ms 203.208.152.161 (203.208.152.161) [AS7473]  2.441 ms 203.208.152.53 (203.208.152.53) [AS7473]  2.618 ms
8  203.208.174.26 (203.208.174.26) [AS7473]  220.140 ms  220.258 ms  220.255 ms
9  gi8-5.agg01-core01.agg01.mango.com.bd (114.130.1.26) [AS17806]  222.472 ms  222.311 ms  222.532 ms
10  206.dhk-peer.mango.com.bd (114.130.3.206) [AS17806]  61.215 ms  61.410 ms  61.523 ms
11  uttara-aggr-rt01-GEv0v1.bracnet.com.bd (202.168.254.110) [AS24342/AS9237]  63.014 ms  63.015 ms  65.611 ms
12  * [AS24342]  65.787 ms  67.230 ms  65.735 ms

[/code]

This is an unconventional KDDI location I’ve got a box in, latency is fine enough.

 

Somebody else has already done the same for US/EU locations, so I won’t bother. You can read about his findings here

 

Conclusion:

Asian routing wise, the OAH (GS) network provides optimal performance to almost all prominent Asian countries. This obviously isn’t true for all US/EU locations, but if you want a node in Asia to serve Asian visitors, there aren’t really any better locations than SG to do it off. OAH seems ot offer a premium product at affordable prices out of SG, so feel free to give it a try.

 

** Trace requests to hosts in countries not included here are welcome, please leave a comment.

 

3 Replies to “OneAsiaHost: 512MB OVZ in Singapore – Review”

  1. Just replying to some of the points brought up. Thanks for the extensive tests, much appreciated.

    (1) Lack of 64bit templates
    The host node is 32bit to keep memory usage down, thus we only added in 32bit templates. If there’s demand for 64bit VPSes we may consider running 64bit nodes in the future.

    (2) 4 Cores on OVZ-512
    This was an oversight, the initial plan was to only have 2 cores for this plan. The plan on SolusVM has been updated for new VPSes and we’ll send a notice out sometime soon before we update the VPSes.

    (3) CacheFly
    Singapore’s nearest CacheFly nodes are in HK or JP. Since we’re connected to HKIX, connected through there would be ideal.

    (4) Google
    We’re peering with Google in Singapore at Singapore Open Exchange, so this is the shortest path possible. I would expect them to be using their Singapore node for this as well, but it is what it is. Most of the bandwidth we do with Google is video traffic, which goes via US anyway so direct path without transit provider inbetween was what we wanted to achieve.

    (5) BuyVM IPv6
    Traceroute via NTT was only slightly better, not by much so left it as it is. Below is the result of traceroute from a NTT link directly.

    traceroute6 to 2607:f358:1:fed5:20::3 (2607:f358:1:fed5:20::3) from 2001:218:4000:5000::66, 64 hops max, 12 byte packets
    1 ge-3-2-0-112.a00.sngpsi02.sg.ra.gin.ntt.net 0.820 ms 0.762 ms 0.738 ms
    2 ae-1.r20.sngpsi02.sg.bb.gin.ntt.net 0.722 ms 0.726 ms 0.698 ms
    3 as-3.r20.snjsca04.us.bb.gin.ntt.net 261.383 ms 187.545 ms 171.662 ms
    4 ae-0.r21.snjsca04.us.bb.gin.ntt.net 188.986 ms 171.817 ms 181.718 ms
    5 10gigabitethernet2-3.core1.sjc2.he.net 202.018 ms 196.566 ms 201.301 ms
    6 10gigabitethernet1-4.core1.sjc1.he.net 202.846 ms 194.584 ms 202.543 ms
    7 energy-group-networks-llc.10gigabitethernet1-1.core1.sjc1.he.net 176.282 ms 173.678 ms 191.960 ms
    8 2607:f358:1a:4::2 196.371 ms 182.997 ms 180.603 ms
    9 2607:f358:1:fed5:20::3 199.946 ms 192.069 ms 207.869 ms

    (6) OCN IPv6
    Has been fixed, no longer using HKIX routes so ping times are now about 74ms or so.

    (7) Internode
    This is one of the few HKIX peers that I actually left the route as it is, even though it’s going from SG > HK > AU which is extended distance. Reason being, NTT goes to US Level 3 and back to AU (300ms), SingTel goes to JP JPIX and back to AU (300ms), PCCW direct 5 hop but latency is still around 150ms.

  2. Thanks about One Asia Host Review, but the review is about 2 years ago, when they just start. How about right now? when they already have many customer? is their service decreased, or any improvement?
    How with their competitor? Like Digital Ocean, DO already open singapore VPS service

Leave a Reply

Your email address will not be published. Required fields are marked *