Singapore Based OpenVZ VPS Testing - OneAsiaHost
New on LowEndTalk? Please read our 'Community Rules' by clicking on it in the right menu!

Singapore Based OpenVZ VPS Testing - OneAsiaHost

KenshinKenshin Member
edited May 2012 in General

Our new servers have been setup, tested and run-in, but lack active VPS testing/feedback. We would like to offer our OVZ-512 plan for a 1 month test to the first 10 active members (at least 5 posts in the past 3 months) who reply in this thread, as a little thank you to the guys and girls who make LET the vibrant community it is today. Please only reply if you plan on actual use or active testing, not just running bench.sh and posting the results then letting the VPS sit idle.

Plan Details
Spec: 512MB RAM, 30GB HDD, 60GB Bandwidth, $15/month ^
Location: Global Switch Datacentre, Singapore
Network: Transit - SingTel, SingNet, NTT, PCCW, Peering - SGIX, SOX, HKIX
Unacceptable Use: IRC, Public Proxy, TOR, Adult Content

Test IP: 116.251.210.1 - 2405:4200:202::1
Work In-progress Website: http://www.oneasiahost.com

^ I am aware the price exceeds LET's requirement, but purely for testing purposes I would like to provide the OVZ-512 instead since we do not offer burstable RAM or vswap. Our OVZ-256 plan will be US$7/month, which will fit the criteria once we go live.

All I'm requesting from the testers is as much feedback as possible during or at the end of the 1 month test, even if there's nothing wrong with the VPS & you're happy, and I'll extend the VPS for another 1 month for full use (non-trial). You can choose to downgrade to OVZ-256 when the extended free period ends or simply terminate.

Feel free to contact me privately about issues with the VPS, or publicly if you feel that you would like to share it with everyone and possible work up a discussion. I believe I'm one of the few providers based in Singapore and would definitely like feedback/discussion on how our product fares, especially the network connectivity as I have a "thing" for route optimization.

Singapore time is GMT +0800, so do forgive me for slow responses (possible 12-24hrs later) as it's 6AM here right now while I'm typing this. I'm currently still working alone on this project for the time being but will get my entire team involved when we go live.

Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
«13

Comments

  • TaylorTaylor Member

    Thanks, I will grab one please.

    I know, I'm Dale Maily.

  • I'll try it out. LMK what kind of testing you're most interested in; IIRC I ran a couple of traceroutes to your test IPs, one of which was acting very weird...

  • ElliotJElliotJ Administrator
    edited May 2012

    Just thought I'd mention Kenshin's old thread asking for traceroutes for his network.
    I personally got pretty awesome results considering it's SEA, something like 8ish hops from London to Singapore, with 230~ish pings.

    Good luck with the launch :)

    Need to reach me quickly? Ping me on Discord

  • RophRoph Member

    Singapore needs some fatter pipes laid, that bandwidth is pitiful :[

  • KenshinKenshin Member
    edited May 2012

    Taylor, kbar check PM.

    @quirkyquark said: I'll try it out. LMK what kind of testing you're most interested in; IIRC I ran a couple of traceroutes to your test IPs, one of which was acting very weird...

    General usability of the VPS, network reachability/latency, I'm more of a RHEL based user, so if there's any odd issue with the other templates I probably won't ever realise. The odd traceroute was intended on SingTel's end unfortunately, some paths are shorter so the entire traceroute looks odd, but SingTel has probably the best overall network connectivity out of Singapore, especially to less connected countries such as Vietnam.

    @Roph said: Singapore needs some fatter pipes laid, that bandwidth is pitiful :[

    You should read my earlier discussion thread, the costs of internet bandwidth in this region is insane not to mention local loops. Realistically, 100mbps+ residential broadband is only good for piracy, not for viewing hosted content.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • @Kenshin said: I'm more of a RHEL based user

    Fantastic, I very much prefer Debian/derivatives, so that'll be good.

  • KenshinKenshin Member

    @quirkyquark said: Fantastic, I very much prefer Debian/derivatives, so that'll be good.

    I've edited the templates from the original OpenVZ template to point sources to our local debian mirror so do test if there's any oddity. Thanks.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • @Kenshin said: I've edited the templates from the original OpenVZ template

    Please do the same for Ubuntu. I generally do this myself at the start, but given how precious bandwidth in SG... :-)

  • KenshinKenshin Member
    edited May 2012

    @quirkyquark said: Please do the same for Ubuntu. I generally do this myself at the start, but given how precious bandwidth in SG... :-)

    This will take a while... Ubuntu was never on my mirroring list, heh. Will update when done.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • TheHackBoxTheHackBox Member
    edited May 2012

    I must say connectivity to your host from OVH sucks as it goes from France to the US to Singapore.

    This signature is brought to you by the NSA. Spying on the entire world since 1952!

  • KenshinKenshin Member

    @TheHackBox said: I must say connectivity to your host from OVH sucks as it goes from France to the US to Singapore.

    Sadly, I've tested all 4 of my transit providers and all of them go through US to reach FR. I can understand the reasoning behind this, because there's more bandwidth capacity in the submarine cables from SG <=> US <=> FR, than the reverse direction across Europe/Asia, which is mainly land.

    I did manage to find a SG router that routes via Asia/Europe directly, ping times are about 200ms. From my end about 300ms.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • gbshousegbshouse Member, Provider
  • seikanseikan Member

    @Kenshin Is the test slot still avaialble? I'm interested.

    Hobby Projects: DNMin | PingBear

  • I'm interested if this is still available.

  • edited May 2012

    @Kenshin: Mind letting me know the amount of IP space, bandwidth capacity and space you're getting from Global Switch currently? And at what price? Thanks!

  • SpencerSpencer Member

    Is it a 1mbit port or larger? Because I have a malasyia VPS for web hosting over there and it is only on a 1mbit port.

  • KenshinKenshin Member

    6 slots given out: Taylor, kbar, quirkyquark, gbshouse, seikan, Bernardoo. Please check PM for the details.

    @Boltersdriveer said: @Kenshin: Mind letting me know the amount of IP space, bandwidth capacity and space you're getting from Global Switch currently? And at what price? Thanks!

    OneAsiaHost is a spinoff from HostSG who has APNIC membership with 2x /20 ranges, combined bandwidth of about 300mbps transit and multiple peering arrangements, so it'll be difficult for me to provide you with any figures since I'm tapping onto this already built network.

    @PytoHost said: Is it a 1mbit port or larger? Because I have a malasyia VPS for web hosting over there and it is only on a 1mbit port.

    100mbps port, but realistically if the bandwidth is out of Singapore it'll be about 10mbps or so per connection.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • Since I'm based in SEA, I'm interested too. Could I get one? :)

    -- BOFH

  • KenshinKenshin Member

    @Wintereise said: Since I'm based in SEA, I'm interested too. Could I get one? :)

    You got PM.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • Thanks :)

    -- BOFH

  • gbshousegbshouse Member, Provider

    OK, time for first impressions:

    Disk performance

    [email protected]:~# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync

    16384+0 records in
    16384+0 records out
    1073741824 bytes (1.1 GB) copied, 2.63098 s, 408 MB/s

    Pings :
    us1 - Chicago, US

    PING us1.rage4.com (149.154.158.203) 56(84) bytes of data.

    64 bytes from 149.154.158.203: icmp_req=1 ttl=42 time=244 ms
    64 bytes from 149.154.158.203: icmp_req=2 ttl=44 time=232 ms
    64 bytes from 149.154.158.203: icmp_req=3 ttl=42 time=233 ms
    64 bytes from 149.154.158.203: icmp_req=4 ttl=44 time=242 ms

    PING us1.rage4.com(2a02:748:a800:149:154:158:203:1) 56 data bytes

    64 bytes from 2a02:748:a800:149:154:158:203:1: icmp_seq=1 ttl=55 time=223 ms
    64 bytes from 2a02:748:a800:149:154:158:203:1: icmp_seq=2 ttl=55 time=225 ms
    64 bytes from 2a02:748:a800:149:154:158:203:1: icmp_seq=3 ttl=55 time=255 ms
    64 bytes from 2a02:748:a800:149:154:158:203:1: icmp_seq=4 ttl=55 time=234 ms

    us2 - Los Angeles, US

    PING us2.rage4.com (69.85.92.169) 56(84) bytes of data.

    64 bytes from 69.85.92.169: icmp_req=1 ttl=45 time=184 ms
    64 bytes from 69.85.92.169: icmp_req=2 ttl=47 time=186 ms
    64 bytes from 69.85.92.169: icmp_req=3 ttl=45 time=185 ms
    64 bytes from 69.85.92.169: icmp_req=4 ttl=47 time=198 ms

    PING us2.rage4.com(2606:df00:3::d5c4:c403) 56 data bytes

    64 bytes from 2606:df00:3::d5c4:c403: icmp_seq=1 ttl=55 time=197 ms
    64 bytes from 2606:df00:3::d5c4:c403: icmp_seq=2 ttl=55 time=195 ms
    64 bytes from 2606:df00:3::d5c4:c403: icmp_seq=3 ttl=54 time=196 ms
    64 bytes from 2606:df00:3::d5c4:c403: icmp_seq=4 ttl=55 time=196 ms

    at1 - Graz, Austria

    PING at1.rage4.com (158.255.212.26) 56(84) bytes of data.

    64 bytes from at1.rage4.com (158.255.212.26): icmp_req=1 ttl=45 time=216 ms
    64 bytes from at1.rage4.com (158.255.212.26): icmp_req=2 ttl=45 time=216 ms
    64 bytes from at1.rage4.com (158.255.212.26): icmp_req=3 ttl=45 time=217 ms
    64 bytes from at1.rage4.com (158.255.212.26): icmp_req=4 ttl=45 time=216 ms

    PING at1.rage4.com(2a03:f80:ed15:158:255:212:26:1) 56 data bytes

    64 bytes from 2a03:f80:ed15:158:255:212:26:1: icmp_seq=1 ttl=49 time=379 ms
    64 bytes from 2a03:f80:ed15:158:255:212:26:1: icmp_seq=2 ttl=49 time=373 ms
    64 bytes from 2a03:f80:ed15:158:255:212:26:1: icmp_seq=3 ttl=49 time=374 ms
    64 bytes from 2a03:f80:ed15:158:255:212:26:1: icmp_seq=4 ttl=49 time=374 ms

    uk1 - London, UK

    PING uk1.rage4.com (46.17.63.136) 56(84) bytes of data.

    64 bytes from uk1.rage4.com (46.17.63.136): icmp_req=1 ttl=47 time=192 ms
    64 bytes from uk1.rage4.com (46.17.63.136): icmp_req=2 ttl=47 time=198 ms
    64 bytes from uk1.rage4.com (46.17.63.136): icmp_req=3 ttl=47 time=192 ms
    64 bytes from uk1.rage4.com (46.17.63.136): icmp_req=4 ttl=47 time=192 ms

    PING uk1.rage4.com(2a01:348:70:46:17:63:136:1) 56 data bytes

    64 bytes from 2a01:348:70:46:17:63:136:1: icmp_seq=1 ttl=54 time=329 ms
    64 bytes from 2a01:348:70:46:17:63:136:1: icmp_seq=2 ttl=54 time=341 ms
    64 bytes from 2a01:348:70:46:17:63:136:1: icmp_seq=3 ttl=54 time=350 ms
    64 bytes from 2a01:348:70:46:17:63:136:1: icmp_seq=4 ttl=54 time=343 ms

    se1 - Stockholm, Sweden

    PING se1.rage4.com (178.73.210.161) 56(84) bytes of data.

    64 bytes from se1.rage4.com (178.73.210.161): icmp_req=1 ttl=39 time=359 ms
    64 bytes from se1.rage4.com (178.73.210.161): icmp_req=2 ttl=37 time=363 ms
    64 bytes from se1.rage4.com (178.73.210.161): icmp_req=3 ttl=37 time=356 ms
    64 bytes from se1.rage4.com (178.73.210.161): icmp_req=4 ttl=39 time=363 ms

    PING se1.rage4.com(2a00:1a28:1251:178:73:210:161:1) 56 data bytes

    64 bytes from 2a00:1a28:1251:178:73:210:161:1: icmp_seq=1 ttl=57 time=207 ms
    64 bytes from 2a00:1a28:1251:178:73:210:161:1: icmp_seq=2 ttl=57 time=205 ms
    64 bytes from 2a00:1a28:1251:178:73:210:161:1: icmp_seq=3 ttl=57 time=206 ms
    64 bytes from 2a00:1a28:1251:178:73:210:161:1: icmp_seq=4 ttl=57 time=205 ms

  • gbshousegbshouse Member, Provider

    Traceroutes (IPv4) 1/2:

    traceroute to us1.rage4.com (149.154.158.203), 30 hops max, 60 byte packets

    1 116.251.210.241 (116.251.210.241) 0.015 ms 0.006 ms 0.005 ms
    2 edge-1.v71.com3.sg.gs (203.175.175.129) 1.805 ms 1.918 ms 1.982 ms
    3 202.176.211.33 (202.176.211.33) 2.109 ms 2.127 ms 2.136 ms
    4 203.208.145.237 (203.208.145.237) 2.952 ms 2.941 ms 2.930 ms
    5 ge-4-0-0-0.sngc3-cr1.ix.singtel.com (203.208.172.153) 2.856 ms ge-0-1-0-0.sngc3-dr1.ix.singtel.com (203.208.172.113) 2.888 ms ge-0-1-2-0.sngc3-dr1.ix.singtel.com (203.208.172.117) 2.849 ms
    6 ge-1-1-3-0.sngtp-dr2.ix.singtel.com (203.208.152.21) 2.824 ms ge-0-1-8-0.sngtp-dr2.ix.singtel.com (203.208.151.193) 2.468 ms 203.208.153.245 (203.208.153.245) 2.463 ms
    7 so-3-0-2-0.laxow-cr1.ix.singtel.com (203.208.151.230) 175.345 ms so-2-0-2-0.laxow-cr1.ix.singtel.com (203.208.151.118) 183.722 ms so-3-0-0-0.laxow-cr1.ix.singtel.com (203.208.149.226) 183.158 ms
    8 ge-7-0-0-0.laxow-dr2.ix.singtel.com (203.208.183.158) 183.777 ms 203.208.153.142 (203.208.153.142) 183.084 ms 181.913 ms
    9 203.208.186.82 (203.208.186.82) 194.874 ms 189.492 ms 198.884 ms
    10 ae1-50g.cr1.lax1.us.nlayer.net (69.31.127.129) 186.833 ms 184.952 ms 185.034 ms
    11 xe-2-2-1.cr2.ord1.us.nlayer.net (69.22.142.255) 222.932 ms 226.113 ms 216.367 ms
    12 ae3-40g.cr1.ord1.us.nlayer.net (69.31.111.153) 216.496 ms 226.593 ms 225.421 ms
    13 69.31.105.38 (69.31.105.38) 236.658 ms 233.192 ms 232.889 ms

    traceroute to us2.rage4.com (69.85.92.169), 30 hops max, 60 byte packets

    1 116.251.210.241 (116.251.210.241) 0.018 ms 0.007 ms 0.005 ms
    2 edge-2.v71.com3.sg.gs (203.175.175.130) 1.725 ms 1.849 ms 1.959 ms
    3 202.176.211.34 (202.176.211.34) 1.892 ms 1.904 ms 1.994 ms
    4 203.208.255.197 (203.208.255.197) 2.132 ms 2.203 ms 2.220 ms
    5 203.208.145.245 (203.208.145.245) 2.313 ms 2.319 ms 2.445 ms
    6 203.208.171.169 (203.208.171.169) 2.406 ms ge-1-0-0-0.sngc3-ar2.ix.singtel.com (203.208.172.158) 2.294 ms 2.273 ms
    7 203.208.152.221 (203.208.152.221) 2.238 ms 203.208.153.245 (203.208.153.245) 4.120 ms 4.116 ms
    8 203.208.171.86 (203.208.171.86) 182.852 ms ge-2-1-0-0.laxow-dr1.ix.singtel.com (203.208.171.10) 188.824 ms 188.816 ms
    9 ge-4-0-0-0.sngtp-cr1.ix.singtel.com (203.208.149.46) 186.338 ms ge-1-1-2-0.sngtp-dr1.ix.singtel.com (203.208.149.214) 176.688 ms ge-2-1-0-0.sngc3-ar4.ix.singtel.com (203.208.152.106) 186.441 ms
    10 203.208.186.82 (203.208.186.82) 178.071 ms 188.069 ms 187.951 ms
    11 as29761.xe-1-0-2.ar1.lax2.us.nlayer.net (69.31.121.254) 181.932 ms 181.891 ms 176.790 ms
    12 po6.core01.po1.lax13 (67.215.251.230) 176.211 ms 176.213 ms 181.465 ms
    13 quadra-hostg-gw.hostigation.com (72.11.150.106) 186.501 ms 186.501 ms 186.491 ms

    traceroute to at1.rage4.com (158.255.212.26), 30 hops max, 60 byte packets

    1 116.251.210.241 (116.251.210.241) 0.021 ms 0.006 ms 0.006 ms
    2 edge-1.v71.com3.sg.gs (203.175.175.129) 2.074 ms 2.268 ms 2.269 ms
    3 202.176.211.34 (202.176.211.34) 2.184 ms 2.204 ms 2.244 ms
    4 203.208.255.197 (203.208.255.197) 2.220 ms 2.317 ms 2.317 ms
    5 203.208.145.245 (203.208.145.245) 2.321 ms 2.439 ms 2.326 ms
    6 ge-1-0-0-0.sngc3-ar2.ix.singtel.com (203.208.172.158) 2.294 ms 2.325 ms 203.208.171.169 (203.208.171.169) 2.339 ms
    7 ge-1-1-3-0.sngtp-dr2.ix.singtel.com (203.208.152.21) 2.301 ms 2.385 ms 3.131 ms
    8 so-3-2-0-0.sngtp-ar6.ix.singtel.com (203.208.151.145) 185.020 ms 203.208.166.173 (203.208.166.173) 3.110 ms so-3-2-0-0.sngtp-ar6.ix.singtel.com (203.208.151.145) 185.008 ms
    9 203.208.153.81 (203.208.153.81) 185.304 ms 203.208.166.45 (203.208.166.45) 189.268 ms 194.489 ms
    10 203.208.171.181 (203.208.171.181) 192.562 ms 193.263 ms uk-lon01a-rd2-ge-2-2.aorta.net (195.66.236.89) 188.497 ms
    11 203.208.153.81 (203.208.153.81) 189.209 ms 189.199 ms 189.202 ms
    12 uk-lon01a-rd2-ge-2-2.aorta.net (195.66.236.89) 193.522 ms 193.523 ms 193.490 ms
    13 84.116.132.241 (84.116.132.241) 220.447 ms at-vie01a-rd1-xe-3-2-0.aorta.net (84.116.134.234) 221.543 ms 84.116.132.237 (84.116.132.237) 216.957 ms
    14 at-grz-lazg-pe02-vl-2032.upc.at (84.116.228.86) 216.554 ms uk-lon01b-rd1-xe-0-0-1.aorta.net (84.116.132.5) 217.665 ms 217.912 ms
    15 at-grz-mk43-pe01-vl-2084.upc.at (84.116.229.74) 214.026 ms at-vie01a-rd1-xe-1-1-0.aorta.net (84.116.134.230) 217.317 ms 84.116.132.34 (84.116.132.34) 220.013 ms
    16 GBE.MDF.GRAZ.EDIS.AT (83.65.45.2) 213.998 ms 214.006 ms at-grz-lazg-pe02-vl-2032.upc.at (84.116.228.86) 219.988 ms
    17 * at-grz-mk43-pe01-vl-2084.upc.at (84.116.229.74) 217.247 ms 216.940 ms
    18 * GBE.MDF.GRAZ.EDIS.AT (83.65.45.2) 226.106 ms *

  • gbshousegbshouse Member, Provider

    Traceroutes (IPv4) 2/2

    traceroute to uk1.rage4.com (46.17.63.136), 30 hops max, 60 byte packets

    1 116.251.210.241 (116.251.210.241) 0.019 ms 0.006 ms 0.006 ms
    2 edge-1.v71.com3.sg.gs (203.175.175.129) 2.097 ms 2.527 ms 2.259 ms
    3 202.176.211.34 (202.176.211.34) 2.227 ms 2.260 ms 2.273 ms
    4 203.208.255.197 (203.208.255.197) 3.304 ms 3.223 ms 3.200 ms
    5 203.208.145.245 (203.208.145.245) 3.842 ms 3.907 ms 3.963 ms
    6 203.208.171.169 (203.208.171.169) 38.900 ms 37.165 ms ge-1-0-0-0.sngc3-ar2.ix.singtel.com (203.208.172.158) 2.822 ms
    7 203.208.153.245 (203.208.153.245) 2.818 ms 2.030 ms 4.533 ms
    8 so-3-0-3-0.loncl-cr1.ix.singtel.com (203.208.151.238) 195.850 ms 195.851 ms 203.208.166.173 (203.208.166.173) 4.568 ms
    9 203.208.153.81 (203.208.153.81) 195.996 ms 196.002 ms 196.134 ms
    10 203.208.152.249 (203.208.152.249) 203.390 ms 203.395 ms 203.377 ms
    11 203.208.153.81 (203.208.153.81) 190.109 ms ge-1-2-2.rt0.the.uk.goscomb.net (46.17.60.157) 205.288 ms 203.208.153.81 (203.208.153.81) 190.309 ms
    12 xe-0-1-1.cs0.the.uk.goscomb.net (93.89.94.133) 199.794 ms xe-0-0-0.rt0.thn.uk.goscomb.net (195.66.224.226) 220.067 ms 220.044 ms
    13 ge-1-2-2.rt0.the.uk.goscomb.net (46.17.60.157) 193.436 ms xe-0-1-0.cs0.gs2.uk.goscomb.net (93.89.90.130) 197.916 ms ge-1-2-2.rt0.the.uk.goscomb.net (46.17.60.157) 192.401 ms
    14 xe-0-1-1.cs0.the.uk.goscomb.net (93.89.94.133) 193.049 ms 193.759 ms *
    15 xe-0-1-0.cs0.gs2.uk.goscomb.net (93.89.90.130) 192.649 ms * 192.808 ms

    traceroute to se1.rage4.com (178.73.210.161), 30 hops max, 60 byte packets

    1 116.251.210.241 (116.251.210.241) 0.017 ms 0.006 ms 0.006 ms
    2 edge-2.v71.com3.sg.gs (203.175.175.130) 2.792 ms 2.797 ms 2.820 ms
    3 202.176.211.34 (202.176.211.34) 2.771 ms 2.761 ms 2.772 ms
    4 203.208.255.197 (203.208.255.197) 2.855 ms 2.989 ms 2.986 ms
    5 203.208.145.245 (203.208.145.245) 3.327 ms 3.419 ms 3.425 ms
    6 ge-1-0-0-0.sngc3-ar2.ix.singtel.com (203.208.172.158) 3.219 ms 203.208.171.169 (203.208.171.169) 2.533 ms 2.525 ms
    7 203.208.153.241 (203.208.153.241) 2.436 ms 2.257 ms 2.309 ms
    8 203.208.171.190 (203.208.171.190) 187.142 ms 203.208.178.186 (203.208.178.186) 182.121 ms 182.331 ms
    9 ge-2-1-0-0.sngc3-ar4.ix.singtel.com (203.208.152.106) 186.352 ms 186.886 ms ge-7-0-0-0.laxow-dr2.ix.singtel.com (203.208.183.158) 187.359 ms
    10 203.208.153.46 (203.208.153.46) 187.519 ms 187.488 ms 187.494 ms
    11 te0-2-0-7.ccr22.lax01.atlas.cogentco.com (154.54.6.241) 185.699 ms te0-3-0-7.ccr21.lax01.atlas.cogentco.com (154.54.1.9) 183.397 ms te0-2-0-7.ccr21.lax01.atlas.cogentco.com (154.54.24.69) 187.455 ms
    12 te0-1-0-3.ccr21.iah01.atlas.cogentco.com (154.54.44.237) 223.296 ms te0-1-0-6.ccr22.iah01.atlas.cogentco.com (66.28.4.237) 220.121 ms 220.220 ms
    13 te0-1-0-6.ccr22.atl01.atlas.cogentco.com (154.54.7.237) 259.441 ms 259.299 ms te0-1-0-6.ccr21.atl01.atlas.cogentco.com (154.54.29.5) 245.012 ms
    14 te0-2-0-3.ccr22.dca01.atlas.cogentco.com (154.54.1.34) 247.542 ms te0-1-0-2.ccr21.dca01.atlas.cogentco.com (154.54.28.238) 238.486 ms te0-5-0-7.ccr21.dca01.atlas.cogentco.com (154.54.42.193) 247.963 ms
    15 te0-5-0-6.ccr21.jfk02.atlas.cogentco.com (154.54.42.22) 250.841 ms te0-1-0-3.ccr21.jfk02.atlas.cogentco.com (154.54.5.245) 250.662 ms te0-4-0-2.ccr21.jfk02.atlas.cogentco.com (154.54.41.2) 247.341 ms
    16 te0-1-0-2.ccr22.bos01.atlas.cogentco.com (154.54.44.38) 322.152 ms te0-4-0-3.ccr22.bos01.atlas.cogentco.com (154.54.44.66) 332.475 ms te0-0-0-5.ccr22.lon13.atlas.cogentco.com (154.54.42.50) 342.309 ms
    17 te0-1-0-1.ccr22.lpl01.atlas.cogentco.com (154.54.42.106) 333.037 ms te0-2-0-1.ccr22.lpl01.atlas.cogentco.com (154.54.0.210) 327.828 ms te0-3-0-1.ccr22.lpl01.atlas.cogentco.com (154.54.1.158) 320.477 ms
    18 te0-0-0-0.ccr21.ham01.atlas.cogentco.com (130.117.50.42) 365.162 ms te0-2-0-3.ccr22.ams03.atlas.cogentco.com (154.54.37.121) 326.256 ms te0-4-0-3.ccr22.ams03.atlas.cogentco.com (154.54.58.69) 338.169 ms
    19 te2-2.ccr01.sto03.atlas.cogentco.com (154.54.38.26) 356.632 ms te0-2-0-0.ccr22.ham01.atlas.cogentco.com (130.117.49.50) 344.478 ms te0-4-0-0.ccr22.ham01.atlas.cogentco.com (154.54.60.182) 339.196 ms
    20 te3-2.ccr02.sto03.atlas.cogentco.com (154.54.38.38) 362.430 ms te2-2.ccr02.sto03.atlas.cogentco.com (154.54.38.34) 358.163 ms te3-1.ccr02.sto03.atlas.cogentco.com (130.117.51.194) 356.375 ms
    21 te3-1.ccr01.sto02.atlas.cogentco.com (154.54.61.62) 357.419 ms 357.096 ms 357.422 ms
    22 149.11.24.18 (149.11.24.18) 360.328 ms po-10.sto3.se.portlane.net (80.67.4.129) 375.817 ms 149.11.24.18 (149.11.24.18) 379.460 ms
    23 * po-10.sto3.se.portlane.net (80.67.4.129) 369.574 ms *

  • gbshousegbshouse Member, Provider

    Traceroutes (IPv6)

    traceroute to us1.rage4.com (2a02:748:a800:149:154:158:203:1), 30 hops max, 80 byte packets

    1 2405:4200:202::241 (2405:4200:202::241) 0.017 ms 0.005 ms 0.005 ms
    2 edge-1.v75.ntp.sg.gs (2405:4200:0:ff05::11) 1.446 ms * *
    3 * * ntt2-RGE.hkix.net (2001:7fa:0:1::ca28:a1db) 102.275 ms
    4 po-1.r00.newthk01.hk.bb.gin.ntt.net (2001:218:6000:2000::2) 52.123 ms 52.103 ms 52.250 ms
    5 xe-0-3-0.r20.newthk02.hk.bb.gin.ntt.net (2001:218:0:2000::6) 51.793 ms 51.787 ms 52.021 ms
    6 as-2.r21.newthk02.hk.bb.gin.ntt.net (2001:218:0:2000::11e) 36.013 ms 51.056 ms 51.045 ms
    7 as-1.r25.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::13d) 157.693 ms 107.338 ms 107.299 ms
    8 ae-9.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::1c5) 79.072 ms 79.660 ms 79.656 ms
    9 as-1.r20.sttlwa01.us.bb.gin.ntt.net (2001:218:0:2000::21) 217.330 ms 212.782 ms 217.285 ms
    10 ae-5.r20.chcgil09.us.bb.gin.ntt.net (2001:418:0:2000::146) 250.055 ms 254.919 ms 229.705 ms
    11 ae-1.r06.chcgil09.us.bb.gin.ntt.net (2001:418:0:2000::4e) 235.407 ms 243.030 ms 243.730 ms
    12 ae-0.ua.chcgil09.us.bb.gin.ntt.net (2001:418:0:5000::293) 247.068 ms 2001:590:2:e::1 (2001:590:2:e::1) 252.886 ms 247.852 ms
    13 ae1-40g.cr1.ord1.us.nlayer.net (2001:590::451f:6f85) 254.016 ms 249.497 ms 249.455 ms
    14 2001:590::451f:6926 (2001:590::451f:6926) 234.921 ms 235.624 ms 234.773 ms

    traceroute to us2.rage4.com (2606:df00:3::d5c4:c403), 30 hops max, 80 byte packets

    1 2405:4200:202::241 (2405:4200:202::241) 0.017 ms 0.005 ms 0.005 ms
    2 edge-1.v75.ntp.sg.gs (2405:4200:0:ff05::11) 1.383 ms * *
    3 * * hurricaneelectric1-RGE.hkix.net (2001:7fa:0:1::ca28:a19e) 38.720 ms
    4 gige-g3-7.core1.lax1.he.net (2001:470:0:16b::1) 195.908 ms 195.894 ms 196.136 ms
    5 10gigabitethernet1-3.core1.lax2.he.net (2001:470:0:72::2) 195.785 ms 196.361 ms 196.356 ms
    6 2001:504:13::59 (2001:504:13::59) 195.723 ms 199.995 ms 199.881 ms
    7 2607:fcd0::1e (2607:fcd0::1e) 200.304 ms 199.578 ms 194.761 ms
    8 hostg-quadra-gw.hostigation.com (2607:fcd0:100:c20::2) 195.627 ms 195.619 ms 195.598 ms

    traceroute to at1.rage4.com (2a03:f80:ed15:158:255:212:26:1), 30 hops max, 80 byte packets

    1 2405:4200:202::241 (2405:4200:202::241) 0.014 ms 0.005 ms 0.005 ms
    2 edge-1.v75.ntp.sg.gs (2405:4200:0:ff05::11) 1.459 ms * *
    3 * * hurricaneelectric1-RGE.hkix.net (2001:7fa:0:1::ca28:a19e) 41.531 ms
    4 gige-g3-7.core1.lax1.he.net (2001:470:0:16b::1) 200.553 ms * 200.732 ms
    5 10gigabitethernet4-3.core1.nyc4.he.net (2001:470:0:10e::2) 255.701 ms 255.695 ms 255.683 ms
    6 10gigabitethernet1-2.core1.lon1.he.net (2001:470:0:128::2) 322.251 ms 321.420 ms 327.887 ms
    7 10gigabitethernet4-2.core1.fra1.he.net (2001:470:0:1d2::2) 345.367 ms 340.442 ms 340.639 ms
    8 gige-g0-1.tserv18.fra1.ipv6.he.net (2001:470:0:a5::2) 338.244 ms 335.230 ms 337.043 ms
    9 2a02:2918:0:fb00::2 (2a02:2918:0:fb00::2) 373.001 ms 373.212 ms 370.444 ms

    traceroute to uk1.rage4.com (2a01:348:70:46:17:63:136:1), 30 hops max, 80 byte packets

    1 2405:4200:202::241 (2405:4200:202::241) 0.014 ms 0.005 ms 0.005 ms
    2 edge-1.v75.ntp.sg.gs (2405:4200:0:ff05::11) 1.384 ms * *
    3 * * *
    4 po-1.r00.newthk01.hk.bb.gin.ntt.net (2001:218:6000:2000::2) 98.996 ms 98.991 ms 99.062 ms
    5 xe-0-3-0.r20.newthk02.hk.bb.gin.ntt.net (2001:218:0:2000::6) 51.287 ms 51.282 ms 51.359 ms
    6 as-1.r22.osakjp01.jp.bb.gin.ntt.net (2001:218:0:2000::191) 114.559 ms 106.673 ms 106.640 ms
    7 as-0.r23.londen03.uk.bb.gin.ntt.net (2001:218:0:2000::1) 262.024 ms 258.881 ms 272.901 ms
    8 ae-2.r02.londen03.uk.bb.gin.ntt.net (2001:728:0:2000::2a) 277.146 ms 270.019 ms 272.418 ms
    9 ae-2.rt0.the.uk.goscomb.net (2001:728:0:5000::6e) 349.954 ms 334.333 ms 347.116 ms
    10 xe-0-1-1.cs0.the.uk.goscomb.net (2a01:348::36:1:1) 342.657 ms 341.883 ms 333.779 ms
    11 xe-0-1-0.cs0.gs2.uk.goscomb.net (2a01:348::24:1:1) 332.864 ms 345.478 ms 341.401 ms

    traceroute to se1.rage4.com (2a00:1a28:1251:178:73:210:161:1), 30 hops max, 80 byte packets

    1 2405:4200:202::241 (2405:4200:202::241) 0.016 ms 0.005 ms 0.004 ms
    2 ge-3-2-0-110.a00.sngpsi02.sg.ra.gin.ntt.net (2001:218:4000:5000::69) 10.482 ms 10.608 ms 10.739 ms
    3 ae-1.r20.sngpsi02.sg.bb.gin.ntt.net (2001:218:0:6000::199) 0.924 ms 0.918 ms 1.104 ms
    4 as-0.r22.londen03.uk.bb.gin.ntt.net (2001:218:0:2000::10d) 182.016 ms 181.607 ms 181.994 ms
    5 2001:7f8:4::a6d4:1 (2001:7f8:4::a6d4:1) 188.488 ms 188.634 ms 188.628 ms
    6 te-2-1.sto3.se.portlane.net (2a00:1a28:1:2003::1) 218.270 ms 205.808 ms 206.021 ms

  • gbshousegbshouse Member, Provider

    What is missing:

    • Debian 6 64bit (running Debian 6 32bit)

    Other:

    • from Ireland - slow as hell :)
  • KenshinKenshin Member

    @gbshouse said: - Debian 6 64bit (running Debian 6 32bit)

    Host is 32 bit to maximize memory, so not happening sadly.

    @gbshouse said: - from Ireland - slow as hell :)

    Same issue with OVH likely, EU routes are a mixed lot depending on the transit provider's peering.

    I'll take a closer look after dinner (7pm here now) on some of the routes to see if I can optimize them any further. I'm particularly concerned that the Stockholm route is better on IPv6 than IPv4.

    Again, thanks. Really appreciated. The rest of you guys/girls with any odd traceroute issue do let me know and I'll try to explain, or adjust if I am able to. Sadly since we're halfway around the globe from EU, depending on which direction it goes the EU routes tend to be wonky.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • I'd like to try one as well, from SG here. Thanks!

  • I've written many reviews on hosting companies and would be happy to do one for you :)
    Example: http://www.lowendtalk.com/discussion/546/community-review-kiloserve-365-mb-kvm-yearly

  • gbshousegbshouse Member, Provider
    edited May 2012

    @Kenshin - take a look on this:
    edge-1.v75.ntp.sg.gs (2405:4200:0:ff05::11) 1.446 ms
    edge-1.v71.com3.sg.gs (203.175.175.129) 1.805 ms 1.918 ms 1.982 ms

  • Got mine, stuff is looking very decent thus far.

    Going to do a review, but more importantly, put some actual apps I use on it later tonight :)

    -- BOFH

  • gbshousegbshouse Member, Provider
    edited May 2012

    Download 100mb from CacheFly

    --2012-05-04 15:45:59-- http://cachefly.cachefly.net/100mb.test
    Resolving cachefly.cachefly.net... 204.93.150.150
    Connecting to cachefly.cachefly.net|204.93.150.150|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 104857600 (100M) [application/octet-stream]
    Saving to: 100mb.test.1' 104,857,600 905K/s in 1m 45s 2012-05-04 15:47:44 (979 KB/s) - 100mb.test.1' saved [104857600/104857600]

  • MikyMiky Member
    edited May 2012

    Probably too busy to be an efficient tester.. too bad :-( But I'd love to see how it could help from Thailand!

  • I've done a little review, check it out if you folks want to:

    http://blog.tomoyo.eu/oneasiahost-512mb-ovz-in-singapore-review/

    Time to install some apps I actually intend to use now :P

    Thanked by 1maxexcloo

    -- BOFH

  • KenshinKenshin Member

    @Boltersdriveer @maxexcloo Check PM

    @gbshouse said: @Kenshin - take a look on this:

    edge-1.v75.ntp.sg.gs (2405:4200:0:ff05::11) 1.446 ms
    edge-1.v71.com3.sg.gs (203.175.175.129) 1.805 ms 1.918 ms 1.982 ms

    HostSG (SG.GS) has 3 locations in Singapore including Global Switch, so these hop over the inter-datacentre links. Each location has it's own transit providers. NTP has PCCW, COM3 is SingTel/SingNet, GS is NTT.

    @liam said: I personally don't like the global switch owners... so I find it hard to buy a vps utilising their services.

    Global Switch only provides the space which NTT rents and resells to us. SOX/SGIX terminates at Global Switch so it was a network decision we made to expand there. Nevertheless will respect your decision, but do feel free to request for one if you change your mind and there's still slots.

    @gbshouse said: Download 100mb from CacheFly

    I'm aware of the speeds to CacheFly, but it was intended because we'll be connecting to CacheFly via our HKIX link. The two closest CacheFly servers are HK and JP, so definitely HK would be the ideal choice. Speed wise likely due to the pipe we have to HKIX, high speed not really possible. The reason I arranged for so many peering links was to ensure that we had direct and low latency paths to as many places within SG/Asia as possible, sadly in terms of costs we don't really save a lot by doing so.

    Thanks everyone who has written feedback, especially Wintereise. I'm going to work on analyzing the routes and improve whatever I can.

    Currently 8 slots out: Taylor, kbar, gbshouse, seikan, Bernardoo, Wintereise, Boltsdriveer, maxexcloo. 2 slots left. Removing quirkyquark from the list as he's using an extra slot I reserved for the helpful guys that assisted with my earlier traceroute requests.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • No problem, thanks for allowing us the chance to use something in SG :)

    -- BOFH

  • @Kenshin said: we do not offer burstable RAM or vswap

    So for the 512MB plan it'd be 512MB on both oomguarpages and privvmpages?

    © 2011-2018 eLohkCalb

  • klikliklikli Member
    edited May 2012

    It's routing through SingTel - not via your PCCW transit - on a Netvigator connection. See:

    traceroute to 116.251.210.1 (116.251.210.1), 64 hops max, 52 byte packets
    1 172.28.2.1 (172.28.2.1) 0.906 ms
    2 dsldevice (192.168.8.1) 41.936 ms
    3 n112119178254.netvigator.com (112.119.178.254) 11.899 ms
    4 n219076122250.netvigator.com (219.76.122.250) 31.727 ms
    5 *
    6 tenge2-4.br02.hkg04.pccwbtn.net (63.218.252.173) 13.385 ms
    7 singtel.te4.2.br02.sin02.pccwbtn.net (63.218.213.42) 48.164 ms
    8 ge-2-0-0.sn-sintp1-bo303.singnet.com.sg (165.21.12.106) 45.858 ms
    9 165.21.255.74 (165.21.255.74) 81.234 ms
    10 115.42.248.33 (115.42.248.33) 46.096 ms
    11 115.42.248.34 (115.42.248.34) 47.602 ms
    12 edge-1.v50.com3.sg.gs (203.175.175.17) 50.600 ms
    13 edge-1.v71.globalswitch.sg.gs (203.175.175.132) 53.534 ms
    14 116.251.210.240 (116.251.210.240) 51.427 ms
    15 dns1.oneasiahost.com (116.251.210.1) 53.529 ms

    PS: And I don't think HE is connected either.

  • KenshinKenshin Member

    @gbshouse said: at1 - Graz, Austria

    PING at1.rage4.com (158.255.212.26) 56(84) bytes of data.
    64 bytes from at1.rage4.com (158.255.212.26): icmp_req=1 ttl=45 time=216 ms
    PING at1.rage4.com(2a03:f80:ed15:158:255:212:26:1) 56 data bytes
    64 bytes from 2a03:f80:ed15:158:255:212:26:1: icmp_seq=1 ttl=49 time=379 ms

    I took a look at this, but EDIS is single homed on IPv6 and all 3 of my transit links behave the same way. Was using HE via HKIX for outgoing, but now using NTT so I got the pings reduced to about 310ms over IPv6.

    @gbshouse said: uk1 - London, UK

    PING uk1.rage4.com (46.17.63.136) 56(84) bytes of data.
    64 bytes from uk1.rage4.com (46.17.63.136): icmp_req=1 ttl=47 time=192 ms
    PING uk1.rage4.com(2a01:348:70:46:17:63:136:1) 56 data bytes
    64 bytes from 2a01:348:70:46:17:63:136:1: icmp_seq=1 ttl=54 time=329 ms

    Was due to HKIX link preference, has been fixed so it's now about 184ms via IPv6

    @gbshouse said: se1 - Stockholm, Sweden

    PING se1.rage4.com (178.73.210.161) 56(84) bytes of data.
    64 bytes from se1.rage4.com (178.73.210.161): icmp_req=1 ttl=39 time=359 ms
    PING se1.rage4.com(2a00:1a28:1251:178:73:210:161:1) 56 data bytes
    64 bytes from 2a00:1a28:1251:178:73:210:161:1: icmp_seq=1 ttl=57 time=207 ms

    This is one of the real oddities I've ever seen, IPv4 being worse than IPv6. However, sadly there's nothing I can do for this one. Reason being, Portlane (SE) is using Cogent (AS174) heavily for both in/out routes. I even tested via their looking glass, everything via IPv4 is Cogent. SG > US > SE thus the latency.

    Reason why IPv6 route is 200ms? They are peering with NTT at LINX (London IX), and we're using NTT.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • KenshinKenshin Member

    @eLohkCalb said: So for the 512MB plan it'd be 512MB on both oomguarpages and privvmpages?

    That's right.

    @klikli said: It's routing through SingTel - not via your PCCW transit - on a Netvigator connection.

    I spoke to you regarding this in my previous thread. Netvigator is ignoring our HKIX prefixes and using our transit links. Thanks for spotting the PCCW transit, the 116.251.210.0/24 range wasn't broadcasted there. Can you try again to see if it's reflected now?

    traceroute to 112.119.178.254 (112.119.178.254), 30 hops max, 60 byte packets
     1  116.251.210.253 (116.251.210.253)  38.591 ms  38.649 ms  38.722 ms
     2  edge-1.v75.ntp.sg.gs (203.175.175.164)  1.149 ms  1.404 ms  1.411 ms
     3  ims5-10G.hkix.net (202.40.161.25)  36.754 ms * *
     4  n219076107037.netvigator.com (219.76.107.37)  37.976 ms  38.226 ms  38.209 ms
     5  n112119178254.netvigator.com (112.119.178.254)  39.843 ms  39.932 ms  39.942 ms

    @klikli said: PS: And I don't think HE is connected either.

    HE only for IPv6 and connected via our HKIX link. Sadly in Singapore, even SingTel's IPv6 routes are rubbish even though I have it turned on.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • @Kenshin said: SingTel's IPv6 routes are rubbish even though I have it turned on.

    Hahaha, I guess most if not all of the SG ISP IPv6 routes are rubbish.

    © 2011-2018 eLohkCalb

  • seikanseikan Member

    A quick benchmark for the VPS I got:

    ==============================
           BENCHMARK RESULT
    ==============================
    CPU Model      : Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
    CPU Cores      : 4
    CPU Frequency  : 3392.116 MHz
    Total Memory   : 512 MB
    Total Swap     : 0 MB
    Download Speed : 1.06MB/s
    Disk I/O Speed : 374 MB/s

    Hobby Projects: DNMin | PingBear

  • klikliklikli Member

    @Kenshin said: HE only for IPv6 and connected via our HKIX link. Sadly in Singapore, even SingTel's IPv6 routes are rubbish even though I have it turned on.

    Actually are you "transit" or "peering" with HE?

    BTW - getting on your direct transit now:
    1 172.28.2.1 (172.28.2.1) 54.383 ms
    2 dsldevice (192.168.8.1) 98.281 ms
    3 n112119178254.netvigator.com (112.119.178.254) 12.511 ms
    4 n219076122250.netvigator.com (219.76.122.250) 12.122 ms
    5 *
    6 tenge2-4.br02.hkg04.pccwbtn.net (63.218.252.173) 16.102 ms
    7 63.216.152.186 (63.216.152.186) 49.361 ms
    8 edge-1.v73.com3.sg.gs (203.175.175.145) 51.194 ms
    9 edge-1.v71.globalswitch.sg.gs (203.175.175.132) 52.077 ms
    10 116.251.210.240 (116.251.210.240) 52.958 ms
    11 dns1.oneasiahost.com (116.251.210.1) 54.064 ms

  • KenshinKenshin Member
    edited May 2012

    @klikli said: Actually are you "transit" or "peering" with HE?

    HE calls it IPv6 transit as per their email to me, but effectively it's HE's full IPv6 routing table over HKIX peering fabric via a direct peering session between us (not MLPA).

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • key900key900 Member, Provider
    edited May 2012

    IPv4 281~ pings. IPV6 348~

    *LetBox.Com Make it Simple, Pure NVMe + Block Storage Boxes!.
  • KenshinKenshin Member
    edited May 2012

    I still find it amusing how netvigator, effectively PCCW, doesn't use the HKIX routes we send via the MLPA route servers but prefers the transit routes instead. So I've setup a /24 range that I only broadcast through HKIX, and it seems that it does work fine when I traceroute with source IP.

    Can you try a traceroute to 116.251.211.1 if you have time? This should go through our HKIX link, if this is true then I'll really need to find a shell on a netvigator link to adjust the outgoing routes on our end and hope for the best.

    > traceroute source 116.251.211.1 112.119.178.254      
    traceroute to 112.119.178.254 (112.119.178.254) from 116.251.211.1, 30 hops max, 40 byte packets
     1  edge-1.v71.com3.sg.gs (203.175.175.129)  2.460 ms edge-2.v71.com3.sg.gs (203.175.175.130)  2.089 ms edge-1.v71.com3.sg.gs (203.175.175.129)  2.120 ms
     2  edge-1.v73.ntp.sg.gs (203.175.175.148)  3.525 ms  5.414 ms  3.422 ms
     3  ims5-10G.hkix.net (202.40.161.25)  40.244 ms  40.396 ms  44.081 ms
     4  n219076107037.netvigator.com (219.76.107.37)  103.506 ms  40.585 ms  40.713 ms
     5  n112119178254.netvigator.com (112.119.178.254)  42.907 ms  41.318 ms  40.924 ms

    Also, do try 116.251.208.1 as well, it's broadcasted via HKIX + SingNet with heavy prepending (6x). If 116.251.208.1 doesn't go via HKIX but 116.251.211.1 does, then basically netvigator probably have a lower local-preference for HKIX MLPA routes and it's not something I can control.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • Do you still have another free slot? I'm willing to test it out. Thanks..

  • KenshinKenshin Member

    @Wira_Soenaryo said: Do you still have another free slot? I'm willing to test it out. Thanks..

    You got PM.

    Currently 9 slots out: Taylor, kbar, gbshouse, seikan, Bernardoo, Wintereise, Boltsdriveer, maxexcloo, Wira_Soenaryo. 1 slot left.

    Asia VPS | Asia Dedicated Server OneAsiaHost - Singapore based Asia-Centric VPS & Dedicated Servers
  • Thank you...

  • qjqqjq Member

    great, seems like there's still one more slot. I am based in singapore. May i have it?

Sign In or Register to comment.