https://support.google.com/websearch/answer/873?hl=en On 7 April 2015 at 23:26, John Levine <johnl@iecc.com> wrote:
A friend of mine lives in Alabama and has business service from at&t. But Google thinks he's in France. We've checked for various possibilities of VPNs and proxies and such, and it's pretty clear that the Goog's geolocation for addresses around 99.106.185.0/24 is screwed up. Bing and other services correctly find him in Alabama.
Poking around I see lots of advice about how to use Google's geolocation data, but nothing on how to update it. Anyone know the secret? TIA
Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
He says he sent in the IP update three weeks ago, nothing happened. Any other suggestions?
On 7 April 2015 at 23:26, John Levine <johnl@iecc.com> wrote:
A friend of mine lives in Alabama and has business service from at&t. But Google thinks he's in France. We've checked for various possibilities of VPNs and proxies and such, and it's pretty clear that the Goog's geolocation for addresses around 99.106.185.0/24 is screwed up. Bing and other services correctly find him in Alabama.
Poking around I see lots of advice about how to use Google's geolocation data, but nothing on how to update it. Anyone know the secret? TIA
Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
"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. On Tue, Apr 7, 2015 at 9:24 PM, John R. Levine <johnl@iecc.com> wrote:
He says he sent in the IP update three weeks ago, nothing happened. Any other suggestions?
On 7 April 2015 at 23:26, John Levine <johnl@iecc.com> wrote:
A friend of mine lives in Alabama and has business service from at&t. But Google thinks he's in France. We've checked for various possibilities of VPNs and proxies and such, and it's pretty clear that the Goog's geolocation for addresses around 99.106.185.0/24 is screwed up. Bing and other services correctly find him in Alabama.
Poking around I see lots of advice about how to use Google's geolocation data, but nothing on how to update it. Anyone know the secret? TIA
Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
Pedro Cavaca suggests:
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 -----Original Message----- From: NANOG [mailto:nanog-bounces+matthew.black=csulb.edu@nanog.org] On Behalf Of Pedro Cavaca Sent: Tuesday, April 07, 2015 3:41 PM To: John Levine Cc: NANOG Mailing List Subject: Re: Fixing Google geolocation screwups https://support.google.com/websearch/answer/873?hl=en On 7 April 2015 at 23:26, John Levine <johnl@iecc.com> wrote:
A friend of mine lives in Alabama and has business service from at&t. But Google thinks he's in France. We've checked for various possibilities of VPNs and proxies and such, and it's pretty clear that the Goog's geolocation for addresses around 99.106.185.0/24 is screwed up. Bing and other services correctly find him in Alabama.
Poking around I see lots of advice about how to use Google's geolocation data, but nothing on how to update it. Anyone know the secret? TIA
Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
On 5 May 2015 at 16:22, Matthew Black <Matthew.Black@csulb.edu> wrote:
Pedro Cavaca suggests:
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."
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.
matthew black california state university, long beach
-----Original Message----- From: NANOG [mailto:nanog-bounces+matthew.black=csulb.edu@nanog.org] On Behalf Of Pedro Cavaca Sent: Tuesday, April 07, 2015 3:41 PM To: John Levine Cc: NANOG Mailing List Subject: Re: Fixing Google geolocation screwups
https://support.google.com/websearch/answer/873?hl=en
On 7 April 2015 at 23:26, John Levine <johnl@iecc.com> wrote:
A friend of mine lives in Alabama and has business service from at&t. But Google thinks he's in France. We've checked for various possibilities of VPNs and proxies and such, and it's pretty clear that the Goog's geolocation for addresses around 99.106.185.0/24 is screwed up. Bing and other services correctly find him in Alabama.
Poking around I see lots of advice about how to use Google's geolocation data, but nothing on how to update it. Anyone know the secret? TIA
Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
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... On Tue, May 5, 2015 at 11:22 AM, Matthew Black <Matthew.Black@csulb.edu> wrote:
Pedro Cavaca suggests:
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
-----Original Message----- From: NANOG [mailto:nanog-bounces+matthew.black=csulb.edu@nanog.org] On Behalf Of Pedro Cavaca Sent: Tuesday, April 07, 2015 3:41 PM To: John Levine Cc: NANOG Mailing List Subject: Re: Fixing Google geolocation screwups
https://support.google.com/websearch/answer/873?hl=en
On 7 April 2015 at 23:26, John Levine <johnl@iecc.com> wrote:
A friend of mine lives in Alabama and has business service from at&t. But Google thinks he's in France. We've checked for various possibilities of VPNs and proxies and such, and it's pretty clear that the Goog's geolocation for addresses around 99.106.185.0/24 is screwed up. Bing and other services correctly find him in Alabama.
Poking around I see lots of advice about how to use Google's geolocation data, but nothing on how to update it. Anyone know the secret? TIA
Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
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. - Matt
In message <20150505210746.GH22158@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.
- 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 -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
On Wed, May 06, 2015 at 10:56:22AM +1000, Mark Andrews wrote:
In message <20150505210746.GH22158@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 -- Skippy was a wallaby. ... Wallabies are dumb and not very trainable... The *good* thing...is that one Skippy looks very much like all the rest, hence..."one-shot Skippy" and "plug-compatible Skippy". I don't think they ever had to go as far as "belt-fed Skippy" -- Robert Sneddon, ASR
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. 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@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
On Wed, May 6, 2015 at 3:19 AM, Fred Hollis <fred@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@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
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
participants (9)
-
Bryan Socha -
Christopher Morrow -
Fred Hollis -
John R. Levine -
Luan Nguyen -
Mark Andrews -
Matt Palmer -
Matthew Black -
Pedro Cavaca