Does traceroute indicate where the packets are being lost?

In reply to a post by john2007:

Does traceroute indicate where the packets are being lost?

Ping statistics for 212.58.244.68:
Packets: Sent = 20, Received = 2, Lost = 18 (90% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 23ms, Average = 22ms

C:\Users\John>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.93]
over a maximum of 30 hops:

1 25 ms 99 ms 99 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * * 27 ms 10.1.3.214
5 * * 25 ms 10.1.2.158
6 * * 23 ms bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.103]
7 * * * Request timed out.
8 * * 24 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
9 23 ms 27 ms 24 ms 132.185.255.165
10 24 ms 24 ms 24 ms bbc-vip014.cwwtf.bbc.co.uk [212.58.246.93]

Trace complete.

My trace to bbc.co.uk just this minute completed:

traceroute to 212.58.241.131 (212.58.241.131), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 6.788 ms 5.296 ms 3.282 ms
2 * * *
3 * * *
4 * 10.1.2.158 (10.1.2.158) 20.096 ms 25.943 ms
5 bbc-gw1-linx.prt0.thdoe.bbc.co.uk (195.66.226.103) 19.154 ms 16.896 ms 19.953 ms
6 * * *
7 ae1.er01.rbsov.bbc.co.uk (132.185.254.46) 22.664 ms 17.130 ms 20.030 ms
8 132.185.255.134 (132.185.255.134) 20.186 ms 19.653 ms 19.578 ms
9 212.58.241.131 (212.58.241.131) 20.349 ms 19.302 ms 19.638 ms

Had problems with bbc iplayer content pausing to buffer for quite a while now. At times the programme I'm viewing will stop to buffer and not recover at all, so resetting back to the beginning. Had this issue since I don't know, maybe as far back as September '11?

BE support staff guy I spoke to a few weeks back, said there were no issues and that was that. It can be frustrating when you exhaust your routes of inquiry when you don't know what else to do. Now that I've become aware of seemingly a wider issue, then I'm hopeful BE will actually investigate it properly and hopefully fix it. I've made my first ever post to their support forum to the thread linked above so I hope that helps.

Just to add: surprisingly no packet loss or weird spiking just now when running ping test. 100 packets sent and received with good stable average of 20-23ms (now interleaved). For a long time now I've been getting a very regular high of between 70-100ms which affects about 3 - 5 packets out of every 100 and occurs with a regularity of about every hundred packets (modal average whilst on fastpath was 6 or 7ms). Tested this on several computers (2 windows and one mac). Today was the first time it didn't happen for a long while and I've been interleaved for several weeks since I called BE support so it's not that that's fixed anything. Just watched Click! and that was all right with no pauses at all though it is a short programme.

Strange goings on. Today the first hop will not respond when doing traceroute, I expect O2 have blocked this. My first hop is 93.96.162.1 (which is zone4 even though I have a zone9 IP?!)

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

1 98 ms 99 ms 99 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * 22 ms 22 ms 10.1.2.158
5 23 ms 22 ms * 195.66.226.103
6 * * * Request timed out.
7 23 ms 24 ms 23 ms 132.185.254.46
8 22 ms 23 ms 25 ms 132.185.255.134
9 * * * Request timed out.
10 21 ms 22 ms * 212.58.241.131
11 * * * Request timed out.
12 * * * Request timed out.
13 ^C

The first part of the bbc appears to be 195.66.226.103

What happens if you ping that address?

john@uranus:~$ ping 195.66.226.103
PING 195.66.226.103 (195.66.226.103) 56(84) bytes of data.
64 bytes from 195.66.226.103: icmp_req=1 ttl=60 time=16.8 ms
64 bytes from 195.66.226.103: icmp_req=2 ttl=60 time=16.1 ms
...
64 bytes from 195.66.226.103: icmp_req=19 ttl=60 time=16.1 ms
64 bytes from 195.66.226.103: icmp_req=20 ttl=60 time=16.3 ms
^C
--- 195.66.226.103 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19031ms
rtt min/avg/max/mdev = 15.943/16.291/16.849/0.294 ms

traceroute to bbc.net.uk (212.58.244.69), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 2.191 ms 5.040 ms 4.879 ms
2 * * *
3 * * *
4 * * *
5 bbc-gw1-linx.prt0.thdoe.bbc.co.uk (195.66.226.103) 22.080 ms 19.032 ms 19.650 ms
6 * * *
7 * * *
8 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 20.063 ms 19.143 ms 20.603 ms
9 132.185.255.148 (132.185.255.148) 20.023 ms 16.993 ms 22.958 ms
10 bbc-vip114.telhc.bbc.co.uk (212.58.244.69) 16.851 ms 16.625 ms 19.828 ms

That's not so good is it?

195.66.226.103 is still an IP that belongs to a range that is owned by Linx!?

Ping statistics for 195.66.226.103:
Packets: Sent = 35, Received = 0, Lost = 35 (100% loss),

132.185.254.93 belongs to the BBC

Ping statistics for 132.185.254.93:
Packets: Sent = 23, Received = 1, Lost = 22 (95% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 23ms, Average = 23ms

But to my mind it would seem to rule out the problem as at the BBC's end. I'm not a network guy but it would appear that your messages are being lost prior to reaching the BBC "network".

In reply to a post by john2007:

But to my mind it would seem to rule out the problem as at the BBC's end. I'm not a network guy but it would appear that your messages are being lost prior to reaching the BBC "network".

Of course it is not a problem with the BBC it never has been That's why i have tried to be a vocal in public about it, I haven't been able to load any content from I player for the past 2 days as there is packet loss from the be network 10.1.3.234 on every hop to the any BBC I P
And this Issue that is preventing some from accessing the bbc is also affecting Eurogamer.net,
Due to the fact that so far BE/O2 have been passing the blame on the bbc, just because the bbc where upgrading their infrastructure to better cope with the Olympics, and as a result only BE/O2 customers have been affected they seriously think that we all are so naive

This is my tracert


Tracing route to 212.58.241.131 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 10.100.10.1
2 * * * Request timed out.
3 * 31 ms 31 ms 10.1.2.5
4 * * * Request timed out.
5 * * 31 ms 10.1.2.158
6 31 ms 30 ms 30 ms bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.10
3]
7 * * * Request timed out.
8 31 ms 31 ms 31 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
9 31 ms 31 ms 30 ms 132.185.255.134
10 31 ms 31 ms 31 ms 212.58.241.131

And a separate ping

Pinging 212.58.241.131 with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=31ms TTL=245
Reply from 212.58.241.131: bytes=32 time=30ms TTL=245
Reply from 212.58.241.131: bytes=32 time=30ms TTL=245
Reply from 212.58.241.131: bytes=32 time=30ms TTL=245

Ping statistics for 212.58.241.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 31ms, Average = 30ms

But I don't get any problem with iPlayer at all, although I get timeouts too. Wouldn't the timeouts occur if the router involved was set not to respond to pings ? When you ping my external IP there's no response but that doesn't mean it's not working