One 43-Year-Old Ship in Cape Town Guards All of Africa's Internet - Here's What Happens When a Cable Breaks

On 10 July 2026, a body called the International Advisory Body on Submarine Cable Resilience - a group of 175 experts working under the International Telecommunication Union and the International Cable Protection Committee - adopted a report in Geneva after a two-year investigation into who actually fixes the internet when it breaks under the ocean. The finding that matters most for South African readers is blunt: access to timely repair resources is not globally equitable, and Africa is the continent that draws the shortest straw.

This isn't an abstract policy story. Almost all of South Africa's international internet capacity - the traffic that carries a Netflix stream from a European data centre, a Microsoft Teams call routed via London, or a cloud backup landing in Frankfurt - travels through a small number of undersea fibre-optic cables that surface at a handful of points on the African coast. When one of those cables breaks, your local Vumatel, Openserve or Frogfoot line doesn't get any slower on paper - your uncapped, unshaped fibre plan is still exactly what you paid for - but the international leg of every request you make can crawl for weeks, sometimes months, while the industry waits for one of a tiny number of specialised ships to reach the fault and fix it.

Two related TechCentral reports, both published in the days around the Geneva report, laid out just how thin that repair capacity is and how concentrated the cables themselves are at a handful of geographic chokepoints. Together they explain a pattern most fibre users have noticed at some point without ever knowing why: occasional periods, sometimes lasting weeks, where an otherwise fast South African fibre line feels sluggish on international sites for no obvious local reason.

The single most striking fact in the report is this: Africa's entire coastline - more than 30,000km, touching dozens of countries - is covered by exactly one permanently stationed cable-repair vessel. That ship is the Léon Thévenin, a 43-year-old vessel operated by French company Orange Marine, home-ported in Cape Town.

To put the geography in perspective: a single repair run from Dakar in West Africa to Mombasa in East Africa covers more than 10,000km - a transit distance the report compares directly to sailing from Shanghai to Los Angeles. If a fault happens off West Africa while the Léon Thévenin is finishing a job near East Africa (or is in scheduled maintenance, which older ships need more of), there is no second African-based vessel to dispatch. The next-nearest options are based in Europe or the Mediterranean, adding days or weeks before a repair can even begin.

Globally, the imbalance is stark. Africa, the South Atlantic and the Pacific islands together share roughly 13% of the world's active cable-repair fleet. Asia-Pacific and North America/Europe each command roughly 40%. The South Indian Ocean and south-east Pacific have zero permanently stationed repair ships at all - any fault there depends on a vessel being freed up from somewhere else in the world and sailing in.

Orange Marine's own president, Didier Dillard, has flagged the aging-fleet problem directly: older vessels lose an estimated 15-20% of their operational availability every year to dry-docking and maintenance - and the Léon Thévenin, at 43 years old, is well past the age where that maintenance burden starts to bite.

The report's repair-time data is the clearest signal of a system under strain. Globally, the average time to begin a repair after a cable fault is reported has more than doubled in twelve years - from under 20 days in 2012 to over 50 days in 2024. The global median sits at 8 days and the global average at 22.7 days once faster and slower regions are blended together - but those averages hide huge regional gaps.

South Africa is actually the standout performer here, not the problem: the report credits South Africa with the fastest cable fault-to-mobilisation time in the world, at 1.95 days - beating even the UK's 3.66 days. That speed comes down to pre-authorised repair permits, streamlined permitting processes, and simple proximity to where the Léon Thévenin is based. The problem isn't South Africa's own response speed; it's that South Africa's fast local mobilisation still depends on one ship that can only be in one place, and once a repair convoy actually has to sail thousands of kilometres to reach a fault - or wait behind another job in the queue - proximity to Cape Town stops helping.

Most faults, reassuringly, aren't sabotage or acts of war - they're mundane. Globally there are 150-200 cable faults a year, and more than 80% are caused by ordinary human maritime activity: a trawler's fishing gear snagging a cable, a ship dropping anchor in the wrong place. The fix for a snagged or severed cable is still the same regardless of cause - a specialised ship has to sail to the exact GPS coordinates, grapple the cable off the seabed (sometimes from kilometres down), splice it, and lower it back - work that a brand-new, purpose-built repair ship costs US$100-150 million (roughly R1.6-2.5 billion) to build, which is exactly why so few of them exist.

Two real 2024 incidents show what a stretched repair system means in practice, and one of them affected South African-routed traffic directly.

In March 2024, four separate submarine cables were severed off the West African coast in quick succession - a rockfall-triggered break in the Congo Canyon, an area that had already suffered a similar dual-cable break in 2020. The result: internet connectivity was "severely throttled" across 12 West African countries, disrupting financial markets, cloud services and cross-border data flows for days. Nigeria alone estimated its economic loss at US$590 million (roughly R9.7 billion) over just four days without full connectivity.

Closer to home in relevance, a February 2024 attack in the Red Sea - a Houthi strike on the cargo vessel Rubymar - severed three Red Sea cables, including infrastructure belonging to Seacom, the operator whose cable carries a meaningful share of South Africa-to-East Africa-to-Europe traffic. Repairs were delayed for months, not because there was no ship available, but because getting permission to operate a repair vessel in Yemeni territorial waters amid an active conflict took far longer than the technical fix itself. That's the kind of delay South Africa's own excellent 1.95-day local mobilisation time can't do anything about - the bottleneck was thousands of kilometres away, in someone else's waters and someone else's war.

The most extreme example globally, cited in the same report, is Tonga: in January 2022, the Hunga Tonga-Hunga Ha'apai volcanic eruption severed the island nation's sole international cable, cutting it off almost entirely from the global internet for 61 days. The economic damage was estimated at US$182 million - 38.7% of Tonga's entire GDP. It's an extreme case because Tonga had only one cable and no redundancy at all; it's a useful worst-case reference point for why redundancy (multiple independent cables serving the same country) matters as much as repair speed.

The companion TechCentral piece on internet chokepoints adds an uncomfortable layer: cable damage that looks deliberate is becoming a more visible pattern, even though the Geneva report itself is cautious about attributing motive, citing state-security sensitivities and the internet's growing split into "distinct US and Chinese ecosystems." A cluster of Baltic Sea incidents illustrates the trend - a pipeline and cables damaged near Finland in October 2023, the C-Lion1 cable and a Lithuania-Sweden link cut in November 2024, and the Estlink 2 power cable plus four telecoms cables damaged in December 2024, an incident linked to the tanker Eagle S that cost roughly €60 million and took more than seven months to fully repair. In July 2025, Taiwan secured its first-ever conviction of a foreign captain - three years' jail time - for deliberately dragging an anchor across the Taiwan-Penghu No. 3 cable.

None of these incidents are African, and the report is explicit that more than 80% of the 150-200 annual global cable faults are still accidental. But the broader argument the report makes - that undersea cables cluster through a small number of geographic chokepoints, the same way global oil shipping bottlenecks through the Strait of Hormuz - applies directly to Africa's position. An estimated 17-plus cables carrying 17-20% of all global internet traffic squeeze through the Bab el-Mandeb Strait, a channel less than 23km wide at the mouth of the Red Sea - the same general chokepoint area where the Rubymar incident cut Seacom's cable. Building a new cable route around a chokepoint like that costs 15-30% more than following the established, congested path, which is exactly why operators keep clustering cables in the same narrow corridors despite the obvious concentration risk.

If you've ever had a fast, reliable South African fibre connection suddenly feel sluggish on international sites and video calls - despite your ISP's status page showing no local fault, your router looking fine, and a speed test to a local server coming back normal - this is very often the explanation. Your fibre operator (Vumatel, Openserve, Frogfoot, Octotel and the rest) controls the cable in the ground on your street. It does not control the undersea cable that carries your traffic onward to servers overseas - that's a completely different layer of infrastructure, owned and operated by international consortiums, and outside any single South African FNO's ability to fix.

This is also a useful reminder of what "uncapped and unshaped" fibre actually promises and doesn't promise: your ISP is committing to not throttling or capping your local line, not to guaranteeing a fixed international transit speed regardless of what happens to the cables carrying that traffic. A cable break thousands of kilometres offshore isn't a breach of your fair-use policy or a sign your ISP is cutting corners - it's a genuine, physical bottleneck upstream of anything your ISP controls.

The good news is that South Africa is meaningfully better positioned than a single-cable country like Tonga. Multiple independent international cable systems now land on South African shores or serve the region - including SAT-3/WASC, WACS, ACE, EASSy and Seacom, alongside newer, higher-capacity systems like 2Africa (backed by Meta and a consortium of telecoms operators) and Google's Equiano, which landed at Melkbosstrand in 2022. That redundancy is exactly why a single cable break rarely causes a total blackout here the way it did in Tonga - traffic can often reroute onto a different cable system, just at reduced capacity and higher latency while the affected route stays down.

Orange Marine isn't standing still on the aging-fleet problem the report flags. A newer vessel, Sophie Germain (a €50 million ship that entered service in 2023), is already stationed in southern France and covers the Mediterranean, Red Sea and North/East Africa - though not the South Atlantic route the Léon Thévenin covers from Cape Town. More significantly, Orange Marine ordered two new hybrid-powered repair ships from Colombo Dockyard in November 2025, specifically to replace the 43-year-old Léon Thévenin and the similarly aged Antonio Meucci (based in Italy). Delivery is expected in 2028 and 2029 - real progress, but still a multi-year gap during which Africa's repair capacity remains exactly as thin as the report describes today.

On the policy side, the Geneva report's core recommendation is that access to repair resources needs to become more globally equitable - faster permitting, pre-authorisation arrangements like the ones South Africa already uses, and fewer regulatory delays of the kind that stalled the Red Sea repairs after the Rubymar incident. None of that fixes the fundamental one-ship problem overnight, but it's the direction the industry body is pushing the countries and operators that control cable repair permitting.

A few practical habits are worth adopting given all of this:

• Test local before you blame your line. Run a speed test against a South African server (most speed-test tools let you pick one) alongside a test to an overseas server. If local speed is fine but international sites and calls are slow, the problem is very likely upstream - international transit, not your fibre line or your home Wi-Fi setup.
• Check your ISP's status page and social channels before assuming the worst. International cable faults are widely reported by network operators and industry press within hours of discovery - if there's been a cable break affecting your route, it's usually public knowledge fast.
• Don't cancel or switch ISPs over a cable-related slowdown. Because the fault sits upstream of any single South African ISP, switching providers on the same physical fibre network won't fix a problem caused by a severed international cable - though it may be worth asking a prospective ISP which international transit providers and cable systems they route through, since ISPs with more diverse upstream partnerships tend to degrade less gracefully during a single cable's downtime.
• Expect these events to keep happening, at roughly the same rate. With 150-200 global cable faults a year and repair capacity not meaningfully expanding until the new Orange Marine ships arrive in 2028-2029, periodic slow patches tied to distant cable repairs are a structural feature of how the modern internet works, not a one-off crisis.