Skip to main content
Sofia Connect

Medusa reaches Aqaba through Coral Bridge—but the route still needs a handoff

Aqaba Digital Hub will reach the Medusa network through the Coral Bridge. The commercial value depends on the unannounced route, handoffs and service terms.

Yuliy Nushev5 min read

CEO, Sofia Connect EAD · Honorary Consul of Georgia in Bulgaria

On 1 October, MEDUSA Submarine Cable System and Jordan’s NaiTel signed an agreement to establish MEDUSA colocation capacity at Aqaba Digital Hub (ADH), giving connected operators an access point to MEDUSA through the Coral Bridge. The significance is not a new 8,700-kilometre cable to Jordan: it is a planned handoff from a short Egypt–Jordan link into a wider Mediterranean network. The announcement leaves the commercial path, activation date and service capacity unspecified, so carriers should treat it as a route under development—not yet as a ready-to-order alternative.

A cable-to-cable handoff, not a new branch

The agreement pairs MEDUSA’s Mediterranean system with the Coral Bridge, a 15-kilometre submarine cable across the Gulf of Aqaba linking Aqaba with Taba in Egypt. Telecom Egypt and NaiTel reported completion of its marine installation in August 2025; the system has 48 fibre pairs and a design capacity above 1 Pbps (Telecom Egypt). Those are design specifications, not a statement of customer capacity now available across the entire Aqaba-to-Europe route.

MEDUSA’s announcement describes ADH as a new access point, connected “via the Coral Bridge,” and says MEDUSA will establish colocation capacity at the Aqaba facility (MEDUSA’s 1 October announcement). It does not describe a separate MEDUSA cable branch laid into Aqaba. The distinction matters: the value depends on the interconnection between systems, not simply on adding another name to the landing-point map.

MEDUSA describes its broader system as more than 8,700 km, with 24 fibre pairs and a 25-year design life, spanning landings across Europe and North Africa and extending toward the Red Sea (MEDUSA’s partnership announcement). In its earlier agreement with Telecom Egypt, MEDUSA said its Egyptian landing would connect to Red Sea sites at Suez, Zafarana and Ras Ghareb through Telecom Egypt’s terrestrial crossing network (MEDUSA and Telecom Egypt). The new Aqaba access point therefore sits in a chain of subsea and terrestrial handoffs; the public announcement does not identify the exact transport path from Taba to MEDUSA’s network or the protection arrangement across those handoffs.

A live Mediterranean segment, but phased delivery

There is already a live western section of the MEDUSA system. Orange announced on 3 June 2026 that the Marseille–Bizerte ViaTunisia segment had reached ready-for-service status, creating an operational link between France and Tunisia (Orange). MEDUSA’s project overview lists 2026 as the ready-for-service target for its eastern Mediterranean service (MEDUSA’s project overview).

That phased build is important for customers evaluating the new Jordan access. A commercial route from Aqaba to Europe depends on more than the Coral Bridge being laid: it needs a lit and saleable MEDUSA segment, colocation and cross-connects at ADH, transport across the Egyptian side, and a defined onward service to the customer’s chosen European point of presence. The public agreement confirms a partnership and a planned colocation presence; it does not publish an RFS date, capacity commitment, price, latency target, or service-level agreement.

For a carrier’s route review, the minimum evidence is a physical route diagram, the named interconnection points, and a clear statement of what is sold at each boundary: dark fibre, wavelength, or IP transit. Capacity reservations, maintenance windows and failover tests matter just as much as the design limits of the two submarine systems. Until those are disclosed, buyers cannot compare the proposed path with an existing service on price, restoration time or diversity.

The release also uses “landing point” language for ADH, while describing the connection as running through Coral Bridge. For route engineering and procurement, operators will need to know where the handoff physically occurs, which party supplies each segment, and what happens if one of those segments fails. Without that detail, a route can be geographically attractive on a diagram while remaining difficult to compare with an existing protected service.

The distinction is material to resilience claims. A short cross-border system can create useful geographic separation, but it does not by itself prove that the route is independent end to end. Buyers will want to establish whether the subsea links, terrestrial crossings, landing-station power and onward backbone are protected on separate failure domains. The release announces neither a protected end-to-end product nor a restoration design, so neither should be inferred from the cable-pair counts.

What it means for the region

Aqaba’s importance to Southeast Europe is conditional, not automatic. If MEDUSA’s European landings and Jordan’s access point can be joined under transparent wholesale terms, carriers may gain another way to reach the Levant and wider Middle East from Mediterranean infrastructure. But the announcement does not establish a new end-to-end service to Bulgaria, nor does it show that the route is independent of existing Egypt-facing paths.

For Bulgarian and Balkan network planners, the useful next step is to ask for the route map and service boundary: which MEDUSA segment is offered, how traffic travels between Taba and the MEDUSA network, what is protected, and where traffic can be handed off toward the Balkans. A second path is valuable only if its failure modes and restoration path are genuinely different from the first.

For Sofia Connect and other regional carriers, the agreement is a signal to monitor rather than a product announcement to repeat. The decisive milestones will be an operational colocation point at ADH, a published activation schedule, and a wholesale offer with disclosed capacity and protection. Until those details appear, Aqaba is a promising interconnection node on the map—not a demonstrated new route for traffic between Sofia and the Mediterranean.

Sources

Sofia Connect Insights

Weekly analysis on regional telecom infrastructure

DWDM, submarine cables, IP transit, peering, regulation, M&A — one email per week, written for engineers and decision-makers. No marketing.

By subscribing you agree to receive emails from Sofia Connect EAD. You can unsubscribe at any time. Privacy.