Maersk and Hapag-Lloyd send Gemini IOS service back through Red Sea

Maersk and Hapag-Lloyd will reroute their Gemini Cooperation Indian Ocean Service (IOS) through the Red Sea starting November 2026, abandoning the longer Cape of Good Hope passage that has defined the service's routing since regional security conditions forced carriers away from Suez.

The decision follows a review of the security situation in the region, according to Hapag-Lloyd, which framed the change as a way to deliver faster connections between Europe and the Middle East. The revised routing begins with selected sailings only — and the carriers themselves flag the caveat: everything depends on operational conditions on the water.

Which vessels sail first?

The schedule details are specific, which is worth noting because provisional dates in this corridor rarely survive contact with reality.

• The first westbound sailing under the revised routing falls to Atlanta Express, voyage 644W, expected to depart Salalah on 4 November 2026.
• The eastbound counterpart, Savannah Express, voyage 644E, is scheduled to leave Tangier on 12 November 2026.

Both dates remain provisional and may shift, the carriers said, depending on operating conditions.

What does the change actually cover?

For shippers moving cargo between Europe and the Middle East, the shift is commercially meaningful. The Cape of Good Hope routing adds thousands of nautical miles and corresponding days of transit compared with the Red Sea and Suez corridor. By restoring the shorter passage for IOS, Maersk and Hapag-Lloyd aim to offer a more efficient connection on this specific Europe–Middle East trade, with knock-on effects for equipment positioning and schedule reliability that shippers on the lane will feel faster than carriers' network averages suggest.

But the limits of the announcement matter as much as the announcement itself. This is a single-service adjustment within the Gemini Cooperation network, not a fleet-wide strategic reversal. The carriers said the move reflects their ongoing assessment of routing options in response to regional security developments — careful language that commits them to nothing beyond IOS.

Crucially, the rerouting does not signal a wider return of the entire Gemini network to the Red Sea and Suez Canal. The bulk of Maersk and Hapag-Lloyd's Asia–Europe capacity continues to route via the Cape unless and until the carriers say otherwise — and they have not said otherwise.

What are the carriers not saying?

Hapag-Lloyd stated that crew safety, vessel security and cargo protection remain priorities, and that it will continue monitoring regional conditions and informing customers of further operational changes. That is standard assurance language, and shippers should read it as such: a promise of communication, not a guarantee of continuity.

What the announcement does not contain is equally telling. There is no commitment on how long the Red Sea routing will hold, no threshold for reverting to the Cape, and no indication of whether other Gemini services are under active review for similar changes. For forwarders planning commitments into 2027, that gap leaves the door open in both directions — a broader Suez return if security holds, or a quiet reversal of IOS if it does not.

The move marks another operational adjustment within the Gemini Cooperation as Maersk and Hapag-Lloyd calibrate routing against regional security developments. Whether November's Salalah departure becomes the first of many Red Sea transits, or an isolated experiment cut short by conditions, will depend on factors the carriers can monitor but not control.