POLOPRO: PeeringDB fix list
AS208824 · peeringdb.com/net/39260
2 things to fix in POLOPRO's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on POLOPRO'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 POLOPRO's PeeringDB record. Add one entry per connection with these values.
-
IPv4 – IPv6 2001:7f8:ca:1:0:20:8824:1 Speed 1000 Mbps (1G) RS peer Yes 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 149.112.50.132 - In the entry with IPv6 2001:504:125:e1::aaec: set IPv4 to 149.112.50.132 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/208824/: 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.