Update on the ongoing BBC and Eurogamer.net issues

As no one seems to be complaining about the network issues that still persist, it will be some 3weeks tomorrow (Friday) exactly ,from almost constantly monitoring , i can see that certain peering links and bbc links have been swapped back and forth presumably by the bbc, this has stopped the packet loss almost completely but only for a short time today no packet loss up until 12 noon this ceased at around 14:30, and re started again at 16:00, and is at high enough levels to cause both slow loading of pages and interruptions to streaming more so the live streaming
And once again just like the last time that i highlighted the fact that the other affected site was Eurogamer.net both replicate the same packet loss issue
I know that both use different carriers /peering for transit once outside the BE/O2 network,

But that BE/O2 network is the only common denominator between the 2 of them therefore this problem lies within the BE/O2 network it is so obvious to some of us,but it's like banging your head against a brick wall , and the problem has probably been made a lot worse to locate,by all those who spoofed their routers H/W MAC address,

Thats assuming that anyone is or actually has been checking on the whole of the be /o2 infrastructure in a bid to find the root cause , they can change the 3rd party links all day but it will not make any difference to this prevailing issue that is able to cause problems of this magnitude to two completely different locations that are known about they could be more affected by this , that is not scaremongering either,

I'm seeing exactly the same thing on my O2 connection, however this evening it seems more widespread. I'm seeing packet loss to other sites as well:
www.pingplotter.com 33%
www.download.com 50%
bbc.co.uk 50%
eurogamer.net 50%
sun.com 50%

Anyone else seeing this?

In reply to a post by MarkS:

I'm seeing exactly the same thing on my O2 connection, however this evening it seems more widespread. I'm seeing packet loss to other sites as well:
www.pingplotter.com 33%
www.download.com 50%
bbc.co.uk 50%
eurogamer.net 50%
sun.com 50%

Anyone else seeing this?

To 64.30.224.118 phx1-sha-redirect-lb.cnet.com (download.com) 1-2% on 3 of the hops on the outside networks but none at the final hop,so isn't an issue
(Pingplotter.com ) 216.92.151.75 shows no packet loss either, Sun.com
137.254.16.113 bigip-www-legacy-sun-cms-adc.oracle.com ( is that for Java ?) also shows no packet loss for me
Whilst its around 20% to both bbc and Eurogamer.net currently for me ,

64.30.224.118 phx1-sha-redirect-lb.cnet.com (download.com) Now showing 62.5% at destination with between 30% and 77% on most of the hops
216.92.151.75 (Pingplotter.com) showing 50% at destination with about the same on 2 of the outside hops
137.254.16.113 (bigip-www-legacy-sun-cms-adc.oracle.com) 40% at destination and between 33% and 90% on the other hops
212.58.241.131 (bbc.co.uk) 43% at destination and 10% to 40% on 3 of the outside hops

Bad as ever again tonight.


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

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

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

1 11 ms 99 ms 99 ms 192.168.1.254
2 * * * Request timed out.
3 16 ms 16 ms 16 ms 10.1.3.234
4 * * * Request timed out.
5 21 ms 21 ms 74 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
6 * * * Request timed out.
7 22 ms * 22 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
8 22 ms 21 ms 22 ms 132.185.255.134
9 22 ms 22 ms 22 ms 212.58.241.131

Trace complete.

In reply to a post by John_ON:

Bad as ever again tonight.


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

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

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

1 11 ms 99 ms 99 ms 192.168.1.254
2 * * * Request timed out.
3 16 ms 16 ms 16 ms 10.1.3.234
4 * * * Request timed out.
5 21 ms 21 ms 74 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
6 * * * Request timed out.
7 22 ms * 22 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
8 22 ms 21 ms 22 ms 132.185.255.134
9 22 ms 22 ms 22 ms 212.58.241.131

Trace complete.

Well they made it into todays Web user mag, page 9 i believe it's on, maybe now a few others will pick up on it too , then they might just get their asses in to gear

In reply to a post by John_ON:

Bad as ever again tonight.


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

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

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

1 11 ms 99 ms 99 ms 192.168.1.254
2 * * * Request timed out.
3 16 ms 16 ms 16 ms 10.1.3.234
4 * * * Request timed out.
5 21 ms 21 ms 74 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
6 * * * Request timed out.
7 22 ms * 22 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
8 22 ms 21 ms 22 ms 132.185.255.134
9 22 ms 22 ms 22 ms 212.58.241.131

Trace complete.

Hmmm,

Pings don't work but tracert does...

I wonder why.

In reply to a post by IanBB:

In reply to a post by John_ON:

Bad as ever again tonight.


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

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

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

1 11 ms 99 ms 99 ms 192.168.1.254
2 * * * Request timed out.
3 16 ms 16 ms 16 ms 10.1.3.234
4 * * * Request timed out.
5 21 ms 21 ms 74 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
6 * * * Request timed out.
7 22 ms * 22 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
8 22 ms 21 ms 22 ms 132.185.255.134
9 22 ms 22 ms 22 ms 212.58.241.131

Trace complete.

Hmmm,

Pings don't work but tracert does...

I wonder why.

I can ping and tracert without issue to the bbc( bbc.co.uk 212.58.241.131) but i did notice there are 2 different ip's for bbc.net.uk i have both running in pingplotter
212.58.246.91 (bbc-vip012.cwwtf.bbc.co.uk)
212.58.246.95 (bbc-vip016.cwwtf.bbc.co.uk)

But there is packet loss on both surprise surprise,not

Both the official communication( or lack of it ) and handling of this or the many problems has been abysmal

Post deleted by IanBB

In reply to a post by IanBB:

In reply to a post by John_ON:

Bad as ever again tonight.


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

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

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

1 11 ms 99 ms 99 ms 192.168.1.254
2 * * * Request timed out.
3 16 ms 16 ms 16 ms 10.1.3.234
4 * * * Request timed out.
5 21 ms 21 ms 74 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
6 * * * Request timed out.
7 22 ms * 22 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
8 22 ms 21 ms 22 ms 132.185.255.134
9 22 ms 22 ms 22 ms 212.58.241.131

Trace complete.

Hmmm,

Pings don't work but tracert does...

I wonder why.

Pings do work. That just happened to be a 100%'er. This morning......


Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=22ms TTL=245
Request timed out.
Request timed out.
Request timed out.

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