HTTP checks from the Johannesburg node issue a full GET request from AS396982 (Google LLC, Johannesburg) and report the status code, response time, and completion status. For targets with CDN PoPs in Johannesburg — Cloudflare, Akamai, and Fastly all operate South African edges — HTTP responses should complete in under 20–30 ms. For bare origins in Europe, the response time floor is 160–170 ms, and for US East Coast origins around 200 ms. These figures assume no server-side processing delay beyond the network RTT.

South Africa is an underserved market from a CDN perspective compared to Europe or the US — not every CDN operates a Johannesburg PoP, and some route South African traffic through a regional PoP in London or Amsterdam rather than serving locally. An HTTP test from this node quickly reveals whether your CDN is serving South African users from a local PoP (fast, sub-30ms) or from Europe (slow, 160ms+). The difference is immediately visible in the HTTP response time, and actionable — CDN PoP selection is typically configurable per region.

HTTP failures from the South Africa node that do not occur from European or US nodes often indicate geo-blocking or WAF rules that do not include South African IP ranges in the allowlist. AS396982 is a well-known Google infrastructure ASN and is unlikely to be blocked by mistake in most generic WAF configurations. More commonly, services with explicit country allowlists may not include ZA or may not correctly map the Google JHB prefix to South Africa. A 403 or 429 response from this node with no corresponding failure from other regions is the classic pattern.

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.