DataKeepers
AS328170 · DataKeepers
DataKeepers (Pty) Ltd
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 196.60.70.211 196.60.70.187 196.60.70.211 IPv6 address missing from PeeringDB 2001:43f8:6d1::211 2001:43f8:6d1::187 2001:43f8:6d1::211 Port speed differs 10G 2 × 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 3 |
| Oct 26, 2026 | 3 |
| Oct 25, 2026 | 3 |
| Oct 24, 2026 | 3 |
| Oct 23, 2026 | 3 |
| Oct 22, 2026 | 3 |
| Oct 21, 2026 | 3 |
| Oct 20, 2026 | 3 |
| Oct 19, 2026 | 3 |
| Oct 18, 2026 | 3 |
| Oct 17, 2026 | 3 |
| Oct 16, 2026 | 3 |
| Oct 15, 2026 | 3 |
| Oct 14, 2026 | 3 |
| Oct 13, 2026 | 3 |
| Oct 12, 2026 | 3 |
| Oct 11, 2026 | 3 |
| Oct 10, 2026 | 3 |
| Oct 9, 2026 | 3 |
| Oct 8, 2026 | 3 |
| Oct 7, 2026 | 3 |
| Oct 6, 2026 | 3 |
| Oct 5, 2026 | 3 |
| Oct 4, 2026 | 3 |
| Oct 3, 2026 | 3 |
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.
| CINX Cape Town, South Africa | 100G | Both | |
| NAPAfrica IX Cape Town Cape Town, South Africa | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 2 × 10G | Both |
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.
| JINXJohannesburg, South Africa | 215 | |
| NetIXSofia, Bulgaria | 204 | |
| NAPAfrica MAPS JohannesburgJohannesburg, South Africa | 31 | |
| Global Peer ExchangeWashington, United States | 6 | |
| JINX VoiceJohannesburg, South Africa | 4 |
Facilities (3)
The buildings DataKeepers lists in PeeringDB, and how many of the exchanges in each it's on.
| Teraco Johannesburg Campus, South AfricaJohannesburg | 1 of 6 | |
| Teraco CT1 Cape Town, South AfricaCape Town | 2 of 3 | |
| Africa Data Centres, Cape Town CPT1, South AfricaCape Town | 1 of 1 |