Sep 23, 2021
Another IPv6 country detection issue
Google IPv6 geolocation seems to be in a pretty tech-demo state.
2a01:7e00::/32 is in the UK but Google has been bouncing it around a lot.
This week, Google thinks I'm in Hong Kong. Last month, Brazil I think, before that, some Easten European country. In fact, the one country google hasn't associated it with is the UK as far as I can tell... This sort of thing seems pretty common with Google (only!).
I've tried this form https://support.google.com/websearch/contact/ip but that doesn't accept IPv6 addresses. 🤦♂️
Is there another channel of reporting this?
cheers!
Details
Informational notification.
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
All Replies (7)
Just for clarification, can you please let me know what specific challenges you face, if any, caused by the incorrect location.
For instance, is the incorrect location changing the language of the interface, or the language of the search results? Are you seeing incorrect search results?
Sep 27, 2021
Yes. Off the top of my head, Incessant capatchas trying to use Google services; google.com searches are currently defaulting to .hk and displaying in presumably Chinese; Google maps is showing outdated aerial imagery around my (uk) office.
Last edited Sep 28, 2021
Oct 13, 2021
Are you still experiencing this issue? I've heard nothing back from the Google Search team yet.
Dec 6, 2021
Yes.
I have effectively disabled my IPv6 connectivity just to work around this issue.
As a test, I enabled IPv6, was directed to the Google HK, and had to pass 8 capatchas to get to this post.For a bit I thought it might be a DNS Geolocation thing rather than a direct GeoIP thing.
For google.com I get similar IPs back from 1.1.1.1, 8.8.8.8, and 9.9.9.11 all pointing to the LHR datacentre but 9.9.9.9 directs me to AMS. This suggested an issue between Google and Quad9 as 9.9.9.11 has ECS enabled, which I assume is passing my DNS endpoint's IPv4 address through as clients all have private IP4s.
But no, all my IPv6 traffic gets converted to google.com.hk regardless of which resolver my DNS server uses.
I've asked the Google Search team for an update on this issue.