Home
Explore Cables Locations Map ISP status Transit map Country resilience Check my connection
Live Network radar Live Map Cable monitoring Events log Cable incidents Big screen
Learn Research Guide Methodology Latency Overland links Deployments by year Pulse Open dataset API Widgets What's new About Contact

Medusa Submarine Cable System

In Service

8,760 km · 18 Landing Points · 13 Countries · Ready for Service: 2026

Ctrl + Scroll to zoom
Tap to interact with map

Specifications

Length8,760 km
StatusIn Service
Ready for Service2026
Landing Points18
Countries13

Owners

AFRIX Telecom

Landing Points (18)

Location Country Position
Algiers, Algeria DZ Algeria 36.7653°, 3.0318°
Athens, Greece GR Greece 37.9761°, 23.7363°
Barcelona, Spain ES Spain 41.3856°, 2.1688°
Benghazi, Libya LY Libya 32.1166°, 20.0668°
Bizerte, Tunisia TN Tunisia 37.2764°, 9.8674°
Carcavelos, Portugal PT Portugal 38.6902°, -9.3316°
Collo, Algeria DZ Algeria 37.0030°, 6.5572°
Manilva, Spain ES Spain 36.3761°, -5.2505°
Marseille, France FR France 43.2932°, 5.3726°
Mazara del Vallo, Italy IT Italy 37.6501°, 12.5913°

If this cable is cut

What each country and landing point keeps if Medusa Submarine Cable System goes down. A calculation from our cable and landing-point database, not a forecast.

CountryOther international cablesLand linksWhat remains
Libya3 yes reserve of 3 cables
Tunisia5 yes reserve of 5 cables
Syria5 yes reserve of 5 cables
Algeria6 yes reserve of 6 cables
Malta6 no reserve of 6 cables
Morocco7 yes reserve of 7 cables
Portugal11 yes reserve of 11 cables
Greece13 yes reserve of 13 cables
Cyprus13 no reserve of 13 cables
Spain19 yes reserve of 19 cables
Egypt23 yes reserve of 23 cables
France28 yes reserve of 28 cables
Italy33 yes reserve of 33 cables

Landing points with no other cable nearby

  • Collo, Algeria: no other cable lands within 50 km.

On an island this means losing the submarine link; on the mainland traffic can still go over land.

Our alerts on this cable in the last 180 days: 2, last on 11 Oct 2026. Events feed →

Counted: other international cables landing in the same country (domestic cables between points of one country are not a way out), other cables at landing points within 50 km, and whether the country has land links. Not counted: cable capacity, operator contracts and satellite. Use as a first look at dependence, not as a statement of what would happen.

Load profile

+2.7% above night floor · typical for this hour
moderate daily load: +11% at peak hours · usual peak 19:00 UTC · 2 corridors
100 0006121823 02:00 UTC · +6.6%03:00 UTC · +3.2%04:00 UTC · -2.5%08:00 UTC · +3.1%09:00 UTC · +2.9%10:00 UTC · +2.7%11:00 UTC · +2.7%12:00 UTC · +2.7%14:00 UTC · +3.5%15:00 UTC · +7.8%16:00 UTC · +3.0%18:00 UTC · +4.4%19:00 UTC · +11.3%20:00 UTC · +2.7%22:00 UTC · +4.0%23:00 UTC · +3.7%
Indirect estimate from diurnal latency rise under load (queueing delay), normalized per corridor to its night floor. This is NOT operator utilization data.

Live Performance

893
measurements
21
probes
229
days monitored
185.2
ms avg RTT
2
anomalies

Monitored from 2026-03-02 through 2026-10-17 - live ICMP round-trip time measurements via our monitoring probes. All values below are recomputed daily from raw probe data.

Measurement sources

Probe Location Samples Avg Min-Max Last seen
#65128 control probe 197 216.7 ms 81.6-765.5 2026-10-17
#6427 own probe Sydney AU 152 278.2 ms 251.5-846.2 2026-10-15
#61129 control probe 125 89.8 ms 73.9-107.5 2026-06-20
own probe Odessa UA 125 78.4 ms 30.7-109.4 2026-10-15
own probe Minsk BY 107 93.2 ms 56.5-142.3 2026-10-12
own probe Balancer IL 38 96.7 ms 89.8-111.0 2026-10-15
own probe Sevastopol UA 34 257.1 ms 93.4-781.0 2026-10-15
own probe Almaty KZ 13 117.1 ms 113.2-119.6 2026-10-12
own probe Tbilisi GE 12 292.4 ms 102.9-466.6 2026-10-12
own probe Jerusalem IL 12 604.2 ms 84.5-764.8 2026-10-12
own probe Moscow RU 10 447.1 ms 88.1-536.9 2026-10-12
#6410 own probe Sao Paulo BR 9 205.5 ms 205.5-205.5 2026-10-12
#6568 own probe Singapore SG 9 187.5 ms 187.3-187.9 2026-10-12
#7062 own probe Cape Town ZA 9 171.4 ms 168.7-177.5 2026-10-12
own probe Saint Petersburg RU 9 77.8 ms 74.1-82.9 2026-10-12
own probe Rostov RU 9 112.8 ms 100.6-191.2 2026-10-12
own probe DVM IL 9 705.0 ms 596.2-760.8 2026-10-12
own probe Ekaterinburg RU 9 716.2 ms 604.2-777.3 2026-10-12
#724 control probe 2 238.8 ms 229.9-247.7 2026-03-28
own probe Kyiv UA 2 69.4 ms 64.5-74.4 2026-07-09

About the Medusa Submarine Cable System Cable System

Medusa is a 8,760 km submarine cable system that lights up in 2026 and links the Mediterranean rim. It lands in a remarkable eighteen stations across thirteen countries - from Carcavelos and Sesimbra on the Portuguese Atlantic, along the Spanish Mediterranean coast at Barcelona, through Marseille in France and Mazara del Vallo in Sicily, to Algeria, Tunisia, Libya (Bizerte, Benghazi, Misuratah, Tripoli), Malta, Greece, Cyprus, Egypt (Port Said), and Morocco. The cable was designed specifically to bypass the chokepoints of the Red Sea route and to create a Mediterranean backbone that keeps its traffic on European and North African soil.

What makes Medusa notable - and what our data confirms - is its modern architecture. Twenty-four fibre pairs running through a single cable body, with a design capacity of 480 Tbps. For comparison, the 2011 Europe India Gateway along a similar route carries 3.84 Tbps on two pairs. Medusa's total capacity is more than 125 times its decade-older neighbour.

The asymmetry in our data

Our monitor has been measuring Medusa between its Port Said (Egypt) and Carcavelos (Portugal) landings - the cable's full east-to-west traversal. Over 30 days we collected 42 clean samples split across two directions:

DirectionSamplesMin RTTAvgMaxStdDevHops
Port Said → Carcavelos3277.8 ms95.0 ms247.7 ms~20 ms16-17
Carcavelos → Port Said10229.9 ms238.8 ms247.7 ms~7 ms17

Show Medusa Submarine Cable System on the interactive cable map

A 152-millisecond gap between the two minimums. Not a transient - it has persisted for at least 30 days. The forward direction minimum of 77.8 ms is actually below the physics floor for Medusa's full 8,760 km length (theoretical: 85.7 ms). That is physically impossible if the packet traverses the entire cable. The real path is shorter - approximately 8,000 km - which corresponds to a direct Mediterranean crossing from the Eastern to Western Med without circling through all of Medusa's Libyan, Algerian, and Tunisian landings.

The return direction at 229.9 ms is another 150 ms on top, consistent with a more circuitous route that likely does traverse one or more intermediate landings and peering points. We cannot tell from outside which specific cable (possibly another Mediterranean cable like 2Africa or a pre-existing system) handles the return. What we can tell is that two directions of the same source-destination pair take notably different physical paths.

What 24 fibre pairs buys you

A fibre pair is the minimum unit in which a submarine cable can sell capacity - two strands, one for each direction of data. Two decades ago, cables went to sea with two to four pairs. Modern cables are pushing twenty-four. Why?

Fibre is cheap. Once you have already built and laid the physical cable body, added power feed equipment on each end, and placed submarine repeater amplifiers every ~80 km, the incremental cost of packing more fibres into the same bundle is small compared to the value of additional wavelengths. Medusa's twenty-four pairs mean twenty-four completely independent optical paths between any two landings - each capable of being lit with a set of coherent transponders carrying 200 or 400 Gbps per wavelength across roughly 80 wavelengths. The arithmetic: 24 pairs × 80 wavelengths × 200 Gbps = 384 Tbps, near the cable's rated 480 Tbps design.

Hyperscaler consortium cables - where Google, Meta, Amazon, and Microsoft own capacity - tend to justify fibre-pair counts in the teens. Carrier-consortium cables for national telecom operators have been quicker to adopt the highest counts. Medusa is the latter: its co-owners include operators from each landing country, who each take ownership of one or more dedicated pairs. The remaining capacity is sold into the wholesale market.

Eighteen landings, thirteen countries

CountryLanding(s)
PortugalCarcavelos, Sesimbra
SpainBarcelona
FranceMarseille
ItalyMazara del Vallo (Sicily)
MoroccoNador, Tétouan
AlgeriaAlgiers, Collo
TunisiaBizerte
LibyaTripoli, Misuratah, Benghazi
MaltaMellieha
GreeceAthens
CyprusYeroskipos
EgyptPort Said

The shape of this list matters. Medusa is not a point-to-point cable. It is a Mediterranean backbone, designed so any two landings can communicate over its fibre without going through a third country. Previously, most inter-Mediterranean traffic hopped through one or two large hub cities (Marseille, Palermo, Marseille again) on other cables. Medusa collapses this: a packet from Algiers to Athens can ride Medusa directly, without transit routing through a French or Italian peering point.

There is a strategic context too. The Red Sea route - the traditional Europe-to-Asia submarine path through Suez - has seen repeated cable faults in recent years, with a combination of anchor strikes and geopolitical tensions affecting traffic. Medusa is a pure Mediterranean cable, not a Europe-Asia system; it does not solve the Red Sea problem directly. But by strengthening the internal connectivity of the Mediterranean, it reduces the pressure on long-haul cables for regional hops and keeps North African and European traffic on a single shared fabric.

Libya, three landings

Medusa is unusual in giving Libya three separate landings: Tripoli in the west, Misuratah in the centre, and Benghazi in the east. Most cable systems that touch Libya land at one point only. The three-landing design is a response to practical realities: Libya has had no stable national telecom backbone for over a decade, and connectivity between its western and eastern regions is unreliable by land. Three separate cable landings, on the same cable body, provides redundancy and direct intra-Libyan connectivity that the terrestrial network cannot guarantee.

Whether Libyan carriers exploit this architecture in the near term is a separate question. The cable provides the capability; taking advantage of it requires stable commercial arrangements at each landing, which in turn depend on regulatory and political conditions. For now, the cable is lit and available; the market will follow.

What our data proves

Three concrete observations from 42 measurements:

  • The cable works. Port Said → Carcavelos at 77.8 ms is near the physics floor for a direct Mediterranean crossing. Medusa is delivering fast, stable latency along its primary backbone route.
  • Return path is different. 229.9 ms on the reverse corresponds to roughly 23,500 km of fibre - clearly using a different, longer route than Medusa itself, consistent with carriers preferring a specific direction for commercial reasons.
  • Modern capacity unlocked. 24 fibre pairs × 480 Tbps rated design is a step change in Mediterranean connectivity. The value will manifest over years as carriers migrate traffic onto Medusa and away from legacy systems like EIG's Mediterranean leg.

Medusa is the opposite of a hyperscaler cable. Its sponsors are telecom operators, not cloud giants. Its mission is to densify regional connectivity, not to sprint across an ocean. But in the Mediterranean, where a dozen countries ring a sea that has been a commercial crossroads for three thousand years, that mission might be exactly right. Our 77.8 ms measurement is the first reliable latency number this cable will produce. Years of infrastructure on top of it will use that number as the baseline.

Try it yourself

Live data on the Medusa cable page. For context on Mediterranean and Europe-Asia cables, see EIG (2011 consortium trunk, 2 pairs) and Nuvem (2026 Google Atlantic cable with four landings). Our open measurement data refreshes every two hours.

What next: Explore Medusa Submarine Cable System on the interactive submarine cable map, browse the full catalog of submarine cables, or follow live network events and real-world internet latency.

Health

Status✓ Normal
RTT83.67 ms / base 366.08 ms
Last checked2026-10-17 18:32

Monitored by our probe network. Open monitoring →

RTT History

Route: #65128 → Carcavelos Measured: 2026-10-17 18:32
83.7 ms
Min Avg Max #
7 days 83.5 383.7 765.5 53
30 days 81.6 354.1 765.5 93
60 days 81.6 216.7 765.5 197

Health Timeline

Wed, Oct 14
View full event log →
Hop Anomaly
10ms → 101ms (9.88×)
12:31
Mon, Oct 12
View full event log →
Hop Anomaly
51ms → 194ms (3.81×)
20:01
Carcavelos
Resolved
214ms → 84ms
04:32
Carcavelos
Improving
214ms → 211ms
03:33
Hop Anomaly
13ms → 239ms (17.94×)
02:00
Sun, Oct 11
View full event log →
Hop Anomaly
107ms → 734ms (6.84×)
21:30
Carcavelos
RTT Spike
357ms → 720ms (2.02×)
21:02
Carcavelos
RTT Spike
357ms → 720ms (2.02×)
21:02
Carcavelos
RTT Spike
326ms → 715ms (2.19×)
20:31
Carcavelos
RTT Spike
326ms → 715ms (2.19×)
20:31
Carcavelos
Anomaly Confirmed
295ms → 711ms (2.41×)
20:31
Carcavelos
RTT Spike
295ms → 711ms (2.41×)
20:31
Carcavelos
RTT Spike
271ms → 570ms (2.10×)
20:01
Carcavelos
RTT Spike
271ms → 570ms (2.10×)
20:01
Carcavelos
Anomaly Confirmed
243ms → 649ms (2.68×)
19:31
Carcavelos
RTT Spike
243ms → 649ms (2.68×)
19:31
Carcavelos
Alert Created
214ms → 667ms (3.12×)
18:32
Carcavelos
Anomaly Confirmed
214ms → 667ms (3.12×)
18:32
Carcavelos
RTT Spike
214ms → 667ms (3.12×)
18:32
Carcavelos
RTT Spike
186ms → 632ms (3.39×)
16:31
Carcavelos
RTT Spike
186ms → 632ms (3.39×)
16:31
Hop Anomaly
36ms → 115ms (3.20×)
16:30
Carcavelos
RTT Spike
167ms → 474ms (2.83×)
14:31
Carcavelos
RTT Spike
167ms → 474ms (2.83×)
14:31
Carcavelos
Resolved
112ms → 81ms
06:03
Carcavelos
Improving
112ms → 82ms
05:04
Carcavelos
Improving
112ms → 99ms
04:06
Carcavelos
Anomaly Confirmed
136ms → 631ms (4.64×)
03:08
Carcavelos
RTT Spike
136ms → 631ms (4.64×)
03:08
Carcavelos
Alert Created
112ms → 568ms (5.08×)
03:08

Incident history

Significant latency incidents our probes detected on this cable, each with its own report.

All cable incidents →

FAQ

Who owns the Medusa Submarine Cable System?
The Medusa Submarine Cable System is owned by AFRIX Telecom.
When will the Medusa cable system be in service and when was it built?
Medusa is scheduled to go into service in 2026. It was not yet constructed as of that year, but the construction plans were finalized for deployment in the following years.
What countries does the Medusa cable route pass through?
The Medusa cable system routes through Algeria, Cyprus, Egypt, France, Greece, Italy, and several others including Malta, Morocco, Portugal, Spain, and Tunisia.
How many fiber pairs does the Medusa cable have, and what technology is used?
The Medusa cable system consists of 24 fiber pairs. It utilizes modern submarine cable technology to ensure high-speed data transmission.
Why was this specific routing chosen for the Medusa cable system?
This routing was chosen to bypass traditional chokepoints, particularly in the Red Sea region, and to create a more direct and secure backbone for traffic within the Mediterranean region, ensuring better control over data flow.
Medusa Submarine Cable System
  • Length8,760 km
  • StatusIn Service
  • Ready for Service2026

Calculate Cable Distance

Find the actual cable routing distance between any two cities

Open Calculator →
Submarine cables Land fiber Live probes
Explore GeoCables: interactive submarine cable map · all 723 submarine cables · live internet latency map · cable landing points worldwide

Log In

Access your routes, favorites, and API key

Create account Forgot password?