ixreport

TOUCHNET TELECOMMUNICATIONS CC

AS328548 · Touchnet

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

Tools: Where can I peer with TOUCHNET TELECOMMUNICATIONS CC? · Where should TOUCHNET TELECOMMUNICATIONS CC peer next? · Compare TOUCHNET TELECOMMUNICATIONS CC 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 TOUCHNET TELECOMMUNICATIONS CC's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 18:41 UTC.

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

Add these exchanges (1)

On the exchange's own member list, but not in TOUCHNET TELECOMMUNICATIONS CC's PeeringDB record. Add one entry per connection with these values.

  1. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488From its IX-F export
    IPv4196.216.148.176
    IPv62001:43f8:bb1::176
    Speed1000 Mbps (1G)
    RS peerYes

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
    IPv6 address missing from PeeringDBnone2001:43f8:6d1::59
    • In the entry with IPv4 196.60.70.59: set IPv6 to 2001:43f8:6d1::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.

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 TOUCHNET TELECOMMUNICATIONS CC'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 22G across 3 exchanges.

Nigeria IXPN Lagos Lagos, Nigeria 196.216.148.176 2001:43f8:bb1::176 1G Yes Not in PeeringDB
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.59 10G Yes Both IPv6 not in PeeringDB
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.10.10
196.60.10.184
2001:43f8:6d0::10:10
2001:43f8:6d0::10:184
10G + 1G 6 routes Both

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

These exchanges have a switch in a facility where TOUCHNET TELECOMMUNICATIONS CC lists itself in PeeringDB, but don't have TOUCHNET TELECOMMUNICATIONS CC 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 TOUCHNET TELECOMMUNICATIONS CC lists in PeeringDB, and how many of the exchanges in each it's on.

South Africa Teraco Johannesburg Campus, South AfricaJohannesburg 1 of 6
South Africa Teraco CT1 Cape Town, South AfricaCape Town 1 of 3
South Africa Teraco DB1 Durban, South AfricaDurban 0 of 2