X-ION: PeeringDB fix list

AS60664 · peeringdb.com/net/32214

PeeringDB

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

Make the changes on X-ION'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 (1)

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

  1. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26From its IX-F export and website members list
    IPv480.249.213.129
    IPv62001:7f8:1::a506:664:1
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:3d::ecf8:0:1
    Port speed differs10G100G
    • In the entry with IPv4 185.1.210.38: set IPv6 to 2001:7f8:3d::ecf8:0:1 (now empty); set Speed to 100000 (100G) (now 10000).

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