ixreport

BCIX Route Servers: PeeringDB fix list

AS16374 · peeringdb.com/net/11967

One thing to fix in BCIX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on BCIX Route Servers'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.

  1. Germany BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.178.185.5 193.178.185.6193.178.185.5 193.178.185.6 193.178.185.7 193.178.185.250 193.178.185.251
    IPv6 address missing from PeeringDB2001:7f8:19:1::3ff6:5 2001:7f8:19:1::3ff6:62001:7f8:19:1::3ff6:5 2001:7f8:19:1::3ff6:6 2001:7f8:19:1::3ff6:7 2001:7f8:19:1::3ff6:fa 2001:7f8:19:1::3ff6:fb
    Port speed differs2 × 10G2 × 200G + 3 × 10G
    • Add an entry: IPv4 193.178.185.7, IPv6 2001:7f8:19:1::3ff6:7, speed 10000 (10G), RS peer no.
    • Add an entry: IPv4 193.178.185.251, IPv6 2001:7f8:19:1::3ff6:fb, speed 200000 (200G), RS peer no.
    • Add an entry: IPv4 193.178.185.250, IPv6 2001:7f8:19:1::3ff6:fa, speed 200000 (200G), 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/16374/: 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.