BGN: PeeringDB fix list
AS215366 · peeringdb.com/net/35779
2 things to fix in BGN's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on BGN'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 BGN's PeeringDB record. Add one entry per connection with these values.
-
IPv4 193.188.137.215 IPv6 2001:7f8:35::21:5366:1 Speed 10000 Mbps (10G) RS peer Yes
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 IPv6 address missing from PeeringDB none 2a03:5f80:4:2::236:157 - In the entry with IPv4 178.18.236.157: set IPv6 to 2a03:5f80:4:2::236:157 (now empty).
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/215366/: 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.