ixreport

OTEL Telecoms

AS37356 · HugeTNS

7Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
7Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

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

Make the changes on OTEL Telecoms'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 Durban Durban, South Africa · PeeringDB 969
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 196.10.141.40: set Speed to 1000 (1G) (now 10000).

    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

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

Map

Where OTEL Telecoms'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 71G across 7 exchanges.

South Africa CINX Cape Town, South Africa 196.223.22.75 2001:43f8:1f1::75 10G 14 routes Both
South Africa DINX Durban, South Africa 196.223.30.75 2001:43f8:1f2::75 10G 9 routes Both
South Africa JINX Johannesburg, South Africa 196.60.96.75 2001:43f8:1f0::75 10G 7 routes Both
South Africa JINX Voice Johannesburg, South Africa 196.223.15.32 1G Yes PeeringDB
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.195 2001:43f8:6d1::195 10G 14 routes Both
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.40 2001:43f8:6d2::40 10G 9 routes Both Speed differs
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.209
196.60.9.10
2001:43f8:6d0::209
2001:43f8:6d0::9:10
2 × 10G 7 routes Both

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

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

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