ixreport

Telkom SA

AS5713 · Openserve

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

Tools: Where can I peer with Telkom SA? · Where should Telkom SA peer next? · Compare Telkom SA with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Telkom SA's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on Telkom SA'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 Telkom SA's PeeringDB record. Add one entry per connection with these values.

  1. South Africa DINX Durban, South Africa · PeeringDB 610From its IX-F export
    IPv4196.223.30.11
    IPv62001:43f8:1f2::11
    Speed10000 Mbps (10G)
    RS peerNo

    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

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

Map

Where Telkom SA'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 980G across 9 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.209.213 2001:7f8:1::a500:5713:3 20G 247 routes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.214 2001:7f8::1651:0:1 100G 853 routes Both
France DE-CIX Marseille Marseille, France 185.1.47.81 2001:7f8:36::1651:0:1 100G 850 routes Both
South Africa DINX Durban, South Africa 196.223.30.11 2001:43f8:1f2::11 10G Not in PeeringDB
United Kingdom LINX LON1 London, United Kingdom 195.66.226.42 2001:7f8:4::1651:1 200G 867 routes Both
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.181 2001:43f8:6d1::181 100G Both
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.128 2001:43f8:6d2::128 40G Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.9.107 2001:43f8:6d0::9:107 400G Both
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 193.239.118.189 2001:7f8:13::a500:5713:1 10G Yes Both

Telkom SA lists no facilities in PeeringDB.

Recent changes Search them

  • Nov 19, 2026 [PDB] AS5713 Telkom SA now in PeeringDB at NAPAfrica IX Durban
  • Nov 19, 2026 [PDB] AS5713 Telkom SA no longer in PeeringDB at NAPAfrica IX Durban (still on its IX-F list)