[189590] in North American Network Operators' Group
Re: Google GeoIP issue
daemon@ATHENA.MIT.EDU (Richard Hesse)
Thu Jun 2 18:26:16 2016
X-Original-To: nanog@nanog.org
In-Reply-To: <6CA1AC26-D729-4A96-9143-BAEC327D9564@gmail.com>
Date: Thu, 2 Jun 2016 15:26:12 -0700
From: Richard Hesse <richard.hesse@weebly.com>
To: NANOG Mailing List <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
If you have peering relationship with Google, you can use the isp.google.co=
m
portal to self-publish geo information on your netblocks. At least you can
in theory. By their own admission, they have never checked the
self-published URL that I configured over a month ago.
YMMV.
-richard
On Thu, Jun 2, 2016 at 6:19 AM, Maxwell Cole <mcole.mailinglists@gmail.com>
wrote:
> Heya,
>
> Im in the same boat if anyone from google wants to be a dear and help out=
.
>
> Cheers,
> > On Jun 1, 2016, at 6:28 PM, Chris Boyd <cboyd@gizmopartners.com> wrote:
> >
> > I too am having a similar problem. Used the remediation link at
> https://support.google.com/websearch/contact/ip and it=E2=80=99s only par=
tially
> corrected. Users who log in to Google are seeing the US google.com page
> after they select the preferred country and languate, but everyone else i=
s
> still getting google.ae. 208.81.245.226 is in Austin, TX.
> >
> > =E2=80=94Chris
> >
> >> On Jun 1, 2016, at 5:17 PM, Peter Loron <peterl@standingwave.org>
> wrote:
> >>
> >> Hello folks. An address we use is not identified as being in the
> correct location by Google. Can someone from their NOC reach out off-list=
?
> >>
> >> Thanks.
> >>
> >>
> >> Sent from my iPhone
> >>
> >
>
>
