nanog mailing list archives
Re: Fixing Google geolocation screwups
From: Bryan Socha <bryan () digitalocean com>
Date: Sat, 16 May 2015 15:22:59 -0400
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
Current thread:
- RE: Fixing Google geolocation screwups Matthew Black (May 05)
- Re: Fixing Google geolocation screwups Pedro Cavaca (May 05)
- Re: Fixing Google geolocation screwups Luan Nguyen (May 05)
- Re: Fixing Google geolocation screwups Matt Palmer (May 05)
- Re: Fixing Google geolocation screwups Mark Andrews (May 05)
- Re: Fixing Google geolocation screwups Matt Palmer (May 05)
- Re: Fixing Google geolocation screwups Fred Hollis (May 06)
- Re: Fixing Google geolocation screwups Christopher Morrow (May 06)
- Re: Fixing Google geolocation screwups Bryan Socha (May 16)
- Re: Fixing Google geolocation screwups Matt Palmer (May 05)