PhoenixNAP: PeeringDB fix list

AS12189 · peeringdb.com/net/2932

PeeringDB

4 things to fix in PhoenixNAP's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on PhoenixNAP's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (3)

On the exchange's own member list, but not in PhoenixNAP's PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214From its IX-F export and website members list
    IPv4185.1.170.69
    IPv62001:7f8:9e::2f9d:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list
    IPv4185.1.210.85
    IPv62001:7f8:3d::2f9d:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list
    IPv4185.1.208.78
    IPv62001:7f8:44::2f9d:0:1
    Speed100000 Mbps (100G)
    RS peerYes

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.

  1. United States Ninja-IX Phoenix Phoenix, United States · PeeringDB 662
    ProblemPeeringDB hasThe export has
    Port speed differs10G30G
    • In the entry with IPv4 206.41.105.31: set Speed to 30000 (30G) (now 10000).

From ixreport.com/net/12189/: 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.