BWC: PeeringDB fix list

AS50187 · peeringdb.com/net/42557

PeeringDB

2 things to fix in BWC's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 20:58 UTC.

Make the changes on BWC'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 (2)

On the exchange's own member list, but not in BWC's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.233.34
    IPv62a03:5f80:4:1::233:34
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.233.33
    IPv62a03:5f80:4:1::233:33
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Russia MSK-IX Novosibirsk Novosibirsk, Russia · PeeringDB 223From its IX-F export

    2 connections, so 2 entries:

    IPv4193.232.87.114
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4193.232.87.113
    IPv6–
    SpeedNot published
    RS peerYes

    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/50187/: 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.