Google dns very high ping and routing issues.

[j154822]

I'm not sure what's happening with Google DNS on BT, but the ping has spiked from the normal 10ms to the average of 123 ms, and trace routing is completely timed out.

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=124ms TTL=115
Reply from 8.8.8.8: bytes=32 time=123ms TTL=115
Reply from 8.8.8.8: bytes=32 time=124ms TTL=115
Reply from 8.8.8.8: bytes=32 time=123ms TTL=115

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

C:\Windows\System32>

1 1 ms 1 ms 3 ms * * * * * * [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 124 ms 123 ms 123 ms dns.google [8.8.8.8]

8.8.4.4 this is normal 

Pinging 8.8.4.4 with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=10ms TTL=116
Reply from 8.8.4.4: bytes=32 time=11ms TTL=116
Reply from 8.8.4.4: bytes=32 time=12ms TTL=116
Reply from 8.8.4.4: bytes=32 time=12ms TTL=116

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

[pippincp]

Perhaps it is an issue with the server at 8.8.8.8 as 8.8.4.4 appear to return a different result.

[j154822]

I asked a friend who lives in France to test and pinging 8.8.8.8 they came back with an average of 10ms so it appears to be an issue localised to either the UK or BT

[c64z86]

I think there may be an issue with your connection or something along your path to BT and 8.8.8.8 instead, sadly, as this is what it shows for me, even over WiFi. 

Reply from 8.8.8.8: bytes=32 time=20ms TTL=115
Reply from 8.8.8.8: bytes=32 time=17ms TTL=115
Reply from 8.8.8.8: bytes=32 time=13ms TTL=115
Reply from 8.8.8.8: bytes=32 time=15ms TTL=115

Reply from 8.8.4.4: bytes=32 time=14ms TTL=115
Reply from 8.8.4.4: bytes=32 time=14ms TTL=115
Reply from 8.8.4.4: bytes=32 time=14ms TTL=115
Reply from 8.8.4.4: bytes=32 time=15ms TTL=115

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 5 ms 2 ms 2 ms 192.168.1.254
3 5 ms 5 ms 4 ms 172.16.18.76
4 * * * Request timed out.
5 16 ms 14 ms 13 ms 31.55.186.184
6 15 ms 13 ms 13 ms 195.99.127.40
7 14 ms 13 ms 11 ms peer3-et0-0-6.redbus.ukcore.bt.net [194.72.16.88]
8 15 ms 14 ms 15 ms 109.159.253.3
9 15 ms 12 ms 13 ms 209.85.253.95
10 18 ms 15 ms 13 ms 142.251.54.29
11 16 ms 15 ms 13 ms dns.google [8.8.8.8]

I just read this on the Google forum that may help:

"While Google does not block ICMP or random UDP to 8.8.8.8 or other Google Public DNS IP addresses, there are rate limits on ICMP error replies from Google networking equipment, and ICMP error replies may be de-prioritized within Google networks and could be more likely to be dropped."

[j154822]

Edit

Factory resting my Asus router appears to have fixed the high ping issues thanks

[c64z86]

I'm not entirely sure either, but I think Google may be partially blocking certain IP addresses because they are think that they are being used for DOS attacks when they are not.

There are other users on this forum who have reported Google suddenly thinking they are in the USA, which, behind the scenes, may or may not have a connection to the issues you have.

[pippincp]

Please contihue with your conspiracy theory. I'm happy to just ignore it.

[c64z86]

Hm that is strange behaviour indeed to reply to a "conspiracy theory" that you are supposedly pretending not to read, then. But, whatever, you do you. 🤷

[Crimliar]

If you are using an Asus router, especially if you are using the Asus-Merlin firmware, it gives you the ability to thoroughly mess up your DNS if you make the wrong settings/choices.