TCP checks from the Johannesburg node attempt a three-way handshake from AS396982 (Google LLC) to the specified host and port. The minimum TCP connection time to a European server from JHB is approximately 320–340 ms (two round trips at 160–170 ms), and to a US East Coast server around 400–420 ms. Measured connection times close to these minimums indicate a healthy path with no server-side queuing. Values significantly above the minimum RTT-implied floor suggest server backlog, asymmetric routing, or stateful firewall inspection adding delay.

TCP checks from a Google ASN in Johannesburg have a specific use case: verifying that application ports are reachable from Google-operated African infrastructure. Google deploys GGC (Google Global Cache) nodes with South African ISPs, and traffic from those caches originates from AS396982 prefixes. If your server needs to accept connections from Google cache infrastructure in South Africa — relevant for Google-served content, YouTube caching agreements, or similar arrangements — a TCP check from this node validates the firewall path.

For general reachability testing from an African vantage point, TCP checks from this node confirm whether a port is open to connections from Southern Africa. Services that explicitly target the African market should verify TCP connectivity on all application ports from JHB before launch. Common failure modes include security groups that were configured for US or European source IP ranges only, and DDoS mitigation rules that block entire AFRINIC IP blocks as a blunt instrument — both are identifiable with a TCP check from this node compared against European or US node results.

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.