3 ms·
GeoIP routing is sometimes worse with native IPv6 than IPv4. Take gstatic.com for example which goes to a neighbouring country with IPv6 (inside same ISP, but s
by edwintorok 11y ago
GeoIP routing is sometimes worse with native IPv6 than IPv4.
Take gstatic.com for example which goes to a neighbouring country with IPv6 (inside same ISP, but still):
$ ping -c 3 gstatic.com
PING gstatic.com (82.77.159.222) 56(84) bytes of data.
64 bytes from cache.google.com (82.77.159.222): icmp_seq=1 ttl=61 time=2.11 ms
64 bytes from cache.google.com (82.77.159.222): icmp_seq=2 ttl=61 time=1.98 ms
64 bytes from cache.google.com (82.77.159.222): icmp_seq=3 ttl=61 time=1.78 ms
--- gstatic.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 1.780/1.960/2.118/0.143 m
$ ping6 -c 3 gstatic.com
PING gstatic.com(bud02s22-in-x03.1e100.net) 56 data bytes
64 bytes from bud02s22-in-x03.1e100.net: icmp_seq=1 ttl=55 time=9.85 ms
64 bytes from bud02s22-in-x03.1e100.net: icmp_seq=2 ttl=55 time=9.67 ms
64 bytes from bud02s22-in-x03.1e100.net: icmp_seq=3 ttl=55 time=10.5 ms
--- gstatic.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 9.675/10.031/10.568/0.403 ms
So I have this in /etc/gai.conf now:
precedence ::ffff:0:0/96 100
- scurvy 11y agoThe worst problem with Google's GeoIP implementation is that you really can't report problems to them in a good manner. They have this: https://support.google.com/websearch/contact/ip https://support.google.com/websearch/contact/ip but it only works for Google.com and not YouTube. I really, really wish Google would put more resources on this.
- secure 11y agoI heard that you can report YouTube connection issues at https://www.reddit.com/r/youtube https://www.reddit.com/r/youtube, and YouTubers will address them. Have you tried that?