[Chrysalis]

Ok I will address the savvis bit first. You will see one of the traceroutes to myself I pasted is not over savvis at all that one was from justedge it hit tiscali, which it then used all the way to ntlworld.com but to me it went to level3 then to me taking a longer route.

sagonet which I didnt paste is just level3 all the way.

the trace to you from lt is as I expected over opentransit, every single ntl ip I have tested except me and one other guy uses opentransit. Also it is only 120ms to your ubr so I think your problems are on of the 3.

1 - your ubr is causing an extra 80ms lag (very over subscribed) but this isnt likely I think.
2 - your LT switch is faulty or saturated try asking to be moved.
3 - your LT server has a problem.

I think number 2 is most likely since you say everyone has the problem, whilst in my case only 2 of us out of about 20 people I have had testing have problems. I also get on non savvis routes.

Here is the trace to you excluding last hop of course.

traceroute to m3ezw.no-ip.com (82.9.140.38), 64 hops max, 60 byte packets
1 41.25.232.72.reverse.layeredtech.com (72.232.25.41) 0.626 ms 0.576 ms 0.578 ms
2 * * *
3 216.39.79.217 (216.39.79.217) 0.597 ms 0.572 ms 0.564 ms
4 ohr2-ge-0-1.FortWorthda1.savvis.net (216.39.64.41) 0.720 ms 0.570 ms 0.563 ms
5 bcs2-so-3-2-0.Dallas.savvis.net (208.172.131.85) 1.825 ms 1.662 ms 1.654 ms
6 dcr2-so-6-0-0.Atlanta.savvis.net (204.70.192.69) 21.939 ms 22.108 ms 21.782 ms
7 bcs2-so-1-2-0.Washington.savvis.net (204.70.192.62) 35.354 ms 37.390 ms 35.509 ms
8 bcs2-so-2-0-0.NewYork.savvis.net (204.70.192.2) 39.566 ms 39.418 ms 39.566 ms
9 P5-0.NYKCR2.New-york.opentransit.net (206.24.207.30) 39.566 ms 39.419 ms 39.411 ms
10 po10-0.nykcr3.NewYork.opentransit.net (193.251.241.114) 39.567 ms 39.730 ms 39.254 ms
11 po4-0.loncr3.London.opentransit.net (193.251.243.22) 110.549 ms 110.401 ms 110.239 ms
12 po0-0.brsbb1.Bristol.opentransit.net (193.251.243.38) 113.981 ms 113.984 ms 114.133 ms
13 ntl.GW.opentransit.net (193.251.254.146) 115.850 ms 115.941 ms 115.899 ms
14 pop-bb-a-so-010-0.inet.ntl.com (62.253.185.201) 114.136 ms 113.830 ms 113.823 ms
15 nth-bb-b-so-400-0.inet.ntl.com (213.105.172.13) 115.695 ms 115.865 ms 116.008 ms
16 lee-bb-a-so-600-0.inet.ntl.com (62.253.185.102) 120.543 ms 120.534 ms 120.701 ms
17 midd-t2core-a-pos31.inet.ntl.com (62.253.187.90) 122.117 ms 122.424 ms 122.251 ms
18 midd-t2cam1-a-ge-wan31.inet.ntl.com (213.106.237.34) 122.406 ms 122.098 ms 122.092 ms
19 midd-midd-ubr-2-ge10.inet.ntl.com (213.106.238.26) 125.836 ms 126.004 ms 125.835 ms

---------- Post added at 15:29 ---------- Previous post was at 15:23 ----------

justedge to you, also different.

traceroute to m3ezw.no-ip.com (82.9.140.38), 64 hops max, 60 byte packets
1 colo-03-teb (64.18.131.129) 0.483 ms 0.285 ms 0.233 ms
2 core-01-teb (64.18.128.1) 14.351 ms 0.458 ms 0.610 ms
3 core-01-lga.njiix.net (64.20.32.173) 0.611 ms 0.461 ms 0.611 ms
4 ge-2-1-7-0.nyc33.ip.tiscali.net (213.200.66.221) 0.609 ms 0.584 ms 0.611 ms
5 so-0-1-0.lon11.ip.tiscali.net (213.200.80.29) 68.452 ms 68.547 ms 68.455 ms
6 so7-3-0.LONCR1.London.opentransit.net (213.200.77.54) 68.565 ms 68.547 ms 68.568 ms
7 po12-0.loncr3.London.opentransit.net (193.251.242.169) 73.820 ms 73.792 ms 73.823 ms
8 po0-0.brsbb1.Bristol.opentransit.net (193.251.243.38) 77.321 ms 77.170 ms 77.195 ms
9 ntl.GW.opentransit.net (193.251.254.146) 74.072 ms 74.172 ms 74.073 ms
10 pop-bb-a-so-010-0.inet.ntl.com (62.253.185.201) 76.189 ms 76.168 ms 76.069 ms
11 nth-bb-b-so-400-0.inet.ntl.com (213.105.172.13) 76.197 ms 76.171 ms 76.197 ms
12 lee-bb-a-so-600-0.inet.ntl.com (62.253.185.102) 79.317 ms 79.294 ms 79.320 ms
13 midd-t2core-a-pos31.inet.ntl.com (62.253.187.90) 81.069 ms 81.036 ms 80.943 ms
14 midd-t2cam1-a-ge-wan33.inet.ntl.com (213.106.237.46) 81.063 ms 81.037 ms 80.944 ms
15 midd-midd-ubr-2-ge10.inet.ntl.com (213.106.238.26) 81.194 ms 81.414 ms 81.442 ms

I find it very odd that every ip I trace on ntl uses what appears to be bgp but I am routed over level3 or cogent everytime.