binsec: PeeringDB fix list
AS206423 · peeringdb.com/net/15548
One thing to fix in binsec's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on binsec'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 193.189.82.206 193.189.82.206 193.189.83.202 IPv6 address missing from PeeringDB 2001:7f8:33::a120:6423:1 2001:7f8:33::a120:6423:1 2001:7f8:33::a120:6423:2 - Add an entry: IPv4 193.189.83.202, IPv6 2001:7f8:33::a120:6423:2, speed 200 (200M), 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.
From ixreport.com/net/206423/: 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.