well have reported it and they have agreed there is a network problem
1 2 ms 2 ms 1 ms 192.168.2.1
2 5 ms 3 ms 2 ms 192.168.0.1
3 264 ms 231 ms 203 ms 10.23.48.1
4 159 ms 67 ms 359 ms oldh-t2cam1-a-v115.inet.ntl.com [80.5.164.61]
5 * 95 ms 64 ms mant-t2core-a-ge-wan62.inet.ntl.com [213.104.242
.41]
6 256 ms 60 ms 61 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
7 14 ms 9 ms 10 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 71 ms 65 ms 16 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
9 15 ms 19 ms 16 ms win-dc-a-v903.inet.ntl.com [213.105.174.34]
10 259 ms 17 ms 15 ms
www.ntlworld.com [62.253.162.30]
how do they know this because i can tracert to local ubr in under 10ms therefore its a network problem
1 1 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.0.1
3 9 ms 8 ms 13 ms spc1-roch1-6-0-gw.bagu.broadband.ntl.com [81.100
.143.1]