CM.com Netherlands B.V.: PeeringDB fix list

AS15447 · peeringdb.com/net/8241

4 things to fix in CM.com Netherlands B.V.'s PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on CM.com Netherlands B.V.'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 (4)

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.

DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214

Problem PeeringDB has The export has

Port speed differs 1G 10G
- In the entry with IPv4 185.1.170.205: set Speed to 10000 (10G) (now 1000).
DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31

Problem PeeringDB has The export has

Port speed differs 1G 10G
- In the entry with IPv4 80.81.196.160: set Speed to 10000 (10G) (now 1000).
DE-CIX Hamburg Hamburg, Germany · PeeringDB 74

Problem PeeringDB has The export has

Port speed differs 1G 10G
- In the entry with IPv4 185.1.210.183: set Speed to 10000 (10G) (now 1000).
DE-CIX Munich Munich, Germany · PeeringDB 248

Problem PeeringDB has The export has

Port speed differs 1G 10G
- In the entry with IPv4 185.1.208.190: set Speed to 10000 (10G) (now 1000).

Problem	PeeringDB has	The export has
Port speed differs	1G	10G

Problem	PeeringDB has	The export has
Port speed differs	1G	10G

Problem	PeeringDB has	The export has
Port speed differs	1G	10G

Problem	PeeringDB has	The export has
Port speed differs	1G	10G

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