15,000 km · 6 Landing Points · 6 Countries · Ready for Service: 2023
| Length | 15,000 km |
|---|---|
| Status | In Service |
| Ready for Service | 2023 |
| Landing Points | 6 |
| Countries | 6 |
| Location |
|---|
| Lagos, Nigeria |
| Lome, Togo |
| Melkbosstrand, South Africa |
| Rupert's Bay, Saint Helena, Ascension and Tristan da Cunha |
| Sesimbra, Portugal |
| Swakopmund, Namibia |
Equiano is Google's privately-funded submarine cable system connecting Europe and Africa. Activated in stages between 2022 and 2023, it runs roughly 15,000 km from Sesimbra in Portugal down the entire west coast of Africa to Melkbosstrand near Cape Town, with branch landings at Lagos (Nigeria), Lomé (Togo), Swakopmund (Namibia), and the remote British Overseas Territory of Saint Helena. The cable is named after Olaudah Equiano, the 18th-century writer and abolitionist born in what is now southern Nigeria.
What makes Equiano interesting from a measurement perspective is that it represents a deliberate attempt by a single hyperscaler — Google — to bypass the traditional consortium model of submarine cable financing. Instead of waiting for telcos to negotiate capacity, Google built the cable for its own traffic, then sold the surplus to local operators. This is part of a broader pattern (Curie, Dunant, Grace Hopper, Equiano, Firmina, Topaz) where the cloud companies have become primary funders of intercontinental subsea infrastructure.
Before Equiano, traffic between European data centers and most West African landing points typically detoured through older systems like SAT-3/WASC, WACS, or ACE. Many of those cables share common landing points and are aging — SAT-3 dates back to 2002. Equiano roughly tripled the available capacity on the West Africa → Europe corridor and introduced direct fiber paths to landing points that previously required transit through other countries.
For end users in countries like Nigeria, Togo, and Namibia, this matters in a way that doesn't always show up in marketing slides: it's not just about raw bandwidth, it's about route diversity. When ACE has a fault (which has happened multiple times in the past five years, sometimes affecting 13 countries simultaneously), Equiano provides an alternative path that doesn't share the same chokepoints. Resilience comes from having more than one cable.
GeoCables tracks Equiano through RIPE Atlas measurements launched from probes we operate in Minsk, Almaty, Tbilisi, Jerusalem, and Sevastopol. The most consistent data we have is on the Sesimbra–Melkbosstrand corridor, which is the cable's longest single segment and the one most directly comparable to "raw" Equiano performance.
| Direction | Measurements (30d) | Min RTT | Avg RTT | Max RTT |
|---|---|---|---|---|
| Sesimbra → Melkbosstrand | 43 | 203 ms | 205 ms | 225 ms |
| Melkbosstrand → Sesimbra | 16 | 182 ms | 189 ms | 204 ms |
Two things stand out. First, the latency is rock-solid: across 59 measurements over 30 days, we never saw a spike, never saw packet loss, never saw a routing flap. For a 15,000-km undersea path crossing the equator twice, that level of stability is the engineering goal of these systems and Equiano delivers it.
Second, there's a small but persistent asymmetry: the Cape Town → Lisbon direction is consistently 15-20 ms faster than the reverse. That's not unusual on long submarine paths — return traffic often takes a slightly different routing inside the destination country, and BGP path selection isn't symmetrical. The point is that the asymmetry is stable and predictable, which is what you want from a well-engineered backbone.
The Sesimbra–Melkbosstrand great-circle distance is roughly 8,000 km. Light in optical fiber travels at about 200,000 km/s — two-thirds of vacuum speed of light, because of the refractive index of glass. The theoretical minimum round-trip time on a perfect 8,000 km path is therefore:
(8,000 km × 2) ÷ 200,000 km/s = 80 ms
Our measured average is 205 ms — about 2.5 times the theoretical floor. Where does the other 125 ms go? A few sources, in rough order of contribution:
A 2.5x ratio between theoretical and measured RTT is normal for transoceanic links. Our other measurements across Atlantic and Pacific cables show similar multipliers. The cable itself is rarely the bottleneck once it's built — the bottleneck is everything that wraps around it.
Equiano is one of the more stable cables in our monitoring set, so we don't expect frequent alerts. What we do expect to track over the coming months:
If you want to follow Equiano in real time, the live cable health monitor on our home page surfaces any RTT anomaly we catch, and the route calculator lets you see whether a given source-destination pair is likely to traverse this specific cable.
Equiano was built with twelve fiber pairs using space-division multiplexing (SDM) — at the time of its activation it was one of the highest-fiber-count subsea cables in service. Total designed capacity is around 144 terabits per second. The cable was manufactured and laid by Alcatel Submarine Networks (now Nokia ASN), the same vendor behind most of Google's other private cables. The branching units that route traffic to Lagos, Lomé, Swakopmund, and Saint Helena are remotely reconfigurable, which gives the operator some flexibility to rebalance capacity between landings as demand grows in different markets.
One subtle but interesting design choice: Equiano's spur to Saint Helena is the first time the island has had a fiber-optic submarine cable. Before 2022, the island's roughly 4,500 residents relied entirely on satellite for international connectivity. The Saint Helena landing was funded in part by the European Development Fund as a digital-inclusion project — a reminder that submarine cables are not purely a commercial story, they are also infrastructure decisions with measurable consequences for who gets to participate in the modern internet.
| Status | ✓ Normal |
|---|---|
| RTT | 143.67 ms / base 144.94 ms |
| Last checked | 2026-04-17 20:31 |
Monitored using RIPE Atlas probes. Open monitoring →
| Min | Avg | Max | # | |
|---|---|---|---|---|
| 7 days | 143.0 | 145.4 | 149.8 | 8 |
| 30 days | 143.0 | 193.9 | 225.1 | 44 |
| 60 days | 143.0 | 196.0 | 225.1 | 57 |
Find the actual cable routing distance between any two cities
Open Calculator →