ixreport

NS3: PeeringDB fix list

AS39479 · peeringdb.com/net/16429

PeeringDB

2 things to fix in NS3's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on NS3'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.

  1. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs20G20G + 10G
    • In the entry with IPv4 217.29.67.169: set Speed to 10000 (10G) (now 20000).
    • Add an entry: IPv4 217.29.67.169, IPv6 –, speed 20000 (20G), RS peer yes.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If NS3 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Italy PCIX Piacenza, Italy · PeeringDB 1933Not on its IX-F export
    IPv4185.1.97.44
    IPv62001:7f8:b9::44:1
    Speed10000 Mbps (10G)

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