ixreport

DataKeepers

AS328170 · DataKeepers

DataKeepers (Pty) Ltd

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

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

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

PeeringDB fix list Printable page · CSV

One thing to fix in DataKeepers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on DataKeepers'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 (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 NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB196.60.70.211196.60.70.187 196.60.70.211
    IPv6 address missing from PeeringDB2001:43f8:6d1::2112001:43f8:6d1::187 2001:43f8:6d1::211
    Port speed differs10G2 × 10G
    • Add an entry: IPv4 196.60.70.187, IPv6 2001:43f8:6d1::187, speed 10000 (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.

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 DataKeepers'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 130G across 3 exchanges.

South Africa CINX Cape Town, South Africa 196.223.23.107 2001:43f8:1f1::1:107 100G 20 routes Both
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.211 2001:43f8:6d1::211 10G 12 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.9.218
196.60.10.33
2001:43f8:6d0::9:218
2001:43f8:6d0::10:33
2 × 10G 16 routes Both

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

These exchanges have a switch in a facility where DataKeepers lists itself in PeeringDB, but don't have DataKeepers 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 (3)

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