BBC pings

Has the bbc blocked pings to bbc.co.uk? Been working fine for years. Anyone confirm?

Yea wont ping for me either

Can't blame them really.

Working outside the UK still:

$ ping bbc.co.uk
PING www.bbc.co.uk (46.23.67.190): 56 data bytes
64 bytes from 46.23.67.190: icmp_seq=0 ttl=47 time=41.254 ms
64 bytes from 46.23.67.190: icmp_seq=1 ttl=49 time=60.507 ms
64 bytes from 46.23.67.190: icmp_seq=2 ttl=47 time=37.930 ms
64 bytes from 46.23.67.190: icmp_seq=3 ttl=47 time=57.145 ms
64 bytes from 46.23.67.190: icmp_seq=4 ttl=47 time=40.537 ms

Whether its linked to the apparent DDOS attack that happened recently who knows. maybe they just blocked any unwanted traffic

Edited by bobble_bob (Mon 11-Jan-16 21:44:12)

That's not their actual network though.

46.23.67.190 belongs to UK2. Going by the content on 46.23.67.190, it is some kind of proxy to view BBC content out of the country and it's getting redirected there so not actually the BBC network or servers.

BBC's own IP space does not seem to respond currently.

Matt

Edited by uno (Mon 11-Jan-16 22:00:49)

In reply to a post by Banger:

Has the bbc blocked pings to bbc.co.uk? Been working fine for years. Anyone confirm?

The Beeb was getting DDoS'd last night. To try and defend against this they've been using a bunch of content delivery networks, alongside using DDoS protection services which have ended up with pings being blocked.

I've seen Verisign and Akamai being used so far. Little point in them responding to pings if traffic is being diverted elsewhere to be scrubbed, misleading result.

traceroute to www.bbc.co.uk (212.58.246.90), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.268 ms 0.344 ms 0.412 ms
2 host-62-24-255-10.as13285.net (62.24.255.10) 5.333 ms 5.469 ms 5.524 ms
3 xe-11-2-0-bragg001.bre.as13285.net (78.151.225.39) 6.707 ms 7.137 ms 7.300 ms
4 host-78-151-225-18.static.as13285.net (78.151.225.18) 7.347 ms host-78-151-229-56.as13285.net (78.151.229.56) 14.041 ms 14.080 ms
5 host-78-144-12-145.as13285.net (78.144.12.145) 14.887 ms host-78-144-12-119.as13285.net (78.144.12.119) 13.446 ms host-78-144-8-63.as13285.net (78.144.8.63) 13.460 ms
6 xe-1-1-0.r2.bb-fo.lon3.vrsn.net (195.66.225.46) 13.698 ms 12.376 ms host-78-144-10-148.as13285.net (78.144.10.148) 13.729 ms
7 xe-4-3-0.r2.bb-fo.ams1.vrsn.net (199.7.62.60) 17.672 ms 18.887 ms 17.582 ms
8 ae2.668.r2.vidn-fo.ams1.vrsn.net (199.16.95.157) 18.874 ms xe-4-3-0.r2.bb-fo.ams1.vrsn.net (199.7.62.60) 21.460 ms 28.046 ms
9 xe-4-3-0.r1.bb-fo.ams1.vrsn.net (199.7.62.20) 52.747 ms ae3.667.r2.vidn-fo.ams1.vrsn.net (199.16.95.155) 18.591 ms xe-4-3-0.r1.bb-fo.ams1.vrsn.net (199.7.62.20) 59.499 ms
10 199.16.80.66 (199.16.80.66) 18.517 ms 217.30.83.10 (217.30.83.10) 19.849 ms ae2.666.r1.vidn-fo.ams1.vrsn.net (199.16.95.153) 22.133 ms
11 199.16.80.66 (199.16.80.66) 21.020 ms 40.909 ms 40.826 ms
12 * * *
13 * * ae0.er01.cwwtf.bbc.co.uk (132.185.254.93) 21.255 ms
14 * 132.185.255.165 (132.185.255.165) 21.014 ms ae0.er02.cwwtf.bbc.co.uk (132.185.254.90) 20.497 ms
15 bbc-vip011.cwwtf.bbc.co.uk (212.58.246.90) <syn,ack> 22.181 ms 132.185.255.165 (132.185.255.165) 22.285 ms ae0.er01.cwwtf.bbc.co.uk (132.185.254.93) 22.864 ms

Blame the asshats who took the BBC off the Internet for a second time in 10 days yesterday and forced them to get serious on DDoS protection.

When did you run that tracert? It just gives up for me as soon as it leaves my ISP.

In reply to a post by RobertoS:

When did you run that tracert? It just gives up for me as soon as it leaves my ISP.

root@HP-Microserver:~# tcptraceroute www.bbc.co.uk 80
traceroute to www.bbc.co.uk (212.58.246.54), 30 hops max, 60 byte packets

Ah. Thanks.

Perhaps similar on a Dell, but too tired now to apply brain.

There are currently several massive DDoS attacks going on against targets in the UK - some with data rates of above 200GBps. You can see some details at http://www.digitalattackmap.com/

yeah we may see this as a permanent policy now, diverted traffic alongside blocking of pings.

Last week I noticed they were diverting traffic, then a few days ago the pings were back to 8ms, but as you said a second attack has took place.

Last week my trace was similar to what ignition posted with latency about 15ms instead of his 40ms, bit went over the same transit.

Now like robertos, I cannot get any routing info outside of my isp's network.

Edited by Chrysalis (Tue 12-Jan-16 08:07:30)

In reply to a post by RobertoS:

Ah. Thanks.

Perhaps similar on a Dell, but too tired now to apply brain.

More about the OS than the manufacturer.

In reply to a post by caffn8me:

There are currently several massive DDoS attacks going on against targets in the UK - some with data rates of above 200GBps. You can see some details at http://www.digitalattackmap.com/

200 gigabytes per second? I suspect a typo, that'd be a world record!

Thanks for link. I have had the pleasure of dealing with this kind of excrement first hand so am not especially tolerant of it.

I don't expect a command incorporating HP-Microserver to work on a Dell, that's all. So would need to find the equivalent if there is one.

In reply to a post by RobertoS:

I don't expect a command incorporating HP-Microserver to work on a Dell, that's all. So would need to find the equivalent if there is one.

That bit isn't part of the command it's part of the command prompt.

The command starts tcptraceroute

Yes, typo. I did of course mean Gbps.

It's a Unix command - Windows equivalent would of course be tracert without resorting to 3rd party utilities.

In reply to a post by ian72:

It's a Unix command - Windows equivalent would of course be tracert without resorting to 3rd party utilities.

tracert does not support TCP traces, so it is not suitable.

This utility does: http://simulatedsimian.github.io/tracetcp.html

I might try that later, thanks Oliver.

Ping plotter pro does tcp pings /tracert BBC are still using verisign , is ine if the last o if their switches before the bbc ae2.666.r1.vidn-fo.ams1.vrsn.net

Target Name: bbc.co.uk
IP: 212.58.246.78
Date/Time: 12/01/2016 14:40:41 to 12/01/2016 14:43:32

Hop PL% Min Max Avg Host Name / [IP]
1 0.0 0 1 0 home.gateway.home.gateway [192.168.1.254]
2 0.0 7 8 7 losubs.subs.dsl1.wh-man.zen.net.uk [62.3.87.145]
3 0.0 7 67 9 ae1-112.cr1.wh-man.zen.net.uk [62.3.80.197]
4 0.6 13 64 18 ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
5 0.0 14 45 15 xe-1-1-0.r2.bb-fo.lon3.vrsn.net [195.66.225.46]
6 0.0 21 59 24 xe-1-3-0.r2.bb-fo.ams1.vrsn.net [199.16.94.174]
7 0.0 21 33 22 ae3.669.r1.vidn-fo.ams1.vrsn.net [199.16.95.159]
8 34.9 20 42 22 ae3.667.r2.vidn-fo.ams1.vrsn.net [199.16.95.155]
9 77.5 22 2993 2839 [217.30.83.10]
10 63.5 21 2998 2882 [217.30.83.10]
11 0.0 0 0 0 [--]
12 64.7 22 2949 1388 ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
13 64.7 22 2949 1388 ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
14 18.5 21 2920 1808 [212.58.246.78]

Edited by tommy45 (Tue 12-Jan-16 14:59:00)

Thanks Ian .

shame opkg system has no tcptraceroute

Fine now.

C:\Users\Bob>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.22] with 32 bytes of data:
Reply from 212.58.244.22: bytes=32 time=36ms TTL=56
Reply from 212.58.244.22: bytes=32 time=17ms TTL=56
Reply from 212.58.244.22: bytes=32 time=18ms TTL=56
Reply from 212.58.244.22: bytes=32 time=42ms TTL=56

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

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

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

1 1 ms 2 ms 1 ms 192.168.1.254
2 17 ms 17 ms 17 ms c.gormless.thn.aa.net.uk [90.155.53.53]
3 17 ms 17 ms 17 ms b.aimless.thn.aa.net.uk [90.155.53.42]
4 17 ms 17 ms 19 ms rt-lonap-a.thdo.bbc.co.uk [5.57.80.90]
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms 18 ms 18 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
8 20 ms 18 ms 18 ms 132.185.255.148
9 18 ms 17 ms 17 ms 212.58.244.22

Trace complete.

C:\Users\Bob>

Grate server names at AA!

You should see the logins to the service, accounts and router, and the passwords are "unusual".

Ta Bob.

Good from here as well (pinging from Linux so the -c 4 means a count of 4, nothing explosive here!)

ping -c 4 bbc.co.uk
PING bbc.co.uk (212.58.246.79) 56(84) bytes of data.
64 bytes from 212.58.246.79: icmp_seq=1 ttl=54 time=9.94 ms
64 bytes from 212.58.246.79: icmp_seq=2 ttl=54 time=9.99 ms
64 bytes from 212.58.246.79: icmp_seq=3 ttl=54 time=9.95 ms
64 bytes from 212.58.246.79: icmp_seq=4 ttl=54 time=9.95 ms

--- bbc.co.uk ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 9.945/9.962/9.994/0.073 ms