C. Steinweg Bridge: PeeringDB fix list

AS328894 · peeringdb.com/net/27816

PeeringDB

2 things to fix in C. Steinweg Bridge'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 C. Steinweg Bridge'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 C. Steinweg Bridge's PeeringDB record. Add one entry per connection with these values.

  1. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its IX-F export and website members list
    IPv4196.60.11.80
    IPv62001:43f8:6d0::11:80
    Speed20000 Mbps (20G)
    RS peerYes

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

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. South Africa NAPAfrica MAPS Johannesburg Johannesburg, South Africa · PeeringDB 3403
    ProblemPeeringDB hasThe export has
    Port speed differs1G20G
    • In the entry with IPv4 196.46.25.156: set Speed to 20000 (20G) (now 1000).

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