DCC-BG: PeeringDB fix list
AS51582 · peeringdb.com/net/35911
3 things to fix in DCC-BG's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on DCC-BG'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 (3)
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.197 193.169.199.73 193.169.198.196 193.169.198.197 193.169.199.73 - In the entry with IPv4 193.169.199.73: set IPv4 to 193.169.198.196 (now 193.169.199.73).
- Add an entry: IPv4 193.169.199.73, IPv6 –.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2a03:5f80:4:2::236:117 - In the entry with IPv4 178.18.236.117: set IPv6 to 2a03:5f80:4:2::236:117 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 91.212.235.53 91.212.235.10 91.212.235.53 IPv6 address missing from PeeringDB none 2001:7f8:9f::a 2001:7f8:9f::a5:1582:2 - In the entry with IPv4 91.212.235.53: set IPv6 to 2001:7f8:9f::a5:1582:2 (now empty).
- Add an entry: IPv4 91.212.235.10, IPv6 2001:7f8:9f::a, RS peer no.
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/51582/: 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.