Google Geo Location Issues
hank at interall.co.il
Thu Jul 1 06:58:54 UTC 2021
On 30/06/2021 17:43, Jason Kuehl wrote:
Once you have access to isp.google.com your problems are far from over.
You would assume that they would use whois info to know which prefix
belongs to your ASN. That would be wrong. If you have, for example, a
multi-homed customer and you provided them with a smaller prefix (/27)
from within your larger prefix (/19), and since they are multihomed some
other ASN announces that smaller prefix (/27), Google will see that and
invalidate any geo-location info you provide for your /19. Google
follows the BGP routing table as authoritative for ownership of prefixes.
Caveat: The views expressed above are solely my own and do not express
the views or opinions of my employer
> This is want I'm working on setting up, here is hoping they approve my
> On Wed, Jun 30, 2021 at 10:30 AM Benjamin Hatton <bhatton at htva.net
> <mailto:bhatton at htva.net>> wrote:
> If they are your subnets, and you have your own AS (and possibly
> enough traffic to Google, I'm not sure what exactly their criteria
> is but we were able to make an account with ~2Gbps peak and no
> peering relationships) you can create an account with the Google ISP
> Portal (isp.google.com <http://isp.google.com>) which has a self
> service tool to upload a csv that will update your prefixes in the
> Google IP Geolocation database. Took ~2 weeks after upload for it
> to be reflected in live data.
> *Ben Hatton*
> *Network Engineer | Haefele Connect*
> d:(607)589-8000 | ben at haefeleconnect.com <mailto:ben at haefeleconnect.com>
> On Wed, Jun 30, 2021 at 10:21 AM Nate Burke <nate at blastcomm.com
> <mailto:nate at blastcomm.com>> wrote:
> Same here, YoutubeTV Geolocation problem, has one of my subnets
> in Tulsa instead of Chicago. Ticket open for 8 months. Every
> reply was that it was 'with engineering' and no ETA. I just got
> a notice from them last week that they're closing the ticket and
> sent a survey to fill out to rate the support received. I told
> them that the issue was still not resolved and never heard back
> from them.
> On 6/30/2021 8:55 AM, Josh Luthman wrote:
>> Been months since I was told they'd get it fixed. To be fair
>> they did say they weren't sure on how long it would take. I
>> feel like I've been forgotten about.
>> Josh Luthman
>> 24/7 Help Desk: 937-552-2340
>> Direct: 937-552-2343
>> 1100 Wayne St
>> Suite 1337
>> Troy, OH 45373
>> On Wed, Jun 30, 2021 at 9:18 AM Mike Hammett <nanog at ics-il.net
>> <mailto:nanog at ics-il.net>> wrote:
>> I've discovered that if you *CAN* get a Google ISP
>> account, you can manage it all there.
>> If you can't, well, you're up shit creek without a paddle.
>> Mike Hammett
>> Intelligent Computing Solutions
>> http://www.ics-il.com <http://www.ics-il.com>
>> http://www.midwest-ix.com <http://www.midwest-ix.com>
>> *From: *"Jason Kuehl" <jason.w.kuehl at gmail.com
>> <mailto:jason.w.kuehl at gmail.com>>
>> *To: *"NANOG" <nanog at nanog.org <mailto:nanog at nanog.org>>
>> *Sent: *Tuesday, June 29, 2021 6:25:06 PM
>> *Subject: *Google Geo Location Issues
>> I'm looking for a contact, email, number, smoke signals
>> for someone at Google I can talk to on geolocation issue.
>> For some reason Google has labeled our IP ranges
>> as Belarus when we're located in the states. If anyone can
>> point me at any contact I would be really happy..
>> Jason W Kuehl
>> Cell 920-419-8983
>> jason.w.kuehl at gmail.com <mailto:jason.w.kuehl at gmail.com>
> Jason W Kuehl
> Cell 920-419-8983
> jason.w.kuehl at gmail.com <mailto:jason.w.kuehl at gmail.com>
More information about the NANOG