[139887] in North American Network Operators' Group
RE: Youtube Geolocation
daemon@ATHENA.MIT.EDU (Mike Schoenfeld)
Thu Apr 21 18:29:44 2011
From: Mike Schoenfeld <Mike.Schoenfeld@mediatek.com>
To: Carl Rosevear <crosevear@skytap.com>, "nanog@nanog.org" <nanog@nanog.org>
Date: Thu, 21 Apr 2011 18:29:31 -0400
In-Reply-To: <BANLkTikBYotuOYwYUk7KXujW1Fzr1pVZ0g@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I don't know what Google uses but any company using F5 equipment is using =
Quova geolocation services=2E You can request updates and check your =
circuit here:
http://www=2Equova=2Ecom/what/request-ip-update/
The problem is that the F5 devices don't update the database files =
automatically, they need to be manually updated=2E Unless I get a specific=
request at my company I don't bother updating on a regular basis=2E
-Mike
-----Original Message-----
From: Carl Rosevear [mailto:crosevear@skytap=2Ecom]=20
Sent: Thursday, April 21, 2011 6:19 PM
To: nanog@nanog=2Eorg
Subject: Re: Youtube Geolocation
I have had this same problem, followed Google's forms, etc=2E=2E=2E they =
never seem to fix it=2E Its really annoying=2E
This is an epic fail on the part of Google in my opinion=2E My netblocks =
all show Seattle in whois=2E=2E=2E my routing is obviously here=2E=2E=2E =
I don't think we have an official address in the UK listed on anything=2E
How does Google get this information? Why don't they possibly ever do =
anything about it? It makes Google's properties perform abysmally to a =
large percentage of our customer base=2E And then we get blamed for it=2E
And Google does nothing, even after submitting the web form that clearly =
states that they will not get back to us about it but will try to resolve =
the issue=2E Its quite hideous really=2E Its in everyone's worst =
interest=2E How about maybe trusting my whois data? If whois data leads =
to incorrect results then it is in the netblock owners' best interest to =
update the whois data if they want to be directed efficiently with gslb/etc=
that uses whois data as the source=2E
And I've been working with ip-geo stuff for years=2E=2E=2E I understand =
that a lot of effort has gone into making it "better" than the whois =
data=2E=2E=2E but every other freaking IP geolocator I type my IP into =
properly recognizes the addresses are in Seattle=2E=2E=2E why not Google?
Anyway, I at the very least commiserate with you if I'm not perhaps making =
some passive-aggressive cry for help from Google or anyone else with a clue=
bat about this issue=2E :) Thanks!
--C
On Thu, Apr 21, 2011 at 2:36 PM, Dan White <dwhite@olp=2Enet> wrote:
> We're experiencing very poor quality with You Tube, and it appears=20
> we're subject to a bad entry within a geolocation database somewhere=2E
>
> When we attempt to view videos, the contact comes back to us from IPs =
like:
>
> 208=2E117=2E226=2E21 (traceroute's through Frankfurt)
> 173=2E194=2E50=2E47
> 74=2E125=2E100=2E29
>
> All of those IPs are >125ms away from us (67=2E217=2E144=2E0/20, and=20
> 216=2E14=2E144=2E0/20)=2E
>
> However, we've never experienced redirection problems with Google=20
> before (we always land at www=2Egoogle=2Ecom), so I'm not sure where to=
=20
> take our trouble=2E The page at:
>
> =
http://www=2Egoogle=2Ecom/support/websearch/bin/request=2Epy?contact_type=3D=
ip
>
> isn't of much help as it assumes the problem is google=2Ecom =
redirection=2E
>
> Are there any contacts at Youtube who could provide some assistance?
>
> Thanks,
> --
> Dan White
>
>
--
Carl Rosevear
Manager of Operations
Skytap, Inc=2E
direct (206) 588-8899
************* Email Confidentiality Notice ********************
The information contained in this e-mail message (including any=20
attachments) may be confidential, proprietary, privileged, or otherwise
exempt from disclosure under applicable laws=2E It is intended to be=20
conveyed only to the designated recipient(s)=2E Any use, dissemination,=20
distribution, printing, retaining or copying of this e-mail (including its=
=20
attachments) by unintended recipient(s) is strictly prohibited and may=20
be unlawful=2E If you are not an intended recipient of this e-mail, or =
believe=20
that you have received this e-mail in error, please notify the sender=20
immediately (by replying to this e-mail), delete any and all copies of=20
this e-mail (including any attachments) from your system, and do not
disclose the content of this e-mail to any other person=2E Thank you!
