Sportpesa South Africa: PeeringDB fix list
AS328260 · peeringdb.com/net/17865
2 things to fix in Sportpesa South Africa's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Sportpesa South Africa'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 Sportpesa South Africa's PeeringDB record. Add one entry per connection with these values.
-
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 196.60.70.161 196.60.70.161 196.60.70.162 IPv6 address missing from PeeringDB none 2001:43f8:6d1::161 2001:43f8:6d1::162 Port speed differs 1G 2 × 1G - In the entry with IPv4 196.60.70.161: set IPv6 to 2001:43f8:6d1::161 (now empty).
- Add an entry: IPv4 196.60.70.162, IPv6 2001:43f8:6d1::162, speed 1000 (1G), 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.
From ixreport.com/net/328260/: 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.