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
What is the ETA?
I'm currently looking for a Low End Singaporean Box.
Does anyone know how this compares with the only other Singaore budget VPS i.e. ExpertVM ?
Anyway if there is still a slot available I would like to have it pls
It down now
Pinging 116.251.211.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Tracing route to 116.251.211.1 over a maximum of 30 hops
1 1 ms 2 ms 1 ms 192.168.1.1
2 13 ms 13 ms 13 ms ZGZIGW-R05C-SHR-EG [163.121.172.116]
3 16 ms 15 ms 17 ms host-163.121.xxxxx.tedata.net [163.121.xxxx]
4 16 ms 18 ms 16 ms host-163.121.xxxx.tedata.net [163.121.xxx]
5 16 ms 17 ms 16 ms host-163.121.xxxx.tedata.net [163.121.xx]
6 16 ms 17 ms 16 ms host-163.121.xxx.tedata.net [163.121.xx
]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * *
Is there any free slot?
I'm willing to test too.
But is HE announcing your prefixes to its peers?
Yes for sure - considering, you have only announce that prefix via HKIX! :P
1 172.28.2.1 (172.28.2.1) 0.941 ms
2 dsldevice (192.168.8.1) 11.618 ms
3 n112119178254.netvigator.com (112.119.178.254) 11.788 ms
4 n219076122230.netvigator.com (219.76.122.230) 20.697 ms
5 218.102.21.70 (218.102.21.70) 13.152 ms
6 hostsg-rfe.hkix.net (202.40.160.212) 49.619 ms
7 edge-1.v73.com3.sg.gs (203.175.175.145) 52.694 ms
8 116.251.211.1 (116.251.211.1) 54.788 ms
1 172.28.2.1 (172.28.2.1) 1.727 ms
2 dsldevice (192.168.8.1) 44.459 ms
3 n112119178254.netvigator.com (112.119.178.254) 12.716 ms
4 n219076122214.netvigator.com (219.76.122.214) 13.772 ms
5 *
6 tenge2-4.br02.hkg04.pccwbtn.net (63.218.252.173) 13.454 ms
7 singtel.te4.2.br02.sin02.pccwbtn.net (63.218.213.42) 45.004 ms
8 xe-11-3-0.orchard.singnet.com.sg (165.21.12.87) 54.976 ms
9 165.21.255.22 (165.21.255.22) 48.707 ms
10 202.176.211.35 (202.176.211.35) 49.845 ms
11 ce-1.v52.com3.sg.gs (203.175.175.39) 58.546 ms
12 singtel.megapop-1.com3.sg.gs (116.251.208.1) 52.384 ms
In fact, I think it make perfect sense to route through private transit instead of local IX. However, in the first place, I raised my question as follows: "It's routing through SingTel - not via your PCCW transit - on a Netvigator connection." However, it seems to be fixed now:
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) 28.760 ms
2 dsldevice (192.168.8.1) 24.410 ms
3 n112119178254.netvigator.com (112.119.178.254) 11.674 ms
4 n219076122250.netvigator.com (219.76.122.250) 12.835 ms
5 pcd507254.netvigator.com (218.102.39.254) 13.094 ms
6 tenge2-4.br02.hkg04.pccwbtn.net (63.218.252.173) 12.915 ms
7 63.216.152.186 (63.216.152.186) 49.244 ms
8 edge-1.v73.com3.sg.gs (203.175.175.145) 51.469 ms
9 edge-1.v71.globalswitch.sg.gs (203.175.175.132) 54.006 ms
10 116.251.210.240 (116.251.210.240) 54.103 ms
11 dns1.oneasiahost.com (116.251.210.1) 54.953 ms
If you need that, just inbox me:)
PM sent. Final slot out to giang.
sgix.sg.gs is correct, you should be seeing that. Can you try traceroute to your VPS IP again?
Thanks, appreciated. I'm aware PDLT is heavily reliant on their NTT connection, so I did some route tweaks in that direction so PDLT users have very good connections to us.
Thanks. Not good for me though, Starhub should be ideally routed through SingNet instead of PCCW. I never noticed this, time to optimize.
I'm currently looking for a Low End Singaporean Box.
I'm looking at a week to a month, a week for the rest of the website content to be done up, and if the feedback I get is positive enough that I feel it's safe to launch as a commercial product. Otherwise up to a month if I need to tweak things. I'm hoping for a week though, the testers are very active with feedback and it helps me a lot.
Sorry, last slot just went out to giang and you don't meet the post requirement either.
Ah sorry for the confusion, 116.251.211.1 is only meant for klikli to test via HK. It's not reachable from anywhere except HK.
I'm willing to test too.
Sorry, last slot just went out to giang and you don't meet the post requirement either.
Yep, confirmed through routeviews long time ago when I only had NTT + HE. SingTel came in only a few weeks ago. A lot of routes through HE since I believe they offered the free IPv6 transit to everyone they peer with.
Private transit shouldn't be preferred for my case because my transit routes are prepended to prefer peering routes.
Not using PCCW was my bad, the range wasn't advertised via PCCW, only through the others, great catch. But still I would have preferred if the peering link was used. But considering 116.251.208.1 still went through SingTel more or less there's nothing I can do cause this is how it looks like at routeviews, which means I was right about them using localpref to override the peering route.
BGP routing table entry for 116.251.208.0/24, version 3559065546 Paths: (34 available, best #18, table Default-IP-Routing-Table) Flag: 0x820 Not advertised to any peer 2828 7473 9911 24482 24482 24482 24482 24482 24482 24482 65.106.7.139 from 65.106.7.139 (66.239.189.139) Origin IGP, metric 3, localpref 100, valid, external 7660 4635 24482 203.181.248.168 from 203.181.248.168 (203.181.248.168) Origin IGP, localpref 100, valid, external, best Community: 7660:6I got my test VPS, here is tracert:
Geekbench score: 7589, pretty high
http://browse.geekbench.ca/geekbench2/648809
Hello Kenshin,
Just did another traceroute into my vps... But the result is exactly the same with my previous one..
Any idea why it doesn't go to sgix.sg.gs instead it goes to telin.sg after hops number 5 (telkom.net.id)?
Hey Kenshin, mind providing a plan in between 512MB and 1GB of RAM? Ideally, 768MB of RAM. Thanks!
Any idea why it doesn't go to sgix.sg.gs instead it goes to telin.sg after hops number 5 (telkom.net.id)?
Your ISP is likely preferring the transit (international) route instead of the peering route we have. From your results this is something I may be able to do something about, give me some time and I'll try to work it out. Hope you don't mind me bugging you for a few more traceroute tests later on.
Bumped you to 1GB RAM for now via SolusVM.
Anyway with regards to the Starhub using PCCW instead, I figured out the reason already and it has to do with the odd arrangement between Starhub and SingTel/SingNet peering/routing. Nothing much I can do, so incoming will be via PCCW, outgoing via SingTel/SingNet.
@Kenshin: Eh, I don't really need the 1GB for now. Just saying it might be nice to get 768MB plans since 1GB is kinda too much, and 768 would kinda be just nice :P .
@Boltsdriveer: Hmm, noted but the price difference would be quite odd so probably not going to happen.
No worries.. feel free to bugging me out
Anyway, I plan to use your vps as my private vpn... if this hops issue can be shorten up.. I think it would be also good for my private vpn performance..
I will try using another provider (SmartFren) tomorrow.
Thanks..
Just to share a few latency oddity that you guys have probably never seen nor even though was possible in Singapore. First, an advance apology to giang for using your IPs for the following traceroute, as I was curious about your traceroute going via HKIX so I tried the traceroute from each of my transit links and US boxes, results were amazing.
Target IP is in Vietnam, we're located in Singapore. Direct distance from SG to VN would be shorter than SG to HK on the map, so expected latency is about 50ms. Results?
HKIX: 84ms (SG > HK > VN)
SingTel: 330ms (SG > UK LINX > VN)
PCCW: 282ms (SG > CN > VN)
NTT: 54ms (SG > VN)
US WholeSaleInternet: 244ms
US BuyVM: 313ms
This is just one of the few oddities with routes within the asian region, which is why I end up being pretty obsessed with route optimization.
Anyway, I plan to use your vps as my private vpn... if this hops issue can be shorten up.. I think it would be also good for my private vpn performance..
I will try using another provider (SmartFren) tomorrow.
Thanks..
Sent you a PM,
SmartFren should be fun if this is anything to go by:
@Kenshin: StarHub has pretty good routes to BuyVM (200ms). You may want to look into that. Traceroute as follows:
@Boltersdriveer: Your VPS should be doing about 200ms to BuyVM as well, so still within margins (US average 170-250ms from SG). NTT does better at 183ms but it's minimal improvement so I didn't feel there's need for route optimization yet.
Reason why I never considered Starhub's bandwidth is because they don't have any international connectivity that is significantly superior to SingTel/NTT/PCCW. I'd probably take PacNet anytime over Starhub due to their extensive network reach in Asia, but currently the 3 I have basically gives me enough option to route optimize, only problem which I've always known and has been demonstrated by some testers is the routes to EU are still a hit and miss, though I've been looking into this for a while but for the time being still no solution.
Here is a traceroute from Italy.
No, this makes sense and has the totally serious background (talked with a network engineer at netvigator often in the past) that their HLIX port is oversold at over 350:1 and they get basically free transit at 1:3 contention anyway.
So in short, they're only there to "look" as though they are there and offer their routes (as per HKIX policy, all HK routes to be advertised). Not surprised, just amused I guess. After you see the rubbish the Tier-1s in SG do between themselves, nothing is surprising anymore. Fancy your traffic between the 2 biggest ISPs in SG going to HK (if lucky) or US/UK (more often) and back? Welcome to Singapore.
Though to be honest, more recently it's not as bad.
Looks like end of the day peering works for everyone except the Tier-1s, since they get enough transit not to need to deal with open peering at all. I remember reading this @ Dr.Peering, guess it's pretty true.
Hello Kenshin,
Still resulting the same one using Telkom until now..
Anyway, here the result from SmartFren provider
Thanks..
Do you have any plans to include PacNet to your BGP mix? BTW, just feeling curious can you do a traceroute to CacheFly and EdgeCast (c.speedtest.net)? :P
That's awesome.
@klikli:
Thanks! Mind doing traceroute to s0.wp.com as well? :P
@klikli:
It's pretty fun that SoftLayer routes your IP by HKIX, considering you both have NTT.
Not at the moment unless there's any advantage in their routes. So far I have most locations covered so I rather focus on peering arrangements for better connectivity.
Peering with SL at HKIX directly, so should be shortest path. I don't peer at Equinix SG where SL is as well, still planning for that.