Website Availability in South Africa

Wondering whether a website is down for everyone or just unreachable from South Africa? The answer usually hides in the physical layer of the internet. South Africa 🇿🇦 connects to the global network through 13 submarine cable systems that come ashore at 8 landing stations, and its national domain zone is .za. Every request from a user in South Africa to a foreign server, and every request from abroad to a site hosted in South Africa, physically travels over these systems or their terrestrial backhaul.

This page summarizes what our measurement network knows about internet connectivity in South Africa: which cables serve the country, how its leading internet providers are performing, and what can make a website appear offline for users there while it works everywhere else.

Current connectivity status in South Africa

As of our latest hourly measurement cycle, the national internet signal of South Africa is operating normally (BGP visibility and active probing dip: 0% against the 24-hour baseline). National-level signals catch large events; an individual website can still be unreachable for local reasons, which is what the availability checker above is for.

Connectivity for most users in South Africa is provided by a small group of networks:

If a website fails to load only for customers of one of these providers, the problem is almost always local: DNS resolution inside that network, ISP-level filtering, or a routing issue, rather than the website itself being down.

Submarine cables that connect South Africa to the internet

The following systems land in South Africa. Cable length is a rough proxy for how much of the world a system reaches: long trunks connect continents, short ones link neighbors. Our monitors registered 7 latency anomalies on cables serving South Africa in the last 30 days.

Plus 1 more systems, mostly regional links. Live health data for every cable is available on the linked pages.

How resilient is South Africa to cable failures?

With 13 cable systems across 8 landing stations, South Africa has a well diversified set of routes. A single cable fault is usually absorbed by the remaining systems, although latency to some regions can temporarily increase. Repairs at sea typically take one to several weeks, because a specialized cable ship has to locate the fault, lift the cable and splice it on deck.

Why a website may not load in South Africa

When a site works in other countries but fails in South Africa, the usual suspects are, in order of likelihood: a DNS problem inside a local ISP, a content delivery network misrouting users in South Africa to an unhealthy edge node, a routing or peering issue between local networks and the site's host, and finally a submarine cable incident affecting the whole region.

Our DNS measurements have not flagged systematic national filtering in South Africa, although individual ISPs and corporate networks can still block specific resources.

Neighbors on the same cables

These countries share submarine cable systems with South Africa, so a major cable incident can affect them together:

🇳🇬 Nigeria (5 shared) · 🇪🇸 Spain (4 shared) · 🇮🇳 India (4 shared) · 🇸🇦 Saudi Arabia (2 shared) · 🇫🇷 France (2 shared) · 🇪🇬 Egypt (2 shared)

See the full list on the website availability by country hub.

Data: GeoCables submarine cable telemetry, RIPE Atlas measurements, IODA national signals, APNIC user estimates. Numbers refresh automatically; last update July 11, 2026.