Quote:
|
Originally Posted by Wolf
again i am told that i must contact CW corporate side.
|
I think what might be happening is this. You are showing NTL a traceroute that shows high RTTs from cw.net routers. It is not NTL's responsibility to fix problems in other ISPs' networks, so they are advising you to contact the other ISP directly. This is not unreasonable: NTL cannot be responsible for defects in cw.net. My guess is that almost all other ISPs would take a similar attitude.
However, on the basis of the traceroutes you posted earlier in this thread, the first hop with problems is the peering hop between ntl.com and cw.net. Therefore, there is a possibility that the problem lies with the NTL peering router or the connection between the last ntl.com router and the first cw.net router. I do not know what tests that you or NTL have done to eliminate this possibility.
There is another possibility, which is masked by the fact that traceroutes only show the outward route for probes, not the return route. It is possible that cw.net is sending traffic destined for ntl.com via the USA: you would see no evidence of this on tracerotues from your NTL connection. What you need to do is to perform a traceroute
from a server on cw.net
to your own PC back on ntl.com, and observe what route that traceroute takes. If it goes via the USA, then this
is a cw.net routing problem, and NTL are correct that cw.net are the only people who can fix this.
I hope this all makes sense.