Tracing route to google.com [142.250.200.46]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms unifi.localdomain [192.168.1.1]
2 7 ms 7 ms 7 ms 79.135.101.1
3 11 ms 8 ms 7 ms 195.72.67.241
4 * * * Request timed out.
5 8 ms 7 ms 7 ms 72.14.221.145
6 8 ms 8 ms 8 ms 209.85.249.187
7 22 ms 7 ms 8 ms 142.251.52.143
8 8 ms 8 ms 8 ms lhr48s30-in-f14.1e100.net [142.250.200.46]
My BT line is routing correctly so definitely a yayzi issue. Youtube is also effected on yayzi.
BT tracert
tracert www.google.com
Tracing route to www.google.com [142.250.187.228]
over a maximum of 30 hops:
1 3 ms 2 ms 2 ms -
2 7 ms 5 ms 5 ms -
4 * * 12 ms 62.172.102.76
5 50 ms 12 ms 12 ms 62.172.102.9
6 15 ms 13 ms 13 ms 109.159.253.3
7 14 ms 12 ms 12 ms 209.85.253.95
8 13 ms 11 ms 11 ms 142.251.54.47
9 12 ms 10 ms 11 ms 142.250.187.228
Trace complete.
Yayzi tracert
tracert www.google.com
Tracing route to www.google.com [216.58.223.228]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms -
2 8 ms 8 ms 8 ms -
3 8 ms 8 ms 8 ms 195.72.67.241
4 * * * Request timed out.
5 8 ms 8 ms 8 ms 72.14.221.145
6 9 ms 9 ms 9 ms 209.85.249.187
7 9 ms 9 ms 9 ms 192.178.98.6
8 106 ms 114 ms 105 ms 142.251.235.255
9 105 ms 105 ms 105 ms 192.178.106.251
10 104 ms 104 ms 104 ms 172.253.76.219
11 105 ms 105 ms 105 ms los02s04-in-f4.1e100.net [216.58.223.228]
Trace complete.
This is just the nature of networks, routes change for all kinds of reasons I can almost guarantee it will be temporary. I have had the same thing happen to me but has always changed back after a few days.
The routing is a red herring, your DNS lookup to Google is resolving a US IP. Thats why its routing you there. As to why, who knows - possibly IP Geo shenanigans.
This wasn’t an issue last week and iplocation.io shows me as located in the UK still. It’s only happened since the port upgrade which is why I reperted it here. If yayzi can/want to do anything about it it’s on them now. I’ve done my bit
I understand routing can vary but flinging me half way around the world is a bit extreme
It might not of been immediately after the upgrade. I was pinging various things before and after and I’m pretty sure it wasn’t high straight after the upgrade went live. Noticed a few days later on webnesday google wasn’t it’s usual snappy self so tested again and yep it was 10x higher than normal.
I notice now base latency went up a few MS just after mignight on the 5th as well, which is fine but might point you to when something might of changed.
Been great since the upgrade. Getting little bit of packet loss some days. Doubt it is significantly impacting anything but seeing less red is always good
