Ok me and some friend's noticed 2 of us on ntl were getting lag and slow speeds from the .us and and the others also on ntl were fine. So I did some traceroute's from some servers and noticed more priority routing going on with ntl.
it appears the only routes to my connection from america are level3 and cogent both which are performing poorly. Yet when I do traceroutes to
www.ntlworld.com and to some ntl connections, backbones from cable & wireless, opentransit and tiscali are used so ntl have other peering routes. I am wondering since I live in a student area which will have high traffic utilisation are ntl sticking the traffic from my ip range onto cheaper transit.
1 41.25.232.72.reverse.layeredtech.com (72.232.25.41) 0.620 ms 0.582 ms 0.561 ms
2 10.1.6.9 (10.1.6.9) 0.716 ms 0.720 ms 0.713 ms
3 216.39.79.213 (216.39.79.213) 0.726 ms 0.564 ms 0.715 ms
4 ohr1-ge-0-1.FortWorthda1.savvis.net (216.39.64.33) 0.714 ms 0.563 ms 0.729 ms
5 bcs2-so-1-2-0.Dallas.savvis.net (208.172.129.229) 1.650 ms 2.143 ms 1.498 ms
6 dcr2-so-6-0-0.Atlanta.savvis.net (204.70.192.69) 21.777 ms 21.781 ms 21.775 ms
7 bcs2-so-6-3-0.Washington.savvis.net (204.70.192.66) 34.880 ms 34.888 ms 35.038 ms
8 cable-and-wireless-americas-operations.Washington.savvis.net (206.24.238.18) 35.194 ms 35.042 ms 35.050 ms
9 so-7-0-0-dcr1.nyk.cw.net (195.2.3.2) 40.396 ms 40.347 ms 40.185 ms
10 so-2-0-0-dcr2.tsd.cw.net (195.2.10.110) 115.381 ms 115.385 ms 115.405 ms
11 so-5-0-0-bcr1.tsd.cw.net (195.2.10.61) 115.700 ms 115.574 ms 115.557 ms
12 ntl1.tsd.cw.net (166.63.211.150) 116.786 ms 116.790 ms 116.784 ms
13 nth-bb-a-so-000-0.inet.ntl.com (62.253.185.97) 116.163 ms 116.039 ms 116.033 ms
14 bir-bb-b-so-200-0.inet.ntl.com (62.253.185.106) 117.894 ms 118.052 ms 118.070 ms
15 brhm-t2core-b-pos31.inet.ntl.com (62.253.185.150) 118.191 ms 118.991 ms 118.067 ms
16 brhm-t2cam1-b-ge-wan33.inet.ntl.com (213.106.231.190) 117.880 ms 117.885 ms 118.033 ms
17 brhm-warw-ubr-6-ge20.inet.ntl.com (213.106.228.214) 125.521 ms 125.263 ms 125.098 ms
18 cpc3-warw6-0-0-cust940.brhm.cable.ntl.com (86.20.247.173) 129.734 ms 126.201 ms 128.022 ms
1 41.25.232.72.reverse.layeredtech.com (72.232.25.41) 0.593 ms 0.571 ms 0.558 ms
2 10.1.6.13 (10.1.6.13) 0.714 ms 0.735 ms 0.559 ms
3 216.39.66.29 (216.39.66.29) 0.558 ms 0.720 ms 0.717 ms
4 216.39.64.17 (216.39.64.17) 0.713 ms 0.563 ms 0.559 ms
5 bcs2-so-1-2-0.Dallas.savvis.net (208.172.129.229) 1.495 ms 1.538 ms 1.656 ms
6 dcr2-so-6-0-0.Atlanta.savvis.net (204.70.192.69) 21.777 ms 21.794 ms 21.777 ms
7 bcs2-so-6-3-0.Washington.savvis.net (204.70.192.66) 35.037 ms 35.045 ms 35.039 ms
8 cable-and-wireless-americas-operations.Washington.savvis.net (206.24.238.18) 35.038 ms 35.046 ms 37.532 ms
9 so-7-0-0-dcr1.nyk.cw.net (195.2.3.2) 39.728 ms 39.722 ms 39.737 ms
10 so-2-0-0-dcr2.tsd.cw.net (195.2.10.110) 115.732 ms 115.787 ms 115.910 ms
11 so-5-0-0-bcr1.tsd.cw.net (195.2.10.61) 115.540 ms 115.545 ms 115.538 ms
12 ntl1.tsd.cw.net (166.63.211.150) 117.101 ms 117.259 ms 117.148 ms
13 win-bb-a-so-500-0.inet.ntl.com (213.105.172.129) 121.508 ms 121.633 ms 121.310 ms
14 win-dc-a-v903.inet.ntl.com (213.105.174.34) 121.479 ms 121.368 ms 121.483 ms
both of those using c&w
and trace to me
1 41.25.232.72.reverse.layeredtech.com (72.232.25.41) 0.477 ms 0.581 ms 0.560 ms
2 10.1.6.13 (10.1.6.13) 0.720 ms 0.564 ms 0.558 ms
3 216.39.79.217 (216.39.79.217) 6.955 ms 0.564 ms 0.559 ms
4 ohr1-ge-0-1.FortWorthda1.savvis.net (216.39.64.33) 0.559 ms 0.721 ms 0.557 ms
5 bcs1-so-3-3-0.Dallas.savvis.net (208.172.131.81) 4.304 ms 36.135 ms 1.808 ms
6 bcs2-so-6-0-0.Dallas.savvis.net (204.70.192.50) 2.121 ms 1.811 ms 1.805 ms
7 dcr2-so-6-0-0.Atlanta.savvis.net (204.70.192.69) 22.089 ms 21.957 ms 21.778 ms
8 bcs2-so-1-1-0.Washington.savvis.net (204.70.192.58) 35.350 ms 47.565 ms 81.063 ms
9 bcs2-so-2-0-0.NewYork.savvis.net (204.70.192.2) 39.874 ms 40.037 ms 39.874 ms
10 bcs1-so-0-0-0.Londonlnx.savvis.net (204.70.192.122) 109.611 ms 109.613 ms 109.629 ms
11 bcr1-so-0-0-0.Londonlnx.savvis.net (204.70.193.113) 109.671 ms 111.334 ms 109.772 ms
12 so-8-2.core2.London1.Level3.net (206.24.169.30) 109.787 ms 109.932 ms 109.767 ms
13 ae-0-55.bbr1.London1.Level3.net (4.68.116.129) 110.234 ms 109.926 ms 110.077 ms
14 ae-1-0.bbr1.London2.Level3.net (212.187.128.46) 110.388 ms 109.968 ms 110.079 ms
15 ge-3-0-0.gar1.London2.Level3.net (4.68.124.62) 110.234 ms 110.240 ms 110.253 ms
16 195.50.91.130 (195.50.91.130) 110.270 ms 110.560 ms 110.568 ms
17 ren-bb-a-so-100-0.inet.ntl.com (62.253.185.165) 121.779 ms 121.630 ms 121.779 ms
18 lee-bb-b-so-600-0.inet.ntl.com (62.253.185.162) 141.481 ms 123.073 ms 150.174 ms
19 lee-bb-a-ae0-0.inet.ntl.com (62.253.187.185) 122.870 ms 123.081 ms 123.030 ms
20 leic-t2core-a-so-000-0.inet.ntl.com (62.253.188.109) 125.216 ms 124.942 ms 125.992 ms
21 leic-t2cam1-a-ge-wan32.inet.ntl.com (82.3.33.9) 125.210 ms 125.061 ms 125.369 ms
22 leic-leic-ubr-8-ge01.inet.ntl.com (82.3.35.150) 125.710 ms 125.270 ms 125.368 ms
my outgoing trace again is crazy, the other's not locked onto level3/cogent go direct to london and out via a shorter route I go to manchester to level3 and then down to london level3 and finally handed over to savvis.
I get the same results with 3 different us isp's and servers and the same sorts of performance differences.
---------- Post added at 18:45 ---------- Previous post was at 18:43 ----------
another
1 colo-03-teb (64.18.131.129) 0.406 ms 0.230 ms 0.236 ms
2 core-01-teb (64.18.128.1) 65.484 ms * 67.582 ms
3 core-01-lga.njiix.net (64.20.32.173) 4.549 ms 0.669 ms 0.583 ms
4 ge-2-1-7-0.nyc33.ip.tiscali.net (213.200.66.221) 0.600 ms 0.555 ms 0.619 ms
5 * * *
6 ntl-gw.ip.tiscali.net (213.200.77.18) 79.218 ms 70.777 ms 82.045 ms
7 pop-bb-b-so-500-0.inet.ntl.com (62.253.184.5) 71.023 ms 70.920 ms 70.931 ms
8 lee-bb-a-so-700-0.inet.ntl.com (62.253.185.237) 76.523 ms 76.398 ms 76.404 ms
9 nth-bb-b-so-000-0.inet.ntl.com (62.253.185.101) 76.424 ms 76.402 ms 76.424 ms
10 pop-bb-a-so-100-0.inet.ntl.com (213.105.172.14) 78.374 ms 78.421 ms 78.518 ms
11 win-bb-b-so-500-0.inet.ntl.com (62.253.185.202) 134.885 ms 78.541 ms 78.660 ms
12 win-dc-b-v900.inet.ntl.com (62.253.188.166) 77.899 ms 77.904 ms 77.945 ms
to me
traceroute to 82.21.24.163 (82.21.24.163), 64 hops max, 40 byte packets
1 colo-03-teb (64.18.131.129) 0.313 ms 0.228 ms 0.218 ms
2 core-01-teb (64.18.128.1) 32.640 ms 3.309 ms 1.417 ms
3 core-01-lga.njiix.net (64.20.32.173) 0.612 ms 0.642 ms 0.586 ms
4 ge-2-1-7-0.nyc33.ip.tiscali.net (213.200.66.221) 0.596 ms 0.546 ms 0.594 ms
5 ge-7-11.car2.NewYork1.Level3.net (213.200.66.210) 0.851 ms 0.678 ms
ge-7-12.car2.NewYork1.Level3.net (213.200.66.214) 0.714 ms
6 ae-1-53.bbr1.NewYork1.Level3.net (4.68.97.65) 1.033 ms
ae-1-55.bbr1.NewYork1.Level3.net (4.68.97.129) 10.280 ms 1.010 ms
7 ae-1-0.bbr1.London2.Level3.net (212.187.128.46) 68.666 ms 68.604 ms 68.799 ms
8 ge-3-0-0.gar1.London2.Level3.net (4.68.124.62) 68.791 ms 68.855 ms 68.689 ms
9 195.50.91.130 (195.50.91.130) 69.282 ms 118.991 ms 69.383 ms
10 ren-bb-a-so-100-0.inet.ntl.com (62.253.185.165) 80.659 ms 80.484 ms 80.640 ms
11 lee-bb-b-so-600-0.inet.ntl.com (62.253.185.162) 100.646 ms 80.230 ms 80.281 ms
12 lee-bb-a-ae0-0.inet.ntl.com (62.253.187.185) 80.406 ms 197.414 ms 80.409 ms
13 leic-t2core-a-so-000-0.inet.ntl.com (62.253.188.109) 82.665 ms 82.598 ms 82.799 ms
14 leic-t2cam1-a-ge-wan31.inet.ntl.com (82.3.33.5) 82.657 ms 82.733 ms 83.660 ms
15 leic-leic-ubr-8-ge01.inet.ntl.com (82.3.35.150) 83.163 ms 83.117 ms 83.301 ms