DNS checks from the Johannesburg node query authoritative nameservers directly from AS396982 (Google LLC, Johannesburg) and return the resolved records with query time. Google operates its own anycast DNS resolver (8.8.8.8) with a JHB node, and Cloudflare (1.1.1.1) also has South African anycast presence. DNS queries to these providers from the JHB node complete in under 5 ms. For authoritative servers with no African anycast node, queries route to the nearest available location — typically London or Amsterdam, adding 160–170 ms to every DNS lookup. At scale, this DNS lookup overhead is the most impactful latency element for African users hitting globally distributed services.

The Johannesburg Google node is the correct location for validating GeoDNS rules targeting South Africa or Sub-Saharan Africa. AS396982 Johannesburg prefixes are correctly geolocated to South Africa in AWS Route 53 geolocation routing policies, Cloudflare load balancer geo rules, and NS1 filter chains. A DNS check from this node confirms that your ZA or Africa-targeted routing policy returns the intended record — ideally a JHB or European IP depending on your nearest-origin strategy. If the South Africa node receives a US IP from your GeoDNS when you intended to serve African users from a European origin, the policy boundary is not correctly set for the AFRINIC IP space.

TTL management matters more for African users than for European ones. An African user whose ISP resolver caches a stale record must wait for the full TTL to expire before getting the updated answer — and because many African ISPs run their own resolvers with limited capacity, they may also apply aggressive negative caching. DNS checks from the South Africa node after a record change confirm that the authoritative server is returning the new record. If the JHB node sees the old record but European nodes see the new one, the issue is likely propagation delay to a Johannesburg-proximate anycast node, not a problem with the authoritative server itself.

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.