Ring a Nerd cc: PeeringDB fix list

AS329049 · peeringdb.com/net/30011

PeeringDB

2 things to fix in Ring a Nerd cc'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 Ring a Nerd cc'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 Ring a Nerd cc's PeeringDB record. Add one entry per connection with these values.

  1. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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 IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d1::71:93
    • In the entry with IPv4 196.60.71.93: set IPv6 to 2001:43f8:6d1::71:93 (now empty).

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