Packet loss to google.

[#1]

Hi, I've been noticing slowness/timeouts when accessing google lately, I've run a few pings and seen packet loss only to google. such as below. Other sites like bbc, thinkbroadband etc have no issues. Any ideas?

Pinging www.google.co.uk [216.58.213.99] with 32 bytes of data:
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Request timed out.
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Request timed out.
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Reply from 216.58.213.99: bytes=32 time=12ms TTL=52
Request timed out.

Ping statistics for 216.58.213.99:
Packets: Sent = 15, Received = 12, Lost = 3 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 12ms, Average = 12ms

Pinging www.google.com [216.58.198.164] with 32 bytes of data:
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Request timed out.
Request timed out.
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Request timed out.
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Request timed out.
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Request timed out.
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52
Reply from 216.58.198.164: bytes=32 time=12ms TTL=52

Ping statistics for 216.58.198.164:
Packets: Sent = 18, Received = 13, Lost = 5 (27% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 12ms, Average = 12ms

Pinging play.l.google.com [216.58.198.174] with 32 bytes of data:
Reply from 216.58.198.174: bytes=32 time=13ms TTL=52
Reply from 216.58.198.174: bytes=32 time=12ms TTL=52
Request timed out.
Reply from 216.58.198.174: bytes=32 time=12ms TTL=52
Reply from 216.58.198.174: bytes=32 time=13ms TTL=52
Reply from 216.58.198.174: bytes=32 time=13ms TTL=52
Request timed out.
Request timed out.
Reply from 216.58.198.174: bytes=32 time=12ms TTL=52
Reply from 216.58.198.174: bytes=32 time=12ms TTL=52
Reply from 216.58.198.174: bytes=32 time=13ms TTL=52
Reply from 216.58.198.174: bytes=32 time=13ms TTL=52
Reply from 216.58.198.174: bytes=32 time=13ms TTL=52
Reply from 216.58.198.174: bytes=32 time=13ms TTL=52
Reply from 216.58.198.174: bytes=32 time=13ms TTL=52

Ping statistics for 216.58.198.174:
Packets: Sent = 15, Received = 12, Lost = 3 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms

[#2]

Those are probably Plusnet addresses for their front end cache or whatever it's called.   I don't know if it applies in that case, but parts of Google are known to drop pings as low priority traffic when conditions dictate.  It doesn't mean they're not responding to the traffic they're supposed to be handling. 

[#3]

This has been discussed here, with no real answers.

https://community.plus.net/t5/Fibre-Broadband/10-packet-loss-to-Google-IP-s/m-p/1339031#M39506

[#4]

ah right thanks npr, had a search but didnt see that thread