Global technology, grounded in Africa.Reported from London · Connected to the world

The four desks

Stories & formats

More

Find a published story by title, subject or author.

african tech

CMC’s EMEA-R links South Africa and Europe. Check the full circuit

Nokia and CMC describe a six-node capacity corridor with South Africa–UK and Saudi Arabia–Europe routes. For a business, the next check is which handovers, building connections and service commitments the order includes.

Watch this report

Read the report and video transcript

Media credits, sources and reuse details ↓

For a business moving work between South Africa and the UK, an international circuit has to reach the office or data centre where that work happens. CMC Networks’ EMEA-R corridor brings six named network hubs into one service proposition. The useful next step is to ask which links, site extensions and service commitments appear on your particular order.

What the new announcement establishes

In its 18 November announcement, Nokia says CMC’s Europe–Middle East–Africa Ring uses its optical transport technology and offers dedicated 1G, 10G and 100G capacity. The companies describe a single CMC contract and service-level agreement, or SLA. The named nodes are Johannesburg, Cape Town, Jeddah, Marseille, Frankfurt and London. These are supplier descriptions of the service. Read Nokia’s announcement.

Follow the described first-phase links

The release describes Johannesburg to London through Cape Town and the Atlantic, and Jeddah to Marseille through the Red Sea and Mediterranean. It also names terrestrial links between London, Frankfurt and Marseille. That gives an infrastructure team concrete endpoints to discuss with the provider. The public description does not identify the full physical route, all cable systems or the protection arrangement for an individual customer circuit.

Put your actual premises on the order

CMC’s current service page lists the six nodes as live. It says extensions to customer sites, data centres and internet exchanges depend on a request and feasibility checks. Ask the provider to identify the exact handover location at each end, who supplies the connection from that location to your building, and when each part can be delivered. A team with a Johannesburg office and a London cloud connection needs those two specific access paths included in the plan. Check CMC’s service description.

Turn the capacity figure into a service checklist

Start with the task the link must support, such as moving a production file between offices or accessing a hosted application. Ask for the committed capacity, expected latency between the agreed handover points, how performance is measured and where service credits apply. Ask how a fault is escalated and which hours the support commitment covers. If you require a backup, ask the provider to explain what infrastructure it shares with the primary path. These are questions for the proposed service design and contract. PING has not measured a circuit or checked an individual customer offer.

Keep future capacity separate in the plan

CMC’s page distinguishes live and upcoming capacity, and says onward regional connections are available on request. Ask which parts of a proposed service are ready now and which depend on an extension. Retain the route, order and SLA together so the same endpoints can be checked during acceptance. For readers elsewhere in Africa, the useful question is how a local access provider reaches one of the corridor’s nodes. CMC describes its broader network and service options on a separate page. See the network and solutions.

How this was reported

PING checked the dated Nokia release and CMC’s current service and network pages on 19 November 2026. The story distinguishes the announcement date from this access date. The original cover depicts only the first-phase connections described in the release. Drafting was assisted by artificial intelligence. Supplier capacity, availability and performance descriptions remain attributed, and the article offers documentation-based questions for a reader’s own service order.

Original route schematic by PING! Magazine, based on Nokia and CMC Networks documentation.

Read PING! on checking the backup route behind Congo Telecom’s WACS update.

Video transcript

Original PING! Magazine graphics and editorial video. Narration uses the Kokoro British Emma synthetic voice, rendered locally. The new service links South Africa, Saudi Arabia and Europe. Check the exact handover point at each end of your circuit. Ask who supplies the link from the network to your building. Then confirm the service levels and how faults will be handled.

Sources and disclosures
Disclosure
Documentation-based reporting with artificial-intelligence-assisted drafting. PING checked current supplier descriptions and gives a service-order checklist. No circuit was bought or tested. The cover is an original PING route schematic, with supplier media held for permission. The separate narrated short uses the local Kokoro Emma synthetic voice, with synchronised captions and source credits.
Declared media rights
Generated illustration
Sources and method
Nokia release dated 18 November 2026, 09:00 Europe/Amsterdam. Current CMC service and network pages accessed 19 November 2026. Live hubs, requested extensions and supplier capacity descriptions are distinguished. Original route schematic by PING! Magazine, based on Nokia and CMC Networks documentation. Cover: First-phase links described in Nokia’s 18 November announcement. Original PING schematic. Video: A 17.8-second PING guide to checking the full circuit behind CMC’s EMEA-R service. PING! Magazine original graphics and edit. Kokoro British Emma synthetic narration. Media provenance: Video -- Generated illustration. Cover -- Owned by PING!.

Reader comments

Comments are not open yet. When available, submissions will require free sign-in and editorial approval before appearing. PING does not promise a response.

Privacy information