datamena: PeeringDB fix list
AS57187 · peeringdb.com/net/5352
One thing to fix in datamena's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on datamena'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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 185.1.8.17 185.1.8.104 185.1.8.17 185.1.8.104 185.1.8.135 IPv6 address missing from PeeringDB 2001:7f8:73::df63:0:2 2001:7f8:73::df63:0:3 2001:7f8:73::df63:0:1 2001:7f8:73::df63:0:2 2001:7f8:73::df63:0:3 Port speed differs 2 × 100G 3 × 200G - In the entry with IPv4 185.1.8.104: set Speed to 200000 (200G) (now 100000).
- In the entry with IPv4 185.1.8.17: set Speed to 200000 (200G) (now 100000).
- Add an entry: IPv4 185.1.8.135, IPv6 2001:7f8:73::df63:0:1, speed 200000 (200G), RS peer no.
From ixreport.com/net/57187/: 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.