ISP Network Problem

[SpicyBird]

I does a tracert to a aws IP address and noticed that on the 10th hops it start to have latency. I've checked DNS whois (http://wq.apnic.net/static/search.html) on that IP and found that is singnet entity in telepark. What can I do about it?

 

[SpicyBird]

Can we like change the router route table to skip this hop?

 

[Henry Ng]

I does a tracert to a aws IP address and noticed that on the 10th hops it start to have latency. I've checked DNS whois (http://wq.apnic.net/static/search.html) on that IP and found that is singnet entity in telepark. What can I do about it?

Nothing much a home user can do. Why are you doing this tracert? What is the issue with your internet?
Must report to ISP and see whether it can help or not?

 

[SpicyBird]

I noticed there's latency connecting to us server do i do a tracert to see where is the bottleneck. Found out that it's ISP problem.

 

[cyberet]

i doubt ST will entertain route optimisation unless theres connectivity issues..

 

[Henry Ng]

i doubt ST will entertain route optimisation unless theres connectivity issues..

Not just ST will not entertain, other ISP will also be the same unless there is connection issues.

 

[ksw2010]

I does a tracert to a aws IP address and noticed that on the 10th hops it start to have latency. I've checked DNS whois (http://wq.apnic.net/static/search.html) on that IP and found that is singnet entity in telepark. What can I do about it?

It is likely hop#10 from your tracert seems to be their oversea POP (USA) where hop#12 maybe a ST peering in USA LAX? if it is the case, the latency from Singapore to USA for most of SG ISPs will be ~180-250ms (from my experience) depend on the US end host location. The latency might due to geographical distance between SG-US where it has to travel through the subsea cable from SG - USA, as you cannot request a latency value similar to local SG latency for a host in USA. For IP location database, it might not be always reflected accuracy as the ISP may register the location for their whole IP supernet in their APNIC but they can use smaller IP ranges somewhere if they have oversea equipment. Better check with ST as well.

 

[Henry Ng]

He can check but look like it is the distance from USA and there may be some issue with the IP address and not ISP. It is hard for user to proof it is ISP fault. Quite sure ISP will have their own story.

It is likely hop#10 from your tracert seems to be their oversea POP (USA) where hop#12 maybe a ST peering in USA LAX? if it is the case, the latency from Singapore to USA for most of SG ISPs will be ~180-250ms (from my experience) depend on the US end host location. The latency might due to geographical distance between SG-US where it has to travel through the subsea cable from SG - USA, as you cannot request a latency value similar to local SG latency for a host in USA. For IP location database, it might not be always reflected accuracy as the ISP may register the location for their whole IP supernet in their APNIC but they can use smaller IP ranges somewhere if they have oversea equipment. Better check with ST as well.