New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
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
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]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
@Boltersdriveer @maxexcloo Check PM
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.
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.
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.
No problem, thanks for allowing us the chance to use something in SG
So for the 512MB plan it'd be 512MB on both oomguarpages and privvmpages?
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.
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.
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
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.
That's right.
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?
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.
Hahaha, I guess most if not all of the SG ISP IPv6 routes are rubbish.
A quick benchmark for the VPS I got:
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
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).
IPv4 281~ pings. IPV6 348~
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.
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.
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.
Thank you...
great, seems like there's still one more slot. I am based in singapore. May i have it?
Can I order for the $7/month one?
Sorry, requirement is for active members only. You're a new account in LET.
Currently not taking orders yet, I want to be sure all aspects are covered before I start collecting a cent from anyone.
Hello,
Brief test result from me
From Indonesia (using Telkom Flexi)
tracert 116.251.210.109
Tracing route to 116.251.210.109 over a maximum of 30 hops
1 308 ms 105 ms 143 ms 172.17.164.130
2 161 ms 119 ms 120 ms 172.17.164.137
3 94 ms 489 ms 265 ms 172.17.164.194
4 116 ms 175 ms 124 ms 192.168.102.73
5 166 ms 119 ms * 62.subnet118-98-61.astinet.telkom.net.id [118.98.61.62]
6 338 ms 304 ms 240 ms 14.190.240.180.telin.sg [180.240.190.14]
7 799 ms 190 ms 411 ms 203.208.174.177
8 229 ms 484 ms 458 ms 203.208.191.102
9 844 ms 644 ms 866 ms Ge-2-0-0.sn-sintp1-bo303.singnet.com.sg [165.21.12.106]
10 230 ms 194 ms 207 ms 165.21.255.74
11 329 ms 174 ms 177 ms 115.42.248.33
12 217 ms 215 ms 213 ms 115.42.248.34
13 144 ms 155 ms 163 ms edge-2.v51.com3.sg.gs [203.175.175.26]
14 151 ms 156 ms 293 ms edge-1.v71.globalswitch.sg.gs [203.175.175.132]
15 151 ms 149 ms 153 ms 116.251.210.241
16 169 ms 155 ms 155 ms 116.251.210.109
Trace complete.
From New York
traceroute 116.251.210.109
traceroute to 116.251.210.109 (116.251.210.109), 30 hops max, 60 byte packets
1 ny8.webrulon.com (199.167.198.15) 0.082 ms 0.052 ms 0.047 ms
2 vl204.mag01.jfk01.atlas.cogentco.com (38.104.167.93) 64.325 ms 64.319 ms 64.267 ms
3 te2-1.ccr02.jfk01.atlas.cogentco.com (154.54.80.89) 36.126 ms 36.143 ms 36.095 ms
4 te0-4-0-6.ccr21.jfk02.atlas.cogentco.com (154.54.40.34) 0.874 ms te0-3-0-7.ccr21.jfk02.atlas.cogentco.com (154.54.7.69) 0.992 ms te0-7-0-2.ccr22.jfk02.atlas.cogentco.com (154.54.24.150) 0.911 ms
5 te0-4-0-6.ccr22.dca01.atlas.cogentco.com (154.54.42.29) 7.307 ms te0-2-0-2.ccr21.ord01.atlas.cogentco.com (154.54.43.86) 22.212 ms te0-4-0-0.ccr21.ord01.atlas.cogentco.com (154.54.43.94) 22.255 ms
6 te0-1-0-3.ccr21.mci01.atlas.cogentco.com (154.54.25.81) 34.378 ms 34.324 ms te0-2-0-3.ccr22.atl01.atlas.cogentco.com (154.54.1.33) 32.672 ms
7 te0-0-0-1.ccr22.iah01.atlas.cogentco.com (154.54.5.94) 33.081 ms te0-2-0-7.ccr22.iah01.atlas.cogentco.com (154.54.42.213) 32.711 ms te0-2-0-6.ccr21.sfo01.atlas.cogentco.com (154.54.45.62) 72.057 ms
8 te0-2-0-3.ccr22.lax01.atlas.cogentco.com (154.54.45.2) 68.615 ms te4-5.ccr02.sjc04.atlas.cogentco.com (154.54.5.114) 260.247 ms te0-0-0-5.ccr22.lax01.atlas.cogentco.com (154.54.5.194) 68.749 ms
9 singtel.sjc04.atlas.cogentco.com (154.54.10.170) 72.470 ms 72.464 ms 72.447 ms
10 203.208.149.6 (203.208.149.6) 74.629 ms 74.582 ms 203.208.171.161 (203.208.171.161) 72.489 ms
11 203.208.153.125 (203.208.153.125) 244.912 ms ge-1-0-0-0.laxow-cr2.ix.singtel.com (203.208.149.118) 68.559 ms 203.208.152.105 (203.208.152.105) 68.599 ms
12 203.208.171.234 (203.208.171.234) 68.725 ms ge-0-1-3-0.laxow-dr1.ix.singtel.com (203.208.149.38) 68.738 ms so-2-0-2-0.sngtp-cr2.ix.singtel.com (203.208.149.29) 261.353 ms
13 203.208.174.182 (203.208.174.182) 252.870 ms 203.208.191.102 (203.208.191.102) 262.289 ms 203.208.174.182 (203.208.174.182) 266.419 ms
14 ge-3-0-0-0.sngtp-dr2.ix.singtel.com (203.208.151.157) 265.400 ms 203.208.166.62 (203.208.166.62) 244.679 ms xe-0-0-0-0.sngc3-cr2.ix.singtel.com (203.208.183.14) 247.539 ms
15 203.208.174.182 (203.208.174.182) 254.517 ms 264.223 ms POS0-0-0.venus.ix.singtel.com (203.208.172.10) 240.143 ms
16 115.42.248.33 (115.42.248.33) 285.256 ms Ge-2-0-0.sn-sintp1-bo303.singnet.com.sg (165.21.12.106) 243.651 ms 255.363 ms
17 115.42.248.34 (115.42.248.34) 238.127 ms 165.21.255.74 (165.21.255.74) 249.675 ms 115.42.248.34 (115.42.248.34) 241.537 ms
18 Ge-2-0-0.sn-sintp1-bo303.singnet.com.sg (165.21.12.106) 247.917 ms 115.42.248.33 (115.42.248.33) 233.545 ms 254.758 ms
19 edge-1.v71.globalswitch.sg.gs (203.175.175.132) 270.141 ms 251.064 ms 115.42.248.34 (115.42.248.34) 257.288 ms
20 115.42.248.33 (115.42.248.33) 254.852 ms 243.193 ms 116.251.210.241 (116.251.210.241) 278.207 ms
21 edge-1.v71.globalswitch.sg.gs (203.175.175.132) 265.653 ms 116.251.210.109 (116.251.210.109) 253.074 ms 252.940 ms
From Netherland
root@venus:~# traceroute 116.251.210.109
traceroute to 116.251.210.109 (116.251.210.109), 30 hops max, 60 byte packets
1 snelis.com (89.207.130.1) 0.439 ms 0.514 ms 0.603 ms
2 84.244.128.97 (84.244.128.97) 1.151 ms 1.223 ms 1.218 ms
3 cr01-sr-ams.we-dare.net (92.48.225.1) 1.621 ms 1.731 ms 1.884 ms
4 TenGE13-2.br02.ams01.pccwbtn.net (195.69.145.37) 3.554 ms 3.605 ms 3.593 ms
5 63.216.152.186 (63.216.152.186) 269.684 ms 269.800 ms 269.707 ms
6 edge-1.v75.globalswitch.sg.gs (203.175.175.161) 270.324 ms 270.882 ms 269.763 ms
7 116.251.210.241 (116.251.210.241) 269.429 ms 269.720 ms 270.051 ms
8 116.251.210.109 (116.251.210.109) 269.717 ms 269.785 ms 269.772 ms
root@venus:~#
Disk i/o check
[root@saturn ~]# 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.67807 s, 401 MB/s
[root@saturn ~]#
Thanks...
There's a really nice IO speed on these vps's
tracert 116.251.210.109
Tracing route to 116.251.210.109 over a maximum of 30 hops
1 308 ms 105 ms 143 ms 172.17.164.130
2 161 ms 119 ms 120 ms 172.17.164.137
3 94 ms 489 ms 265 ms 172.17.164.194
4 116 ms 175 ms 124 ms 192.168.102.73
5 166 ms 119 ms * 62.subnet118-98-61.astinet.telkom.net.id [118.98.61.62]
6 338 ms 304 ms 240 ms 14.190.240.180.telin.sg [180.240.190.14]
7 799 ms 190 ms 411 ms 203.208.174.177
8 229 ms 484 ms 458 ms 203.208.191.102
9 844 ms 644 ms 866 ms Ge-2-0-0.sn-sintp1-bo303.singnet.com.sg [165.21.12.106]
10 230 ms 194 ms 207 ms 165.21.255.74
11 329 ms 174 ms 177 ms 115.42.248.33
12 217 ms 215 ms 213 ms 115.42.248.34
13 144 ms 155 ms 163 ms edge-2.v51.com3.sg.gs [203.175.175.26]
14 151 ms 156 ms 293 ms edge-1.v71.globalswitch.sg.gs [203.175.175.132]
15 151 ms 149 ms 153 ms 116.251.210.241
16 169 ms 155 ms 155 ms 116.251.210.109
This is really weird, we're peering PT Telekomunikasi directly via AS7713. Can you try a traceroute to 116.251.208.1, as well as if possible, traceroute to your IP address from the VPS? Below is a traceroute from the host node to your 5th hop IP.
From Japan:
Looks pretty solid.
Well, would I get one VPS left and joining the test group?
Hello Kenshin,
Here is the result..
Tracing route to singtel.megapop-1.com3.sg.gs [116.251.208.1]
over a maximum of 30 hops:
1 * 176 ms 188 ms 172.17.164.130
2 307 ms 313 ms 345 ms 172.17.164.129
3 181 ms 148 ms 174 ms 172.17.164.194
4 191 ms 216 ms 213 ms 192.168.102.73
5 436 ms 435 ms * 62.subnet118-98-61.astinet.telkom.net.id [118.98
.61.62]
6 * 181 ms 176 ms sgix.sg.gs [218.100.70.30]
7 189 ms 189 ms 176 ms edge-1.v71.com3.sg.gs [203.175.175.129]
8 243 ms 239 ms 234 ms ce-1.v53.com3.sg.gs [203.175.175.55]
9 258 ms 267 ms 307 ms singtel.megapop-1.com3.sg.gs [116.251.208.1]
Trace complete.
It use less hops on that IP..
Anyway, I can't traceroute back to my IP.. seems something has blocked it..
traceroute to 172.17.164.130 (172.17.164.130), 30 hops max, 60 byte packets
1 116.251.210.241 (116.251.210.241) 0.022 ms 0.007 ms 0.005 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 *^C
[root@saturn ~]# traceroute 172.17.164.130
traceroute to 172.17.164.130 (172.17.164.130), 30 hops max, 60 byte packets
1 116.251.210.241 (116.251.210.241) 0.017 ms 0.007 ms 0.006 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 *^C
[root@saturn ~]#
Thanks..
Here's a traceroute from the Philippines, if it's helpful.
2 119.93.255.209 (119.93.255.209) 17.110 ms 20.448 ms 17.508 ms 3 210.213.132.22.static.pldt.net (210.213.132.22) 28.429 ms 21.166 ms 17.353 ms 4 210.213.128.82.static.pldt.net (210.213.128.82) 27.903 ms 18.248 ms 17.326 ms 5 210.213.129.45.static.pldt.net (210.213.129.45) 18.420 ms 18.908 ms 19.455 ms 6 210.213.128.49.static.pldt.net (210.213.128.49) 17.086 ms 19.676 ms 17.173 ms 7 ge-10-1-0.spc-gw2.n4i.pldt.net (210.213.131.21) 18.397 ms 18.960 ms 17.668 ms 8 p16-2-0-1.r20.newthk02.hk.bb.gin.ntt.net (129.250.12.221) 94.491 ms 95.827 ms 97.487 ms 9 p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.6.97) 133.172 ms 134.529 ms 142.556 ms 10 ae-1.a00.sngpsi02.sg.ra.gin.ntt.net (116.51.16.246) 132.180 ms 134.039 ms 133.688 ms 11 ge-3-2-0-110.a00.sngpsi02.sg.ra.gin.ntt.net (116.51.17.238) 149.436 ms 149.801 ms 148.958 ms 12 116.251.210.240 (116.251.210.240) 134.227 ms 133.743 ms 133.212 ms 13 dns1.oneasiahost.com (116.251.210.1) 149.974 ms 149.294 ms 149.738 ms
Traceroute from StarHub MOL:
Great pings here!