ixreport

Tracker Connect

AS328417 · Tracker

Tracker Connect (Pty) Ltd

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

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

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

PeeringDB fix list Printable page · CSV

2 things to fix in Tracker Connect's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Tracker Connect'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 (2)

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
    IPv6 address missing from PeeringDBnone2001:43f8:1f0::1:47
    • In the entry with IPv4 196.60.97.47: set IPv6 to 2001:43f8:1f0::1:47 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::9:4 2001:43f8:6d0::10:64
    • In the entry with IPv4 196.60.10.64: set IPv6 to 2001:43f8:6d0::10:64 (now empty).
    • In the entry with IPv4 196.60.9.4: set IPv6 to 2001:43f8:6d0::9:4 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

Map

Where Tracker Connect'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 40G across 2 exchanges.

South Africa JINX Johannesburg, South Africa 196.60.97.47 10G 6 routes Both IPv6 not in PeeringDB
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.9.4
196.60.10.64
20G + 10G 6 routes Both IPv6 not in PeeringDB

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

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

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

South Africa Teraco Johannesburg Campus, South AfricaJohannesburg 2 of 6
South Africa Africa Data Centres, Johannesburg JHB2, South AfricaSamrand 1 of 1