PacketFabric: PeeringDB fix list

AS4556 · peeringdb.com/net/10802

PeeringDB

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

Make the changes on PacketFabric'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. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 206.82.104.179: set Speed to 200000 (200G) (now 100000).

Check these entries (1)

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

  1. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249Not on its IX-F export or website members list
    IPv4206.53.202.38
    IPv62001:504:61::11cc:0:1
    Speed100000 Mbps (100G)

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