Team,
We are having issues in our Virginia US office & it shows geolocation in all browsers as Canada instead of US region when we access news.google.com in our PC.
Our public ip is 129.46.232.65. This issue is being observed for more than 2 month.
Can you help to whom we can contact to resolve the issue.
Regards,
Raja
This sometimes helps
https://support.google.com/websearch/contact/ip
you should probably also seek out getting geo updated on at least 3 different ones you have 3 different results.
129.46.232.65
ip2location Raleigh NC
neustar butler TN
maxmind Bridgewater NJ
Hi Anthony,
First one already tried & but no response.
Who will help in getting geo updated which shows 3 results as per your email.
Hi Raja,
If you have peering with them (AS15169), you can submit Geolocation data via ISP Portal (https://isp.google.com/).
Regards,
Siyuan
Neustar reporting, found after I sent the last email. Sorry
https://www.security.neustar/resources/tools/submit-to-global-ip-database
Luke
Ns
Thanks Luke. Let me submit the request to maxmind to change it.
How you got below know info. Is there a way to check.
you should probably also seek out getting geo updated on at least 3 different ones you have 3 different results.
129.46.232.65
ip2location Raleigh NC
neustar butler TN
maxmind Bridgewater NJ
I slammed together a Really Bad Script last year that checked all the major geo IP datapack providers via screen scrap or API for a particular issue we were dealing with. If I can find it, I’ll make it Less Really Bad and put it up on Github.
Team,
We are having issues in our lasvegas office & it shows geolocation in all browsers as Israel instead of US region when we access news.google.com in our PC.
Our public ip is 129.46.96.20.
Can you help to whom we can contact to resolve the issue.
Regards,
Raja
Looks like (according to RDNS) it’s a “global NAT” address. Is it only being used in the continental US, or other countries?
If the former, check that geofeeds are correctly configured and registered with Google in their ISP Portal.
If the latter, you’re going to encounter issues.
Regards,
Christopher H.
For Google-related sites specifically and if you haven’t already, it’s worth publishing an RFC8805-compliant geofeed and submitting it to them via their ISP portal at https://isp.google.com/ if you have an account with the announcing ASN affiliated to it. This is assuming that the IP you specified is linked to an organization and network you’re affiliated with, which based on your email’s domain and the announcing ASN is most likely the case.
For other sites and geolocation databases, it’s worth submitting the same geofeed to each DB/provider individually via email or by following the information on https://geolocatemuch.com/ to enable other DBs/providers to automatically discover and update their databases.
Hi Christopher,
It is used only in continental US & we also reported this issue to at noc@google.com.
Any further info to be provided to resolve this issue.
Regards,
Raja
As Peter and I have mentioned, you’ll need to register a geofeed with Google. An example can be downloaded from https://isp.google.com/static/downloads/example-geo-feed.csv and registered in the ISP Portal.
Having said that, it may be worthwhile checking-in with your internal IP Network Operations team (if you don’t have access to manage this). Being Qualcomm, I’d imagine relationships with Google would already exist.
Regards,
Christopher H.
Regards,
Hank