ixreport

Teraco Data Environments

AS37599 · NAPAfrica

Teraco Data Environments Pty Ltd

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

Tools: Where can I peer with Teraco Data Environments? · Where should Teraco Data Environments peer next? · Compare Teraco Data Environments 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 Teraco Data Environments's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-11-19 12:40 UTC.

Make the changes on Teraco Data Environments'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
    Port speed differs10G200G + 3 × 10G

    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 that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. South Africa NAPAfrica MAPS Cape Townghost Cape Town, South Africa · PeeringDB 3884

    Only one outside network

    IPv4196.46.25.24
    IPv6–
    Speed10000 Mbps (10G)

Exchanges over time

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

Map

Where Teraco Data Environments'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 5 exchanges.

South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.39 2001:43f8:6d1::39 10G 6 routes Both Speed differs
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.165
196.10.141.200
2001:43f8:6d2::165
2001:43f8:6d2::200
100G + 10G 4 routes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.200 2001:43f8:6d0::200 100G 7 routes Both
South Africa NAPAfrica MAPS Cape Townghost Cape Town, South Africa 196.46.25.24 10G Yes PeeringDB
South Africa NAPAfrica MAPS Johannesburg Johannesburg, South Africa 196.46.25.144 10G Yes Both

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

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

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