See results for a different country - Computer - Google Search Help
He says he sent in the IP update three weeks ago, nothing happened. Any other suggestions?
"We'll investigate your report and, if necessary, pass the details on
to our engineering team. Updates to IP addresses may take more than a
month. We won't follow up with you individually but we'll do our best
to resolve the issue."
'more than a month' > 3wks.
Pedro Cavaca suggests:
See results for a different country - Computer - Google Search Help
Correct me if I'm wrong, that looks like Google simply saves location data in a browser cookie.
"A location helps Google find more relevant information when you use Search, Maps, and other Google products. Learn how Google saves location information on this computer."
matthew black
california state university, long beach
Pedro Cavaca suggests:
> See results for a different country - Computer - Google Search HelpCorrect me if I'm wrong, that looks like Google simply saves location data
in a browser cookie."A location helps Google find more relevant information when you use
Search, Maps, and other Google products. Learn how Google saves location
information on this computer."
I don't see the text you quoted on the URL I provided.
I do see a "report the problem" clickable, which was the point I was
trying to make on my original answer.
There's a form here - https://support.google.com/websearch/contact/ip
But google is pretty smart, its systems will learn the correct geolocation
over time...
That'd be quite a trick, given that the netblock practically can't be used
at all with Google services.
- Matt
One would expect support.google.com to not be geo blocked just like
postmaster@ should not be filtered. That said they can always
disable IPv6 temporarially (or just firewall off the IPv6 instance
of support.google.com and have the browser fallback to IPv4) and
reach support.google.com over IPv4 to lodge the complaint.
Mark
I was specifically responding to the suggestion that Google would
automagically "learn" the correct location of the netblock, presumably based
on the characteristics of requests coming from the range. Being explicitly
told that a given netblock is in a given location (as effective, or
otherwise, as that may be) doesn't really fit the description of "systems
[learning] the correct geolocation over time".
- Matt
Honestly, I lost patience "the system learning the proper location of the IPv6 block". I have a very similar problem to the OP since 4-5 months, submitted this IP correction form multiple times... nothing changed.
This is *very* annoying.
Yes, my whois/SWIP is perfectly fine, every other geo ip database is showing correct location.
Honestly, I lost patience "the system learning the proper location of the
IPv6 block". I have a very similar problem to the OP since 4-5 months,
submitted this IP correction form multiple times... nothing changed.
This is *very* annoying.Yes, my whois/SWIP is perfectly fine, every other geo ip database is showing
correct location.
which block fred?
The best way as a isp/provider to keep google updated on your geo is:
1: support their self published geo feed:
http://tools.ietf.org/id/draft-google-self-published-geofeeds-02.html
2: If you qualify get setup on their peering portal http://peering.google
com and you'll be able to provide them with your feed and see it's
processing status/errors/etc
3: wait a few weeks, it'll take awhile after first process to get all
around google.
4: keep your geofeed data accurate keeping it mind it can take a few weeks
for new blocks to populate around google.
Alternatively, you can try to support their feed and ask the noc to forward
a request to the geo team to pull it, it'll help but don't expect it perm
fixed.
This is only for the services where they might block based on location or
default to a specific language. You're not going to alter things like
where on google maps you appear.
Bryan Socha
Network Engineer
DigitalOcean