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

["Neil J. McRae" <neil () domino org>]

+1!

On 30/01/2019, 22:10, "NANOG on behalf of Ren Provo" <nanog-bounces () nanog org<mailto:nanog-bounces () nanog org> on 
behalf of ren.provo () gmail com<mailto:ren.provo () gmail com>> wrote:

Hi Thomas,

You probably should remove sessions with networks explicitly *not* participating in route servers versus displaying 
them on a global shame list.

Cheers, -ren

On Wed, Jan 30, 2019 at 5:06 PM Thomas King <thomas.king () de-cix net<mailto:thomas.king () de-cix net>> wrote:
Hi all,

Thanks for your support! This helps us getting all peers on the new IPv4 space.

Our looking glass shows which peers already have changed the IP settings (see section “BGP session established”) and 
which peers are still working on it (see section “BGP sessions down”):
https://lg.de-cix.net/routeservers/rs1_nyc_ipv4#sessions-up

Best regards,
Thomas


From: NANOG <nanog-bounces () nanog org<mailto:nanog-bounces () nanog org>> on behalf of James Stankiewicz <stankiewicz 
() njedge net<mailto:stankiewicz () njedge net>>
Date: Wednesday, 30. January 2019 at 19:32
To: Jared Mauch <jared () puck nether net<mailto:jared () puck nether net>>
Cc: North American Network Operators' Group <nanog () nanog org<mailto:nanog () nanog org>>
Subject: Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Microsoft an Edgecast has not yet made there changes.

On Wed, Jan 30, 2019 at 12:20 PM Jared Mauch <jared () puck nether net<mailto:jared () puck nether net>> wrote:
Akamai is working on doing our part. Apologies.
Sent from my iCar

On Jan 30, 2019, at 12:02 PM, Mehmet Akcin <mehmet () akcin net<mailto:mehmet () akcin net>> wrote:
Pinged my contacts in each

On Wed, Jan 30, 2019 at 05:52 Jason Lixfeld <jason+nanog () lixfeld ca<mailto:jason%2Bnanog () lixfeld ca>> wrote:
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.
--
Mehmet
+1-424-298-1903


--
Jim Stankiewicz
Principal Network Architect
NJEdge
W:855.832.EDGE(3343)
c:201.306.4409
[https://docs.google.com/uc?export=download&id=0B15Cb24EwZVsOUhIa0lWbG9ZT2c&revid=0B15Cb24EwZVsdVB2SlJ3ekFEUllPRDZyMGZ5cUtkbko2bWQ0PQ]