DE-CIX New York Route Servers: PeeringDB fix list
AS63034 · peeringdb.com/net/6978
One thing to fix in DE-CIX New York Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on DE-CIX New York Route Servers's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 206.82.104.254 206.82.106.254 206.82.104.66 206.82.104.254 206.82.106.254 IPv6 address missing from PeeringDB 2001:504:36::f63a:afc:1 2001:504:36::f63a:afd:1 2001:504:36::f63a:63:34 2001:504:36::f63a:afc:1 2001:504:36::f63a:afd:1 Port speed differs 2 × 1G 3 × 20G - In the entry with IPv4 206.82.104.254: set Speed to 20000 (20G) (now 1000).
- In the entry with IPv4 206.82.106.254: set Speed to 20000 (20G) (now 1000).
- Add an entry: IPv4 206.82.104.66, IPv6 2001:504:36::f63a:63:34, speed 20000 (20G), RS peer no.
From ixreport.com/net/63034/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.