NTT DATA, IS, South Africa
AS3741 · IS
NTT DATA, Middle East and Africa (MEA)
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.
-
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.
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 195.66.224.198 195.66.227.253 195.66.231.39 195.66.227.253 195.66.231.39 IPv6 address in PeeringDB, not in the export 2001:7f8:4::e9d:1 2001:7f8:4::e9d:2 2001:7f8:4::e9d:3 2001:7f8:4::e9d:2 2001:7f8:4::e9d:3 Port speed differs 2 × 100G + 20G 2 × 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.
-
IPv4 195.66.236.198 IPv6 2001:7f8:4:1::e9d:1 Speed 20000 Mbps (20G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 11 |
| Nov 18, 2026 | 11 |
| Nov 17, 2026 | 11 |
| Nov 16, 2026 | 11 |
| Nov 15, 2026 | 11 |
| Nov 14, 2026 | 11 |
| Nov 13, 2026 | 11 |
| Nov 12, 2026 | 11 |
| Nov 11, 2026 | 11 |
| Nov 10, 2026 | 11 |
| Nov 9, 2026 | 11 |
| Nov 8, 2026 | 11 |
| Nov 7, 2026 | 11 |
| Nov 6, 2026 | 11 |
| Nov 5, 2026 | 11 |
| Nov 4, 2026 | 11 |
| Nov 3, 2026 | 11 |
| Nov 2, 2026 | 11 |
| Nov 1, 2026 | 11 |
| Oct 31, 2026 | 11 |
| Oct 30, 2026 | 11 |
| Oct 29, 2026 | 11 |
| Oct 28, 2026 | 11 |
| Oct 27, 2026 | 11 |
| Oct 26, 2026 | 11 |
| Oct 25, 2026 | 11 |
| Oct 24, 2026 | 11 |
| Oct 23, 2026 | 11 |
| Oct 22, 2026 | 11 |
| Oct 21, 2026 | 11 |
| Oct 20, 2026 | 11 |
| Oct 19, 2026 | 11 |
| Oct 18, 2026 | 11 |
| Oct 17, 2026 | 11 |
| Oct 16, 2026 | 11 |
| Oct 15, 2026 | 11 |
| Oct 14, 2026 | 11 |
| Oct 13, 2026 | 11 |
| Oct 12, 2026 | 11 |
| Oct 11, 2026 | 11 |
| Oct 10, 2026 | 11 |
| Oct 9, 2026 | 11 |
| Oct 8, 2026 | 11 |
| Oct 7, 2026 | 11 |
| Oct 6, 2026 | 11 |
| Oct 5, 2026 | 11 |
| Oct 4, 2026 | 11 |
| Oct 3, 2026 | 11 |
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.
| CINX Cape Town, South Africa | 2 × 100G | Both | |
| DE-CIX Frankfurt Frankfurt, Germany | 2 × 100G | Both | |
| DINX Durban, South Africa | 2 × 10G | Both | |
| HKIX Hong Kong, Hong Kong | 1G | Both | |
| JINX Johannesburg, South Africa | 2 × 100G | Both | |
| LINX LON1 London, United Kingdom | 2 × 100G + 20G | Both IPv4 not in exportIPv6 not in exportSpeed differs | |
| LINX LON2 London, United Kingdom | 20G | PeeringDB only | |
| NAPAfrica IX Cape Town Cape Town, South Africa | 2 × 100G | Both | |
| NAPAfrica IX Durban Durban, South Africa | 2 × 10G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 2 × 100G | Both | |
| TIX Tanzania - Dar es Salaam Dar es Salaam, Tanzania | Not in PeeringDB |
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.
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| LONAPLondon, United Kingdom | 311 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| NetIXSofia, Bulgaria | 204 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| BBIX Hong KongHong Kong, Hong Kong | 104 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| NAPAfrica MAPS JohannesburgJohannesburg, South Africa | 31 | |
| IAIXHong Kong, Hong Kong | 20 | |
| Global Peer ExchangeWashington, United States | 6 | |
| JINX VoiceJohannesburg, South Africa | 4 |
Facilities (13)
The buildings NTT DATA, IS, South Africa lists in PeeringDB, and how many of the exchanges in each it's on.
| Telehouse - London (Docklands West)London | 2 of 7 | |
| Equinix FR2 - Frankfurt, NorthFrankfurt | 1 of 6 | |
| Telehouse - London (Docklands East)London | 2 of 6 | |
| Teraco Johannesburg Campus, South AfricaJohannesburg | 2 of 6 | |
| MEGA-i (iAdvantage Hong Kong)Hong Kong | 1 of 4 | |
| Teraco CT1 Cape Town, South AfricaCape Town | 2 of 3 | |
| OADC - ParklandsJohannesburg | 1 of 2 | |
| Teraco DB1 Durban, South AfricaDurban | 2 of 2 | |
| NTT Johannesburg 1 Data Center (JOH1)Centurion | 1 of 1 | |
| OADC CPT3 - Cape TownCape Town | 1 of 1 | |
| OADC, UmhlangaDurban | 1 of 1 | |
| Digital Realty London LHR17West Drayton | No exchange | |
| NTT Data (MEA) - Johannesburg 1 Data Center (JOH1)Centurion | No exchange |