ixreport

Mimecast South Africa

AS37235 · Mimecast

3Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
2Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Mimecast South Africa? · Where should Mimecast South Africa peer next? · Compare Mimecast South Africa with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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-11-19 12:40 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.

  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 JINX Johannesburg, South Africa · PeeringDB 129
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB196.60.96.70 196.60.96.170196.60.96.70 196.60.96.170 196.60.97.71
    IPv6 address missing from PeeringDB2001:43f8:1f0::70 2001:43f8:1f0::1702001:43f8:1f0::70 2001:43f8:1f0::170 2001:43f8:1f0::1:71
    Port speed differs2 × 10G2 × 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.

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where Mimecast South Africa's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 30G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

South Africa JINX Johannesburg, South Africa 196.60.96.70
196.60.96.170
2001:43f8:1f0::70
2001:43f8:1f0::170
2 × 10G 25 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.71.154 2001:43f8:6d1::71:154 10G Yes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa Website list only

Mimecast South Africa lists no facilities in PeeringDB.