Fixing Google geolocation screwups

Thu May 7 02:52:28 UTC 2015

On Wed, May 6, 2015 at 3:19 AM, Fred Hollis <fred at web2objects.com> wrote:
> 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?

>
> On 06.05.2015 at 03:36 Matt Palmer wrote:
>>
>> On Wed, May 06, 2015 at 10:56:22AM +1000, Mark Andrews wrote:
>>>
>>> In message <20150505210746.GH22158 at hezmatt.org>, Matt Palmer writes:
>>>>
>>>> On Tue, May 05, 2015 at 12:03:23PM -0400, Luan Nguyen wrote:
>>>>>
>>>>> 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.
>>>
>>>
>>> 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.
>>
>>
>> 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
>>
>