Mimecast South Africa: PeeringDB fix list
AS37235 · peeringdb.com/net/4396
2 things to fix in Mimecast South Africa'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 Mimecast 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 Mimecast 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.96.70 196.60.96.170 196.60.96.70 196.60.96.170 196.60.97.71 IPv6 address missing from PeeringDB 2001:43f8:1f0::70 2001:43f8:1f0::170 2001:43f8:1f0::70 2001:43f8:1f0::170 2001:43f8:1f0::1:71 Port speed differs 2 × 10G 2 × 100G + 10G - In the entry with IPv4 196.60.96.70: set Speed to 100000 (100G) (now 10000).
- Add an entry: IPv4 196.60.97.71, IPv6 2001:43f8:1f0::1:71, speed 100000 (100G), 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/37235/: 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.