bbc pings

hope its nothing at my end but seemingly pings to the bbc.com site have gone from about 11-12ms to about 360ms,is it anything to do with the launch of their new app to listen to any and every radio station?too much usage not enough bandwidth?

Depends on where the location being pinged actually is, i.e. load may DNS resolving to a node that is some way away

If you look at my BQM links in my sig, you will see my average latency on that is about 20ms. So no problem here with bbc.com

ping bbc.com

Pinging bbc.com [2a04:4e42:200::81] with 32 bytes of data:
Reply from 2a04:4e42:200::81: time=19ms
Reply from 2a04:4e42:200::81: time=20ms
Reply from 2a04:4e42:200::81: time=20ms
Reply from 2a04:4e42:200::81: time=20ms

Ping statistics for 2a04:4e42:200::81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 20ms, Average = 19ms

C:\Users\Bob>ping bbc.com -4

Pinging bbc.com [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=20ms TTL=60
Reply from 151.101.0.81: bytes=32 time=20ms TTL=60
Reply from 151.101.0.81: bytes=32 time=20ms TTL=60
Reply from 151.101.0.81: bytes=32 time=20ms TTL=60

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

Nothing unusual here regarding pings, the connection is ADSL1 so the average time is around 46ms at the moment.

mine up to last few days have always been around the 12ms mark,all other sites seem normal only bbc.com and bbc.co.uk have gone high
this is what I am seeing

Microsoft Windows [Version 10.0.17134.376]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping bbc.com

Pinging bbc.com [2a04:4e42:400::81] with 32 bytes of data:
Reply from 2a04:4e42:400::81: time=335ms
Reply from 2a04:4e42:400::81: time=335ms
Reply from 2a04:4e42:400::81: time=335ms
Reply from 2a04:4e42:400::81: time=335ms

Ping statistics for 2a04:4e42:400::81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 335ms, Maximum = 335ms, Average = 335ms

C:\WINDOWS\system32>ping google.com

Pinging google.com [2a00:1450:4009:807::200e] with 32 bytes of data:
Reply from 2a00:1450:4009:807::200e: time=12ms
Reply from 2a00:1450:4009:807::200e: time=12ms
Reply from 2a00:1450:4009:807::200e: time=12ms
Reply from 2a00:1450:4009:807::200e: time=12ms

Ping statistics for 2a00:1450:4009:807::200e:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 12ms, Average = 12ms

C:\WINDOWS\system32>ping idnet.net

Pinging idnet.net [2a02:390:1::49:444e:6574] with 32 bytes of data:
Reply from 2a02:390:1::49:444e:6574: time=12ms
Reply from 2a02:390:1::49:444e:6574: time=12ms
Reply from 2a02:390:1::49:444e:6574: time=12ms
Reply from 2a02:390:1::49:444e:6574: time=11ms

Ping statistics for 2a02:390:1::49:444e:6574:

Edited by steve195527 (Sat 03-Nov-18 19:37:44)

In reply to a post by MrSaffron:

Depends on where the location being pinged actually is, i.e. load may DNS resolving to a node that is some way away

so one of nodes in my path may have developed a fault?

Try this, which might show you where the bottleneck is:-

tracert bbc.com

Also, what do you get if you use the "-4" parameter as in my second one earlier. So:- ping bbc.com -4

Here is my ping, I had to force it to use IPv4 due to my Security Suit blocks IPv6 ICMP and I cannot be bother to unblock it.

*** Ping ***

ping -4 bbc.com

Pinging bbc.com [151.101.128.81] with 32 bytes of data:
Reply from 151.101.128.81: bytes=32 time=2ms TTL=57
Reply from 151.101.128.81: bytes=32 time=2ms TTL=57
Reply from 151.101.128.81: bytes=32 time=2ms TTL=57
Reply from 151.101.128.81: bytes=32 time=2ms TTL=57

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

*** Trace Route ***

tracert -4 bbc.com

Tracing route to bbc.com [151.101.128.81]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Yazoo [192.168.2.253]
  2     1 ms     1 ms     1 ms  172.16.10.194
  3     2 ms     2 ms     3 ms  31.55.186.181
  4     4 ms     4 ms     3 ms  31.55.186.180
  5     3 ms     3 ms     3 ms  core4-hu0-6-0-1.faraday.ukcore.bt.net [195.99.127.200]
  6     3 ms     2 ms     2 ms  peer8-et-3-0-3.telehouse.ukcore.bt.net [62.6.201.214]
  7     3 ms     2 ms     2 ms  195.99.126.83
  8     2 ms     2 ms     2 ms  151.101.128.81

Trace complete.

It seems fine to me, but maybe its now all sorted.

Paul

In reply to a post by RobertoS:

Try this, which might show you where the bottleneck is:-

tracert bbc.com

Also, what do you get if you use the "-4" parameter as in my second one earlier. So:- ping bbc.com -4

Yeah I have to do IPv4 checks myself due to my security suit blocks IPv6 ICMP pings.

Paul

trace shows this:-

Tracing route to bbc.com [2a04:4e42:200::81]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 2a02:390:7aaa:0:6203:47ff:fe37:3cb5
2 12 ms 11 ms 12 ms 2a02:390:ffff:ffff:ffff:ffff:ffff:fff6
3 11 ms 11 ms 11 ms 2a02:390:0:ff28::
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 298 ms 298 ms 298 ms 2403:e800:ff00:110::3f
9 * * 297 ms 2403:e800:105:36::2
10 * * * Request timed out.
11 * * 328 ms bundle-ether20.cha-core10.brisbane.telstra.net [2001:8000:0:2000:3001:6001:0:a]
12 * * * Request timed out.
13 * * * Request timed out.
14 332 ms 332 ms 332 ms fas2991580.lnk.telstra.net [2001:8000:106:b0::2]
15 334 ms 334 ms 335 ms 2a04:4e42:200::81

Trace complete.
not sure what it means or how to fix,if I can from my end?

ipv4 pings are ok:-

Microsoft Windows [Version 10.0.17134.376]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\steve>ping bbc.com -4

Pinging bbc.com [151.101.128.81] with 32 bytes of data:
Reply from 151.101.128.81: bytes=32 time=11ms TTL=61
Reply from 151.101.128.81: bytes=32 time=12ms TTL=61
Reply from 151.101.128.81: bytes=32 time=11ms TTL=61
Reply from 151.101.128.81: bytes=32 time=11ms TTL=61

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

Edited by steve195527 (Sun 04-Nov-18 00:35:44)