10% packet loss to Google IP's
@dannyboy75 wrote:
Does anyone know what could be causing this?
A lot of devices process ICMP echo pings at a lower priority than other packets. This can lead to poor response times and in some cases if the device is particularly busy no response at all. Ping is a useful diagnostic when it works but problems getting responses to ping requests is not in itself a problem. It seems curious that attaching your phone to your network affects ICMP but perhaps your phone does its own pinging and something, somewhere is limiting to you to a single continuous stream of pings. I think the bottom line though is just that responding to ping requests is optional and sometimes devices just can't be bothered 
Thanks for the reply
Sorry, I probably didn't word it very clearly, but all I meant with my mobile phone was that if I disconnect it from WiFi (so it's using 4G rather than going out through my router), then it shows no packet loss when pinging these Google IP's. So the issue is only with packets going out via Plusnet. Connecting my phone to my WiFi doesn't affect any of the other computers in the house.
I know what you're saying about packet priorities, but I'm not sure if that would completely explain for me why it's only occurring for these Google addresses. It's no biggie really, I'm just curious as much as anything, but can't help thinking it must be a Plusnet issue.
I've always thought / found pings to google were pretty reliable and as such could be used as a good measure of the ISP's network / routing.
But I've just tried a ping test to the three google servers from my BT connection and I'm getting the same result as you. 
Ping statistics for 8.8.8.8:
Packets: Sent = 35, Received = 30, Lost = 5 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 23ms, Average = 21ms
Ping statistics for 216.58.213.131: (google.co.uk)
Packets: Sent = 36, Received = 32, Lost = 4 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 23ms, Average = 21ms
Ping statistics for 216.58.213.142: (google.com)
Packets: Sent = 46, Received = 41, Lost = 5 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 33ms, Average = 22ms
I've also tried a few website based ping tests to google and none showed any packet loss.
Strange -- don't consider it to be anything to be concerned about just puzzled.
Interesting, glad to hear it's not just me
I wonder if it's a routing issue on a particular PN gateway? According to the checker, I'm currently on psb-ir01. I'm sure when I last checked a few days ago I was still on one of the old gateways so must've been migrated recently.
It gets even better over '6in4' tunneled IPv6 !, fewer hops AND lower latency -
$ mtr google.com
Loss% Snt Last Avg Best Wrst StDev
1. my-home-gateway 0.0% 100 2.9 2.9 2.8 3.0 0.1
2. tunnel.tserv5.lon1.ipv6.he.net 0.0% 100 28.0 23.3 20.9 32.6 3.9
3. v316.core1.lon1.he.net 0.0% 100 16.0 17.6 16.0 21.1 2.0
4. 2001:7f8:17::3b41:1 0.0% 100 19.7 18.6 17.0 20.2 1.2
5. 2001:4860:0:1::104f 0.0% 100 18.3 17.3 16.2 19.4 1.1
6. 2001:4860:0:1::1759 0.0% 100 19.1 16.9 15.5 19.1 1.1
7. lhr25s02-in-x200e.1e100.net 0.0% 100 19.3 17.3 15.6 19.6 1.4
I've yet to hear any explanation from Plusnet how using IPv6 encapsulated in an 6in4 tunnel over the same IPv4 network, can have 25% lower latency and 10% faster bandwidth, than the native IPv4 which carried it !.
