Connected Space: PeeringDB fix list
AS328431 · peeringdb.com/net/19493
2 things to fix in Connected Space'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 Connected Space'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 Connected Space's PeeringDB record. Add one entry per connection with these values.
-
NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its IX-F export and website members listIPv4 196.60.9.243 IPv6 2001:43f8:6d0::9:243 Speed 10000 Mbps (10G) RS peer Yes 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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:43f8:6d1::207 2001:43f8:6d1::208 - In the entry with IPv4 196.60.70.207: set IPv6 to 2001:43f8:6d1::207 (now empty).
- In the entry with IPv4 196.60.70.208: set IPv6 to 2001:43f8:6d1::208 (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/328431/: 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.