MTR from the Johannesburg node (AS396982, Google LLC) runs a continuous path trace to your target, reporting per-hop latency and packet loss. The most distinctive feature of South African MTR traces is the submarine cable exit — a latency jump of 160–170 ms to London or Amsterdam, representing the SEACOM or WACS cable propagation time plus any Google backbone hops from JHB to the cable landing station. Everything before that jump is South African domestic network; everything after is the international path. The cable crossing is typically visible as a single hop with a large RTT increase.

MTR traces from JHB to European targets via SEACOM typically route through Mombasa (Kenya) or Fujairah (UAE) before landing in Marseille or Djibouti and continuing overland to Western Europe. Via WACS, the path goes up the West African coast through Accra or Dakar before landing in Portugal or Spain. The intermediate cable landing stations appear as hops in the MTR output with incremental latency additions of 20–40 ms each. Knowing which cable system is carrying the traffic helps when diagnosing whether latency is due to cable routing or congestion on a specific segment.

Google's own fiber infrastructure in Africa means that MTR traces from AS396982 in JHB may route through Google's private backbone rather than public transit for certain destinations — particularly other Google-operated networks and major peering partners. Hops through Google's backbone show as internal Google ASNs (AS15169 hops) in the MTR output. Loss on Google internal backbone hops is typically ICMP rate limiting on Google's internal routers, not real packet loss. Real path issues appear as sustained loss from the point of failure onward, including at the final destination hop.

Johannesburg is the internet hub of Sub-Saharan Africa. The city hosts NAP Africa at Teraco's JHB1 facility — the largest carrier-neutral colocation and peering point on the continent. Teraco JHB1 houses over 200 networks including MTN (AS37457), Vodacom (AS36874), Telkom SA (AS10474), and major content networks including Google, Meta, and Akamai. Our probe node runs on AS396982 (Google LLC) in a Google datacenter in Johannesburg, reflecting Google's direct investment in African network infrastructure as part of their regional expansion strategy. Google operates its own fiber and peering arrangements in JHB, connecting to the broader South African internet ecosystem via Teraco and NAP Africa.

South Africa's international connectivity relies on submarine cable systems landing at multiple points along the eastern and western coastlines. SEACOM (operational since 2009) connects the East African coast to Europe via the Middle East. WACS (West Africa Cable System) runs along the western coast connecting South Africa to Europe via West Africa. EAST AFRICA MARINE SYSTEM (EASSy) provides additional eastern coast capacity. The combination of multiple cable systems landing in South Africa gives JHB better path diversity to Europe than most other African cities, though total available bandwidth remains constrained compared to European or North American interconnection points.

Reference RTTs from the Johannesburg Google node: JHB to London is approximately 160 ms, JHB to Amsterdam 165 ms, JHB to Frankfurt 170 ms, JHB to New York 200–210 ms, JHB to Singapore 200–210 ms, JHB to Nairobi 30–40 ms, JHB to Lagos 90–100 ms. The London and Amsterdam latency figures are lower than many people expect — SEACOM and WACS provide reasonably direct paths to Europe without the multi-hop routing of older satellite-dependent links. These submarine cable paths have made South Africa one of the best-connected countries in Africa for international latency.

Google's presence in Johannesburg via AS396982 is part of Google's broader African strategy, which includes Google Cache (GGC) nodes deployed with South African ISPs and the Equiano subsea cable (connecting South Africa to Portugal). The AS396982 prefix in JHB is correctly identified as a Google infrastructure ASN by all major GeoIP databases. Traffic from this node will be recognized as originating from a major cloud provider's South African infrastructure — relevant for services that apply different routing or rate-limiting rules to cloud provider source IPs versus residential ISP IPs. DE-CIX Johannesburg, launched as part of DE-CIX's African expansion, provides additional interconnection options beyond NAP Africa and JINX.

South Africa's domestic backbone connects Johannesburg to Cape Town, Durban, and Pretoria over long-haul fibre operated by Telkom SA and a growing number of private operators. JHB to Cape Town is approximately 30 ms, JHB to Durban 15–20 ms. The Johannesburg node is by far the most relevant test location for Sub-Saharan African network conditions — it sits at the continent's main peering hub with direct access to all the major African and international carrier paths. For any service targeting African audiences, an HTTP or ping test from this node is the first step in understanding the continental connectivity picture.