A New Route, Not Just More Capacity
Africa’s subsea cable story in the last five years has been largely about adding capacity on familiar routes: 2Africa — the Meta-backed 45,000km ring system — adds massive throughput but broadly follows Atlantic and Indian Ocean coastlines that existing cables already use. The Medusa cable addresses North Africa with an 8,700km Mediterranean system. Equiano hugs the West African coast. All of these expand bandwidth, but none fundamentally diversifies the routing topology.
Via Africa does something structurally different: it runs directly across the Atlantic from West Africa to the UK, France, and Portugal, creating a trans-Atlantic corridor that bypasses the Mediterranean bottleneck and the congestion-prone cable junction zones around the Strait of Gibraltar and the Suez Canal approaches. More than half of Africa’s international bandwidth flows through just five countries — Nigeria, South Africa, Egypt, Algeria, and Kenya — creating concentration risk that any single regional event can activate. Via Africa targets that concentration directly by offering an alternative pathway that doesn’t share physical infrastructure with the dominant Mediterranean and Indian Ocean routes.
The consortium is led by Orange and includes Orange Côte d’Ivoire, Sonatel (Senegal), Canalink, GUILAB, International Mauritania Telecom, and Silverlinks. Orange’s CEO framed the resilience rationale explicitly: “You need different routes to make sure that when you have one or two cable cuts, you still have connectivity.” That framing — resilience before raw bandwidth — is the appropriate framing for 2026, when the most pressing African connectivity problem is not theoretical peak throughput but practical uptime during disruption events.
The Infrastructure Context Via Africa Enters
Nigeria alone currently hosts eight submarine cables yet faces persistent fiber cuts and network congestion, demonstrating that cable count is not the same as connectivity reliability. West Africa’s internet costs remain among the highest in the world on a per-Mbps basis, and latency to European cloud regions (the primary destination for most African enterprise workloads) adds 60 to 90 milliseconds to every request because of inefficient routing through Mediterranean junction points.
The Computer Weekly analysis of the Via Africa announcement notes that Via Africa is explicitly positioned to “contribute to greater diversity and resilience of international connectivity serving Africa” — language that signals its primary purpose is route diversification, not just throughput addition. That is the right priority given that the 2022 West Africa cable break (which affected multiple cables simultaneously along the same routing corridor) demonstrated that capacity redundancy on overlapping routes provides far less protection than true route independence.
For hyperscalers evaluating where to place African data center infrastructure, route diversity is a prerequisite. AWS, Microsoft Azure, and Google Cloud have been cautious about large capital commitments to West African data center regions partly because latency to hyperscaler backbone nodes is too high for latency-sensitive workloads and partly because network resilience guarantees are difficult to provide when bandwidth concentration risk is high. A trans-Atlantic route that decouples West Africa’s connectivity from the Mediterranean would materially change that calculus.
Advertisement
What Enterprise Architects and Connectivity Buyers Should Do About It
1. Model Your Latency Exposure Under a Single-Route Failure Scenario
Most enterprise connectivity teams in Africa have never stress-tested what happens to their applications under a concurrent multi-cable disruption on their primary routes. This is not a theoretical risk: the January 2024 West Africa cable cut took out multiple cables in the same corridor simultaneously. Before Via Africa is available (3 to 4 years minimum), enterprises should identify their current routing path — typically through the ISP’s upstream to a Mediterranean cable system — and assess which business-critical applications have no failover path if that route degrades.
The practical tool is a BGP looking glass or traceroute service that shows the actual routing path your traffic takes from key West African nodes to European cloud regions. Enterprises are often surprised to discover their “direct” AWS or Azure connection transits multiple intermediate countries and cable segments, each a potential failure point. Documenting this exposure is the prerequisite for designing around it.
2. Evaluate Current Cable Carrier Diversity in Procurement Decisions
Via Africa is not available today, but the resilience principle it embodies can be applied now through carrier diversification. West African enterprises purchasing international bandwidth should verify whether their primary and secondary ISP carriers use different cable systems — or whether both route through the same submarine cable infrastructure. Many “dual carrier” arrangements in West Africa use two different ISPs that both ultimately depend on the same cable, providing no resilience against a cable-level disruption.
TeleGeography’s submarine cable map provides a free, accurate reference for verifying which cables each carrier uses. An enterprise buying bandwidth from a Nigerian ISP and its competitor may discover both route through the ACE cable. Adding a third carrier that specifically uses the WACS or MainOne cable (now part of the 2Africa consortium) provides genuine route diversity that survives a single cable-level failure.
3. Track the Via Africa Procurement Process for Early Capacity Access
Via Africa is at the MoU stage as of May 2026, with a route study and cable supplier procurement process coming next. For enterprises and cloud providers seeking to ensure long-term bandwidth security in West Africa, the consortium structure is designed to allow participation: the announcement noted that the project “remains open to additional partners” and that participating investors “take part in governance, enabling investors to participate directly in decisions regarding design, deployment, and operation.” Telecoms, ISPs, and large enterprises with sufficient bandwidth commitments can seek to participate as consortium members rather than simply as future cable capacity customers — a position that provides both supply security and cost advantages.
The timeline for commercial capacity sales (after construction, typically 1 to 2 years into the 3 to 4 year estimate) will be the earliest point at which bandwidth pre-commitment agreements are practically useful. Following Orange’s official project updates will provide the earliest available signal on procurement timeline milestones.
The Structural Lesson
Via Africa’s announcement at the Africa Forward Summit on May 12, 2026 is significant not just as a cable project, but as a signal about how African connectivity is maturing as an infrastructure asset class. The narrative is shifting from “how do we get more bandwidth into Africa?” — the 2010s framing — to “how do we make African connectivity resilient enough that hyperscalers will build infrastructure here and enterprises will trust it for mission-critical workloads?” The answer to the second question is route diversity, geographic de-concentration, and trans-oceanic alternatives that make Africa’s internet topology more robust to the kinds of localized disruption events that have historically knocked out large fractions of West African bandwidth simultaneously.
Via Africa will not be operational for several years, and significant uncertainty remains around capacity specifications, exact routing, and final consortium composition. But the project’s stated design rationale — route diversity and resilience, not just throughput — represents an evolution in infrastructure philosophy that, if executed, makes Africa a more attractive region for the hyperscaler investment the continent needs to lower cloud costs and increase service quality for its 1.4 billion-plus population.
Frequently Asked Questions
How should Algerian enterprises evaluate whether to build on-premise infrastructure or leverage cloud services?
The build-vs-buy decision in infrastructure should be driven by data sovereignty requirements, workload characteristics, and total cost of ownership over a 5-year horizon. For most Algerian enterprises, a hybrid approach — retaining sensitive data on-premise while using cloud for scalable, non-sensitive workloads — offers the best balance. The frameworks described provide evaluation criteria that apply to the Algerian context with minimal adaptation.
What is the realistic timeline for Algeria to close the infrastructure gap with regional peers like Morocco and Singapore?
Current investment trajectory suggests a 5-7 year timeline for Algeria to reach comparable enterprise cloud service availability, assuming continued investment in submarine cable connectivity, domestic data center capacity, and cloud provider market entry. The timeline could compress to 3-4 years with accelerated public-private investment in digital infrastructure as part of the national digital transformation strategy.
Which infrastructure technologies described here can be adopted immediately by Algerian organizations versus which require long lead times?
Software-defined networking, containerization, and cloud-native application architectures can be adopted immediately with existing talent and current cloud service availability. Hyperscale data center build-out, advanced edge computing networks, and submarine cable infrastructure require multi-year planning and significant capital investment. Algerian organizations should focus adoption efforts on the software and tooling layers where they can move quickly.
Sources & Further Reading
- New Orange-Backed Subsea Cable to Connect Nigeria, 19 Other Countries — TechCabal
- Orange and Partners Announce Via Africa Subsea Cable — SubmarineNetworks
- Via Africa Subsea Cable Project — Computer Weekly
- Meta-Backed 2Africa Subsea Cable Completed — Connecting Africa
- Medusa Project to Bridge North Africa with 8.7K Submarine Cable — SubTel Forum
- Submarine Cable Map — TeleGeography


