Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

[Marijana Novakovic via NANOG <nanog () nanog org>]

Greetings Jason,

Thank you for your kind feedback, we have CM planned for today to do the needed change.

Kind regards, Mara


________________________________
From: NANOG <nanog-bounces () nanog org> on behalf of Mike Hammett <nanog () ics-il net>
Sent: Wednesday, January 30, 2019 8:41 AM
To: Jason Lixfeld
Cc: North American Network Operators' Group
Subject: Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

A lot of huge companies apparently find it tough to find the $75k to hire one more peering person. Not all, though. For 
many, everything just runs like clockwork.



-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com

Midwest-IX
http://www.midwest-ix.com

________________________________
From: "Jason Lixfeld" <jason+nanog () lixfeld ca>
To: "North American Network Operators' Group" <nanog () nanog org>
Sent: Wednesday, January 30, 2019 7:52:09 AM
Subject: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Hi,

In late October 2018, DE-CIX announced that they would be renumbering their IPv4 address block in New York between 
01-28-19 and 01-30-19.

This was followed by numerous reminders in months, weeks and even days leading up to the renumbering activity.

The renumbering activity has come and gone, but LinkedIn, Amazon and Akamai are still using the old IPs.

If three months has gone by and the numerous reminders that have been sent have resulted in these organizations still 
living on the old IP space, it seems to me that there may be some sort of a disconnect between who receives the 
notifications from IXPs and how they are filtered upstream.

I’m hopeful that the eyeballs who read this list are some of those folks who should have received the notifications 
from DE-CIX, or can at least filter the info back downstream to whoever can perform the renumbering activity.

Thanks.