ixreport

NTT DATA, IS, South Africa

AS3741 · IS

NTT DATA, Middle East and Africa (MEA)

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

Tools: Where can I peer with NTT DATA, IS, South Africa? · Where should NTT DATA, IS, South Africa peer next? · Compare NTT DATA, IS, South Africa with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in NTT DATA, IS, South Africa's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on NTT DATA, IS, South Africa'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 NTT DATA, IS, South Africa's PeeringDB record. Add one entry per connection with these values.

  1. Tanzania TIX Tanzania - Dar es Salaam Dar es Salaam, Tanzania · PeeringDB 361From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export195.66.224.198 195.66.227.253 195.66.231.39195.66.227.253 195.66.231.39
    IPv6 address in PeeringDB, not in the export2001:7f8:4::e9d:1 2001:7f8:4::e9d:2 2001:7f8:4::e9d:32001:7f8:4::e9d:2 2001:7f8:4::e9d:3
    Port speed differs2 × 100G + 20G2 × 100G
    • The entry with IPv4 195.66.224.198, IPv6 2001:7f8:4::e9d:1 isn't in the export: delete it if that connection is gone.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If NTT DATA, IS, South Africa has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.236.198
    IPv62001:7f8:4:1::e9d:1
    Speed20000 Mbps (20G)

Exchanges over time

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

Map

Where NTT DATA, IS, South Africa'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 1.3T, at the 10 of 11 exchanges with a speed in PeeringDB or the exchange's IX-F export.

South Africa CINX Cape Town, South Africa 196.223.22.10
196.223.22.13
2001:43f8:1f1::10
2001:43f8:1f1::13
2 × 100G Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.195.177
80.81.196.45
2001:7f8::e9d:0:2
2001:7f8::e9d:0:3
2 × 100G Down Both
South Africa DINX Durban, South Africa 196.223.30.10
196.223.30.13
2001:43f8:1f2::10
2001:43f8:1f2::13
2 × 10G Both
Hong Kong HKIX Hong Kong, Hong Kong 123.255.91.234 2001:7fa:0:1::ca28:a1ea 1G Both
South Africa JINX Johannesburg, South Africa 196.60.96.10
196.60.96.13
2001:43f8:1f0::10
2001:43f8:1f0::13
2 × 100G Up, 0 routes Both
United Kingdom LINX LON1 London, United Kingdom 195.66.224.198
195.66.227.253
195.66.231.39
2001:7f8:4::e9d:1
2001:7f8:4::e9d:2
2001:7f8:4::e9d:3
2 × 100G + 20G 5,936 routes Both IPv4 not in exportIPv6 not in exportSpeed differs
United Kingdom LINX LON2 London, United Kingdom 195.66.236.198 2001:7f8:4:1::e9d:1 20G PeeringDB only
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.126
196.60.71.67
2001:43f8:6d1::126
2001:43f8:6d1::71:67
2 × 100G Yes Both
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.65
196.10.141.126
2001:43f8:6d2::65
2001:43f8:6d2::126
2 × 10G Yes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.126
196.60.9.254
2001:43f8:6d0::126
2001:43f8:6d0::9:254
2 × 100G Both
Tanzania TIX Tanzania - Dar es Salaam Dar es Salaam, Tanzania Not in PeeringDB

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

These exchanges have a switch in a facility where NTT DATA, IS, South Africa lists itself in PeeringDB, but don't have NTT DATA, IS, South Africa 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.

Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Telehouse - London (Docklands East); Telehouse - London (Docklands West)
United Kingdom LONAPLondon, United Kingdom 311 Telehouse - London (Docklands East); Telehouse - London (Docklands West)
Germany LOCIX FRANKFURTFrankfurt am Main, Germany 205 Equinix FR2 - Frankfurt, North
Bulgaria NetIXSofia, Bulgaria 204 Telehouse - London (Docklands East); Telehouse - London (Docklands West); MEGA-i (iAdvantage Hong Kong) and 3 more
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands East); Telehouse - London (Docklands West)
Germany MegaIX FrankfurtFrankfurt, Germany 114 Equinix FR2 - Frankfurt, North
Hong Kong BBIX Hong KongHong Kong, Hong Kong 104 MEGA-i (iAdvantage Hong Kong)
Germany Equinix FrankfurtFrankfurt, Germany 78 Equinix FR2 - Frankfurt, North
South Africa NAPAfrica MAPS JohannesburgJohannesburg, South Africa 31 Teraco Johannesburg Campus, South Africa
Hong Kong IAIXHong Kong, Hong Kong 20 MEGA-i (iAdvantage Hong Kong)
United States Global Peer ExchangeWashington, United States 6 Telehouse - London (Docklands West); Equinix FR2 - Frankfurt, North; Teraco Johannesburg Campus, South Africa
South Africa JINX VoiceJohannesburg, South Africa 4 Teraco Johannesburg Campus, South Africa; OADC - Parklands
Facilities (13)

The buildings NTT DATA, IS, South Africa lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Telehouse - London (Docklands West)London 2 of 7
Germany Equinix FR2 - Frankfurt, NorthFrankfurt 1 of 6
United Kingdom Telehouse - London (Docklands East)London 2 of 6
South Africa Teraco Johannesburg Campus, South AfricaJohannesburg 2 of 6
Hong Kong MEGA-i (iAdvantage Hong Kong)Hong Kong 1 of 4
South Africa Teraco CT1 Cape Town, South AfricaCape Town 2 of 3
South Africa OADC - ParklandsJohannesburg 1 of 2
South Africa Teraco DB1 Durban, South AfricaDurban 2 of 2
South Africa NTT Johannesburg 1 Data Center (JOH1)Centurion 1 of 1
South Africa OADC CPT3 - Cape TownCape Town 1 of 1
South Africa OADC, UmhlangaDurban 1 of 1
United Kingdom Digital Realty London LHR17West Drayton No exchange
South Africa NTT Data (MEA) - Johannesburg 1 Data Center (JOH1)Centurion No exchange