NETGUARD: PeeringDB fix list
AS39251 · peeringdb.com/net/15970
2 things to fix in NETGUARD's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on NETGUARD'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 (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 IPv4 address missing from PeeringDB 193.169.198.210 193.169.198.210 193.169.198.211 IPv6 address missing from PeeringDB 2001:7f8:58::9953:0:1 2001:7f8:58::9953:0:1 2001:7f8:58::9953:0:2 - Add an entry: IPv4 193.169.198.211, IPv6 2001:7f8:58::9953:0:2.
-
Problem PeeringDB has The export has Port speed differs 4 × 10G 10G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
From ixreport.com/net/39251/: 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.