ixreport

SADV

AS37049 · SA Digital Villages

6Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
6Using the route servers
3To fix in PeeringDB
6Facilities in PeeringDB

Tools: Where can I peer with SADV? · Where should SADV peer next? · Compare SADV with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in SADV's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on SADV's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (3)

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 CINX Cape Town, South Africa · PeeringDB 344
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 196.223.22.196: set Speed to 20000 (20G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 20G
    • In the entry with IPv4 196.60.70.196: set Speed to 20000 (20G) (now 10000).
    • In the entry with IPv4 196.60.71.136: set Speed to 20000 (20G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs100G + 20G2 × 100G
    • In the entry with IPv4 196.60.8.196: set Speed to 100000 (100G) (now 20000).

    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

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

Map

Where SADV'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 210G across 6 exchanges.

South Africa CINX Cape Town, South Africa 196.223.22.196 2001:43f8:1f1::196 10G 9 routes Both Speed differs
South Africa DINX Durban, South Africa 196.223.30.196
196.223.31.196
2001:43f8:1f2::196
2001:43f8:1f2::1:196
2 × 10G 10 routes Both
South Africa JINX Johannesburg, South Africa 196.60.96.196 2001:43f8:1f0::196 20G 5 routes Both
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.196
196.60.71.136
2001:43f8:6d1::196
2001:43f8:6d1::71:136
2 × 10G 18 routes Both Speed differs
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.166
196.10.141.196
2001:43f8:6d2::166
2001:43f8:6d2::196
2 × 10G 48 routes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.196
196.60.11.24
2001:43f8:6d0::196
2001:43f8:6d0::11:24
100G + 20G 102 routes Both Speed differs

Exchanges in its buildings that it isn't on (4)

These exchanges have a switch in a facility where SADV lists itself in PeeringDB, but don't have SADV as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (6)

The buildings SADV lists in PeeringDB, and how many of the exchanges in each it's on.