How to Fix IP GEO for google/youtube tv

Thu Mar 11 19:39:57 UTC 2021

>
> Based on how difficult it is to correct their data for them at no charge,
> I'm not sure he's entirely wrong in that statement.
>

No, it's still wrong.

Stating that Google's team 'doesn't want to improve things' , while also
having zero knowledge of the reasons why the current issues are present, is
at best uninformed , and at worst just plain ignorant.

On Thu, Mar 11, 2021 at 2:29 PM Josh Luthman <josh at imaginenetworksllc.com>
wrote:

> Based on how difficult it is to correct their data for them at no charge,
> I'm not sure he's entirely wrong in that statement.
>
> The fact that this thread exists, the latest of multiple, and has ended in
> no resolution to the problem once again is a testament to how Google
> responds to this problem.
>
> Josh Luthman
> 24/7 Help Desk: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
>
> On Thu, Mar 11, 2021 at 12:23 PM Grant Taylor via NANOG <nanog at nanog.org>
> wrote:
>
>> On 3/11/21 2:36 AM, William Guo wrote:
>> > but they don't wanna improve it for some reason.
>>
>> That is both unfair and wrong.
>>
>> I know for a fact that they do want their internal GeoIP to be as
>> accurate as possible and that they do want to improve the inaccuracies
>> if and when possible.
>>
>> I have personally submitted a handful of GeoIP changes through channels.
>>   It does take a wile O(weeks) to complete.  But it /does/ complete.
>>
>> If you have a GGC node, you can reach out to the GGC operations team for
>> help resolving GeoIP issues.  Ostensibly the GGC operations team focuses
>> on GGC related issues.  But they should be able to document the issue
>> and send it to proper internal teams anyway.
>>
>> I would assume that Google's NOC can also re-route issues as necessary.
>>
>> I believe that saying "they don't wanna improve" as a fact, vs an
>> opinion, is disingenuous and somewhat rude.
>>
>>
>>
>> --
>> Grant. . . .
>> unix || die
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20210311/e545868a/attachment.html>