BICS: PeeringDB fix list
AS6774 · peeringdb.com/net/150
10 things to fix in BICS's PeeringDB record, from what its exchanges publish: 4 to add, 6 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on BICS'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 (4)
On the exchange's own member list, but not in BICS's PeeringDB record. Add one entry per connection with these values.
-
Hopus Paris, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France · PeeringDB 1320From its website members listThe exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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.
-
IPv4 149.112.104.41 IPv6 2001:504:a::a500:6774:1 Speed Not published RS peer Not published
Correct these entries (6)
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 Port speed differs 100G + 99G 3 × 100G + 99G 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.
-
Problem PeeringDB has The export has Port speed differs 10G 10G + 1G 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.
-
Problem PeeringDB has The export has Port speed differs 4G 10G - In the entry with IPv4 103.162.254.67: set Speed to 10000 (10G) (now 4000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 196.223.21.77: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 50G + 20G 30G + 20G - In the entry with IPv4 195.66.224.128: set Speed to 30000 (30G) (now 50000).
-
Problem PeeringDB has The export has Port speed differs 1G 5G - In the entry with IPv4 196.60.114.5: set Speed to 5000 (5G) (now 1000).
From ixreport.com/net/6774/: 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.