ColocationIX: PeeringDB fix list
AS61955 · peeringdb.com/net/6724
6 things to fix in ColocationIX's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct, 2 to check. As of 2026-10-08 22:13 UTC.
Make the changes on ColocationIX'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 (2)
On the exchange's own member list, but not in ColocationIX's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its website members listIPv4 185.1.32.136 IPv6 2001:7f8:8f::a506:1955:1 Speed Not published RS peer Not published
Correct these entries (2)
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 Port speed differs 10G 2G - In the entry with IPv4 193.178.185.127: set Speed to 2000 (2G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 1.25G - In the entry with IPv4 185.0.20.134: set Speed to 1250 (1.25G) (now 10000).
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If ColocationIX has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 194.68.128.46 IPv6 2001:7f8:d:fe::46 Speed 10000 Mbps (10G) -
IPv4 194.68.123.46 IPv6 2001:7f8:d:ff::46 Speed 10000 Mbps (10G)
From ixreport.com/net/61955/: 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.