[IanUK]

I think I may have found the problem:

Traces show a new entry that I haven't seen before that is losing upto 100% of packets:

Tracing route to news.easynews.com [140.99.99.130]
over a maximum of 30 hops:
1 6 ms 6 ms 10 ms 10.82.176.1
2 6 ms 5 ms 18 ms wapk-t2cam1-b-ge-wan41-112.inet.ntl.com [80.1.17
0.185]
3 * 7 ms * popl-t2core-b-ge-wan61.inet.ntl.com [62.255.81.1
41]
4 9 ms 7 ms 7 ms popl-t2core-a-ge-wan61.inet.ntl.com [62.255.81.1
3]
5 7 ms 8 ms 7 ms pop-bb-a-so-320-0.inet.ntl.com [62.253.185.65]
6 7 ms 7 ms 7 ms so-7-0.hsa2.London1.Level3.net [212.113.14.129]
7 9 ms 7 ms 7 ms so-4-0-0.mp1.London1.Level3.net [212.187.131.121
]
8 9 ms 8 ms 9 ms so-3-0-0.mp1.London2.Level3.net [212.187.128.46]
9 80 ms 80 ms 82 ms as-0-0.bbr2.Washington1.Level3.net [4.68.128.102
]
10 136 ms 137 ms 136 ms so-0-0-0.mp1.Phoenix1.Level3.net [64.159.3.213]
11 137 ms 136 ms 136 ms so-10-0.hsa1.Phoenix1.Level3.net [4.68.113.242]
12 145 ms 147 ms 146 ms news.easynews.com [140.99.99.130]
Trace complete.

The new entry is number 3 (popl-t2core-b-ge-wan61.inet.ntl.com ) above, its also showing in some other traces, packet loss is running at 50 to 100% - who should I report this to ?

cheers

Ian