i just trace to it & to be honest the NTL side looks ok
Tracing route to
www.novalogic.co.uk [38.144.95.66]
over a maximum of 30 hops:
1 16 ms 13 ms 9 ms 10.***.71.***
2 9 ms 8 ms 23 ms swan-t2cam1-b-v105.inet.ntl.com [80.0.254.149]
3 10 ms 10 ms 10 ms swan-t2core-b-ge-wan62.inet.ntl.com [213.105.225
.149]
4 15 ms 13 ms 15 ms win-bb-b-so-220-0.inet.ntl.com [62.253.187.241]
5 14 ms 11 ms 12 ms bre-bb-a-so-100-0.inet.ntl.com [62.253.185.197]
6 15 ms 18 ms 14 ms redb-ic-1-so-010-0.inet.ntl.com [62.253.188.106]
7 45 ms 35 ms 32 ms 195.66.224.185
8 95 ms 93 ms 91 ms p6-0.core02.jfk01.atlas.cogentco.com [154.54.1.5
]
9 90 ms 88 ms 90 ms p12-0.core02.jfk02.atlas.cogentco.com [66.28.4.1
69]
10 90 ms 88 ms 88 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.1
3]
11 97 ms 95 ms 96 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81
]
12 109 ms 106 ms 109 ms p14-0.core01.atl01.atlas.cogentco.com [66.28.4.1
61]
13 129 ms 161 ms 134 ms p14-0.core01.mco01.atlas.cogentco.com [66.28.4.1
53]
14 124 ms 155 ms 121 ms p14-0.core01.tpa01.atlas.cogentco.com [66.28.4.1
42]
15 134 ms 131 ms 130 ms p5-0.core01.iah01.atlas.cogentco.com [66.28.4.45
]
16 169 ms 166 ms 166 ms p14-0.core01.san01.atlas.cogentco.com [66.28.4.6
]
17 173 ms 171 ms 171 ms p6-0.core01.lax02.atlas.cogentco.com [66.28.4.23
0]
18 170 ms 168 ms 167 ms 204.6.150.242
19 167 ms 171 ms 171 ms 38.144.95.66
Trace complete.
ive hightlighted where the main jumps are & there off the NTL network
Can you post back with a trace route from your NTL connection & your BT connection if possible?