Re: Fixing Google geolocation screwups
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
Re: Fixing Google geolocation screwups
On Wed, May 6, 2015 at 3:19 AM, Fred Hollis 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.gh22...@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 >> >
Re: Fixing Google geolocation screwups
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.gh22...@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
Re: Fixing Google geolocation screwups
On Wed, May 06, 2015 at 10:56:22AM +1000, Mark Andrews wrote: > In message <20150505210746.gh22...@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
Re: Fixing Google geolocation screwups
In message <20150505210746.gh22...@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: ma...@isc.org
Re: Fixing Google geolocation screwups
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
Re: Fixing Google geolocation screwups
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 wrote: > Pedro Cavaca suggests: > > https://support.google.com/websearch/answer/873?hl=en > > 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@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 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, jo...@iecc.com, Primary Perpetrator of "The Internet for > > Dummies", Please consider the environment before reading this e-mail. > > http://jl.ly > > > > > > >
Re: Fixing Google geolocation screwups
On 5 May 2015 at 16:22, Matthew Black wrote: > Pedro Cavaca suggests: > > https://support.google.com/websearch/answer/873?hl=en > > 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@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 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, jo...@iecc.com, Primary Perpetrator of "The Internet for > > Dummies", Please consider the environment before reading this e-mail. > > http://jl.ly > > > > > > >
RE: Fixing Google geolocation screwups
Pedro Cavaca suggests: > https://support.google.com/websearch/answer/873?hl=en 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@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 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, jo...@iecc.com, Primary Perpetrator of "The Internet for > Dummies", Please consider the environment before reading this e-mail. > http://jl.ly > > >
Re: Fixing Google geolocation screwups
shawn wilson writes: > On Apr 8, 2015 7:19 AM, "Rob Seastrom" <[[r...@seastrom.com]]> wrote: >> >> >> Blair Trosper <[[blair.tros...@gmail.com]]> writes: >> >> > MaxMind (a great product) >> >> I've heard anecdotal accounts of MaxMind intentionally marking all >> address blocks assigned to a VPN vendor as "open proxy" even when >> advised repeatedly that the disputed addresses (a) had no VPN services >> running on them either inbound or outbound, and (b) in fact were web >> servers for the company's payment system, or mail servers for their >> corporate email. >> > > I would wonder if these apps didn't have issues that allowed web proxy to the > world. Maybe MaxMind is doing something wrong or maybe they're seeing the > result of malicious activities and classifying from that. That was not the conclusion that one would draw from their replies. -r
Re: Fixing Google geolocation screwups
On 04/08/15 14:56, Jeroen Massar wrote: > That stated, properly providing a WHOIS entry for each prefix > (inetnum/inet6num) is a good idea as that kind of indicates that that > prefix is fixed in that location and not just moving around. [skip] > Do make sure though that you do not show any foreign address in the > whois data (even if that is the correct entity that the prefix is > registered under) Seems that it is contrary to each other ;) I thought to do something like automated whois query on tunnel destination and put that (geo)data to each /48 inet6num tunnelled. But as I don't believe it will help, so priority of that task is low and not yet realized.
Re: Fixing Google geolocation screwups
Globalisation only works if network abuse and network contacts follow best practice and engage. Else trade blocks and network country blocks are done and remain in place until certain countries ethically/practically do the right thing. Colin > On 8 Apr 2015, at 13:17, Tim Franklin wrote: > >> That all said: Restricting content based on location is complete and >> utter nonsense in 2015. The world is global, people want to pay for >> content and the content owners just don't allow people to pay for it. > > Globalisation is for your corporate lords and masters to buy labour and raw > materials where they're cheap. > > If mere peons try to buy goods and services in the same way, expect to be > crushed by the best legislation money can buy :( > > Regards, > Tim.
Re: Fixing Google geolocation screwups
> That all said: Restricting content based on location is complete and > utter nonsense in 2015. The world is global, people want to pay for > content and the content owners just don't allow people to pay for it. Globalisation is for your corporate lords and masters to buy labour and raw materials where they're cheap. If mere peons try to buy goods and services in the same way, expect to be crushed by the best legislation money can buy :( Regards, Tim.
Re: Fixing Google geolocation screwups
On 2015-04-08 13:31, Max Tulyev wrote: > We operate IPv6 tunnel broker tb.netassist.ua, so /48 from our /32 is > spread all around the world. > Google change geo of our WHOLE /32 from time to time to another cute > random place ;) One time Google decided we are in IRAN and block a lot > of content as "not available in your country" o_O > Unfortunately, there is no "magic button" to fix it, as well as no human > contact in Google to discuss it. I'm still trying to find a good > solution, but not found it. Do check: http://tools.ietf.org/html/draft-google-self-published-geofeeds-02 That draft also contains folks to kick who wrote it. Or more details on how SixXS uses that: https://www.sixxs.net/faq/misc/?faq=geolocation It is a hard problem unfortunately as there are a variety of reasons why content owners perform Geolocation (language detection / Content restrictions etc). For most organizations "Geolocation" all comes down to "IP Protection" (Stupid Property aka "Content", not Internet Protocol). Hence, if you have a /32 IPv6 assigned to the Ukraine (which is already considered a shady country by most unfortunately for you) and then start offering VPN services, you'll likely just end up blocked in most of these "IP protecting networks" as folks just think you are trying to circumvent their great and awesome IP Protection strategies. That stated, properly providing a WHOIS entry for each prefix (inetnum/inet6num) is a good idea as that kind of indicates that that prefix is fixed in that location and not just moving around. As for Google, well, they have the method described above, but as they are primarily a HTTP company, they could just detect Language setting by the HTTP Accept-Language header. For YouTube etc they are in the same boat as everybody else: IP Protection. (property not network). In the end, having a prefix per country/region is the correct way to go. Do make sure though that you do not show any foreign address in the whois data (even if that is the correct entity that the prefix is registered under) otherwise that whole prefix will suddenly be blocked by for instance Netflix as "it is foreign"... Though Netflix always considers VPNs as a bad thing, ignoring the fact that for some folks that is the only real way to get a reasonable Internet experience. That all said: Restricting content based on location is complete and utter nonsense in 2015. The world is global, people want to pay for content and the content owners just don't allow people to pay for it. We all know what the end result of that is ;) Greets, Jeroen
Re: Fixing Google geolocation screwups
On Apr 8, 2015 7:19 AM, "Rob Seastrom" wrote: > > > Blair Trosper writes: > > > MaxMind (a great product) > > I've heard anecdotal accounts of MaxMind intentionally marking all > address blocks assigned to a VPN vendor as "open proxy" even when > advised repeatedly that the disputed addresses (a) had no VPN services > running on them either inbound or outbound, and (b) in fact were web > servers for the company's payment system, or mail servers for their > corporate email. > I would wonder if these apps didn't have issues that allowed web proxy to the world. Maybe MaxMind is doing something wrong or maybe they're seeing the result of malicious activities and classifying from that.
Re: Fixing Google geolocation screwups
We operate IPv6 tunnel broker tb.netassist.ua, so /48 from our /32 is spread all around the world. Google change geo of our WHOLE /32 from time to time to another cute random place ;) One time Google decided we are in IRAN and block a lot of content as "not available in your country" o_O Unfortunately, there is no "magic button" to fix it, as well as no human contact in Google to discuss it. I'm still trying to find a good solution, but not found it. On 04/08/15 01:26, John Levine 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, jo...@iecc.com, Primary Perpetrator of "The Internet for > Dummies", > Please consider the environment before reading this e-mail. http://jl.ly > > >
Re: Fixing Google geolocation screwups
Blair Trosper writes: > MaxMind (a great product) I've heard anecdotal accounts of MaxMind intentionally marking all address blocks assigned to a VPN vendor as "open proxy" even when advised repeatedly that the disputed addresses (a) had no VPN services running on them either inbound or outbound, and (b) in fact were web servers for the company's payment system, or mail servers for their corporate email. Kind of reminiscent of dealing with certain RBLs for whom "personal beef" was enough reason to list an address. So, folks might want to temper the "great product" comment with this anti-endorsement. -r
Re: Fixing Google geolocation screwups
maxmind is the company that does it for speedtest.net So if you've ever wondered why your IP blocks still show up as coming from your upstream and not you, well, that's why. /hard_learned_trade_secret On 04/07/2015 03:17 PM, Blair Trosper wrote: No, Google has their own internal system. Doubt MaxMind will help out. This discussions and others like it may lead you in the right direction: https://productforums.google.com/forum/#!topic/websearch/fkyem9xUKOQ On Tue, Apr 7, 2015 at 6:10 PM, Aaron C. de Bruyn wrote: You might try here: https://www.maxmind.com/en/correction -A On Tue, Apr 7, 2015 at 3:42 PM, Fred Hollis wrote: Thanks for sending this to the list: We have the very same issue as well (both IPv4+IPv6). If someone knows the magic button to solve this, please contact me as well. On 08.04.2015 at 00:26 John Levine 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, jo...@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
Re: Fixing Google geolocation screwups
"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 wrote: >> https://support.google.com/websearch/answer/873?hl=en > > > 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 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, jo...@iecc.com, Primary Perpetrator of "The Internet for >>> Dummies", >>> Please consider the environment before reading this e-mail. http://jl.ly >>> >>> >>> >> >
Re: Fixing Google geolocation screwups
https://support.google.com/websearch/answer/873?hl=en 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 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, jo...@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
Re: Fixing Google geolocation screwups
It wouldn't hurt to correct it with MaxMind (a great product), but you'd probably have better results dealing with Google directly. If you have Google Apps, you've got support, and that would be one way to go about getting it addressed. On Tue, Apr 7, 2015 at 6:29 PM, Aaron C. de Bruyn wrote: > I figure they all collaborate. I updated one of our IPs with MaxMind > and a few weeks later Google was fixed. > > Of course that could be because half the staff here carry tiny > GPS-enabled Google location reporting devices in their pocket too... > > -A > > On Tue, Apr 7, 2015 at 4:17 PM, Blair Trosper > wrote: > > No, Google has their own internal system. Doubt MaxMind will help out. > > > > This discussions and others like it may lead you in the right direction: > > https://productforums.google.com/forum/#!topic/websearch/fkyem9xUKOQ > > > > On Tue, Apr 7, 2015 at 6:10 PM, Aaron C. de Bruyn > > wrote: > >> > >> You might try here: https://www.maxmind.com/en/correction > >> > >> -A > >> > >> On Tue, Apr 7, 2015 at 3:42 PM, Fred Hollis > wrote: > >> > Thanks for sending this to the list: We have the very same issue as > well > >> > (both IPv4+IPv6). If someone knows the magic button to solve this, > >> > please > >> > contact me as well. > >> > > >> > > >> > On 08.04.2015 at 00:26 John Levine 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, jo...@iecc.com, Primary Perpetrator of "The Internet > for > >> >> Dummies", > >> >> Please consider the environment before reading this e-mail. > >> >> http://jl.ly > >> >> > >> >> > >> > > > > > >
Re: Fixing Google geolocation screwups
I figure they all collaborate. I updated one of our IPs with MaxMind and a few weeks later Google was fixed. Of course that could be because half the staff here carry tiny GPS-enabled Google location reporting devices in their pocket too... -A On Tue, Apr 7, 2015 at 4:17 PM, Blair Trosper wrote: > No, Google has their own internal system. Doubt MaxMind will help out. > > This discussions and others like it may lead you in the right direction: > https://productforums.google.com/forum/#!topic/websearch/fkyem9xUKOQ > > On Tue, Apr 7, 2015 at 6:10 PM, Aaron C. de Bruyn > wrote: >> >> You might try here: https://www.maxmind.com/en/correction >> >> -A >> >> On Tue, Apr 7, 2015 at 3:42 PM, Fred Hollis wrote: >> > Thanks for sending this to the list: We have the very same issue as well >> > (both IPv4+IPv6). If someone knows the magic button to solve this, >> > please >> > contact me as well. >> > >> > >> > On 08.04.2015 at 00:26 John Levine 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, jo...@iecc.com, Primary Perpetrator of "The Internet for >> >> Dummies", >> >> Please consider the environment before reading this e-mail. >> >> http://jl.ly >> >> >> >> >> > > >
Re: Fixing Google geolocation screwups
No, Google has their own internal system. Doubt MaxMind will help out. This discussions and others like it may lead you in the right direction: https://productforums.google.com/forum/#!topic/websearch/fkyem9xUKOQ On Tue, Apr 7, 2015 at 6:10 PM, Aaron C. de Bruyn wrote: > You might try here: https://www.maxmind.com/en/correction > > -A > > On Tue, Apr 7, 2015 at 3:42 PM, Fred Hollis wrote: > > Thanks for sending this to the list: We have the very same issue as well > > (both IPv4+IPv6). If someone knows the magic button to solve this, please > > contact me as well. > > > > > > On 08.04.2015 at 00:26 John Levine 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, jo...@iecc.com, Primary Perpetrator of "The Internet for > >> Dummies", > >> Please consider the environment before reading this e-mail. > http://jl.ly > >> > >> > > >
Re: Fixing Google geolocation screwups
You might try here: https://www.maxmind.com/en/correction -A On Tue, Apr 7, 2015 at 3:42 PM, Fred Hollis wrote: > Thanks for sending this to the list: We have the very same issue as well > (both IPv4+IPv6). If someone knows the magic button to solve this, please > contact me as well. > > > On 08.04.2015 at 00:26 John Levine 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, jo...@iecc.com, Primary Perpetrator of "The Internet for >> Dummies", >> Please consider the environment before reading this e-mail. http://jl.ly >> >> >
Re: Fixing Google geolocation screwups
The list on http://nanog.peeringdb.com/index.php/GeoIP is useful, especially if several GeoIP databases return incorrect locations. -- Arzhel On Wed, Apr 8, 2015, at 10:42, Fred Hollis wrote: > Thanks for sending this to the list: We have the very same issue as well > (both IPv4+IPv6). If someone knows the magic button to solve this, > please contact me as well. > > On 08.04.2015 at 00:26 John Levine 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, jo...@iecc.com, Primary Perpetrator of "The Internet for > > Dummies", > > Please consider the environment before reading this e-mail. http://jl.ly > > > >
Re: Fixing Google geolocation screwups
Thanks for sending this to the list: We have the very same issue as well (both IPv4+IPv6). If someone knows the magic button to solve this, please contact me as well. On 08.04.2015 at 00:26 John Levine 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, jo...@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
Re: Fixing Google geolocation screwups
https://support.google.com/websearch/answer/873?hl=en On 7 April 2015 at 23:26, John Levine 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, jo...@iecc.com, Primary Perpetrator of "The Internet for > Dummies", > Please consider the environment before reading this e-mail. http://jl.ly > > >
