ixreport

Cell C

AS37168 · Cell C

Cell C (Pty) Ltd

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Cell C'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 (6)

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
    IPv6 address missing from PeeringDBnone2001:43f8:1f1::59
    • In the entry with IPv4 196.223.22.59: set IPv6 to 2001:43f8:1f1::59 (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 DINX Durban, South Africa · PeeringDB 610
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:1f2::59
    • In the entry with IPv4 196.223.30.59: set IPv6 to 2001:43f8:1f2::59 (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.

  3. South Africa JINX Johannesburg, South Africa · PeeringDB 129
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:1f0::59 2001:43f8:1f0::124
    • In the entry with IPv4 196.60.96.124: set IPv6 to 2001:43f8:1f0::124 (now empty).
    • In the entry with IPv4 196.60.96.59: set IPv6 to 2001:43f8:1f0::59 (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.

  4. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d1::186
    • In the entry with IPv4 196.60.70.186: set IPv6 to 2001:43f8:6d1::186 (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.

  5. South Africa NAPAfrica IX Durban Durban, South Africa · PeeringDB 969
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d2::144
    • In the entry with IPv4 196.10.141.144: set IPv6 to 2001:43f8:6d2::144 (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.

  6. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::144 2001:43f8:6d0::9:144
    • In the entry with IPv4 196.60.8.144: set IPv6 to 2001:43f8:6d0::144 (now empty).
    • In the entry with IPv4 196.60.9.144: set IPv6 to 2001:43f8:6d0::9:144 (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

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 Cell C'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 240G across 6 exchanges.

South Africa CINX Cape Town, South Africa 196.223.22.59 10G 7 routes Both IPv6 not in PeeringDB
South Africa DINX Durban, South Africa 196.223.30.59 10G 7 routes Both IPv6 not in PeeringDB
South Africa JINX Johannesburg, South Africa 196.60.96.59
196.60.96.124
2 × 20G 26 routes Both IPv6 not in PeeringDB
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.186 20G 8 routes Both IPv6 not in PeeringDB
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.144 20G 8 routes Both IPv6 not in PeeringDB
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.144
196.60.9.144
100G + 40G 48 routes Both IPv6 not in PeeringDB

Cell C lists no facilities in PeeringDB.