QUOTE(jjj2 @ Jan 3 2014, 11:41 AM)
Hi Bro,
I dont think Starhub actually owning the node as it most probably under peering policy between the ISPs with Sparkle Telekom Italia.
Can you try to post the trace route results here instead of linking to another forum, I think it's not allowed.
If you are connecting to SEA server, it should be direct to SG as Time has 2 interconnection via Tuas & Woodlands to SG Global IX. Latency should be around 20-50ms depending on location.
Thanks.
Yeah that's what Starhub informed me and asked that I get in touch with my own ISP to have them take action. I just sent another email to wecare@astro.com.my yesterday (3rd email I have sent regarding this issue) but it's still not resolved.
Here's the trace route result for 2nd Jan
» Click to show Spoiler - click again to hide... «
and today's result.
» Click to show Spoiler - click again to hide... «
I have never gotten 30-50ms pings on SEA servers ever since I switched to TIME. It has always been constant 70-80ms which I felt was odd since we are like next to each other. The last time I ever got pings below 50ms was when I was on Unifi.
EDIT: My first email sent regarding this issue was 23rd December 2013 to TIME's customer service email. The trace route result then was slightly different as there was an additional hop that routed the traffic to Japan before making it's way back to Singapore. Here's the trace route result which I copy and pasted in the email I sent.
» Click to show Spoiler - click again to hide... «
1 4 ms 2 ms 3 ms 192.168.1.1
2 6 ms 5 ms 3 ms lo-0.ag-01-glsfb.ni.time.net.my [223.28.0.216]
3 3 ms 3 ms 3 ms xe-5-3-0-0.er-01-glsfb.ni.time.net.my [223.28.2.37]
4 9 ms 16 ms 13 ms xe-0-1-0-0.cr-02-glsfb.ni.time.net.my [223.28.2.1]
5 13 ms 10 ms 17 ms ae-0-0.br-01-mciwg.ni.time.net.my [223.28.2.122]
6 8 ms 8 ms 12 ms 124.158.226.149
7 12 ms 9 ms 9 ms ae-4.cr-gw-2-sin-pip.sg.globaltransit.net [124.158.224.98]
8 12 ms 16 ms 8 ms ae-2.br-gw-1-sin-pip.sg.globaltransit.net [124.158.224.190]
9 9 ms 9 ms 9 ms xe-0-6-0-7.r00.sngpsi02.sg.bb.gin.ntt.net [116.51.17.185]
10 12 ms 19 ms 12 ms ae-1.r21.sngpsi02.sg.bb.gin.ntt.net [129.250.6.104]
11 120 ms 84 ms 82 ms as-1.r22.tokyjp01.jp.bb.gin.ntt.net [129.250.5.20]
12 284 ms 282 ms 291 ms p16-5-3-3.r22.tokyjp01.jp.ce.gin.ntt.net [61.120.145.146]
13 308 ms 286 ms 287 ms vlan905-an-cat6k-ts1-r1.starhub.net.sg [203.118.3.151]
14 283 ms 288 ms 284 ms 203.118.7.241
15 257 ms 257 ms 264 ms 203.117.6.54
16 276 ms 274 ms 280 ms d117155133.ppp117155.cyberway.com.sg [203.117.155.133]
It was then on around Christmas day that the routing was changed directly to Singapore but through the Seabone node.
This post has been edited by loafer: Jan 3 2014, 12:18 PM