works fine from here:
Code:
Tracing route to newswww.bbc.net.uk [212.58.226.20]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms efw-1209668945.localdomain [192.168.200
2 9 ms 6 ms 6 ms 10.225.80.1
3 8 ms 7 ms 7 ms nott-t2cam1-a-v107.inet.ntl.com [81.109
4 11 ms 7 ms 7 ms nott-t3core-1a-ge-013-0.inet.ntl.com [1
4.217]
5 10 ms 9 ms 12 ms lee-bb-a-as0-0.inet.ntl.com [213.105.17
6 13 ms 13 ms 14 ms pop-bb-b-as1-0.inet.ntl.com [62.253.185
7 16 ms 14 ms 14 ms tele-ic-2-as0-0.inet.ntl.com [62.253.18
8 18 ms 14 ms * ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.2
9 14 ms 15 ms 13 ms 212.58.238.153
10 16 ms 14 ms 14 ms newslb11.thdo.bbc.co.uk [212.58.226.20]
ping works on icmp echo requests, so that, and the fact my tracert works suggests that't not the problem.
ICMP does have lower prority than TCP/UDP traffic though, so the router could be dropping the ICMP packets if it's "a bit busy".