AE15 Went Back to Suez the Day After a Red Sea Attack. Here's the Watch List to July 24

Maersk and Hapag-Lloyd announced on July 6 that the AE15, a Gemini Cooperation service connecting Asia with the Mediterranean, will sail via Suez instead of the Cape of Good Hope. The timing is awkward: the announcement landed one day after a Red Sea attack off Yemen and just before a fresh escalation around the Strait of Hormuz. If you have cargo booked on this service, or you are weighing a shift to it for the transit-time gain, the question between now and the first canal transit is not only what the advisory says. It is what would make the carriers use the reversal clause written into it.

The week in sequence

The timing of the announcement against this week’s incidents is the whole story.

Date	Event
July 5	A cargo ship reports an attack by unknown armed assailants 30 nautical miles southwest of Hodeidah in the Red Sea. A skiff opened fire; armed guards on board returned fire; the vessel and crew were reported safe. No group immediately claimed responsibility.
July 6	Maersk and Hapag-Lloyd issue the AE15 advisory: the service moves to the trans-Suez route, with Majestic Maersk named as the first sailing. The published rotation is Qingdao – Kwangyang – Ningbo – Tanjung Pelepas – Port Said – Damietta – Colombo – Singapore.
July 7–8	A Qatari LNG tanker, Al Rekayyat, is struck by a projectile near the entrance to the Strait of Hormuz and close to Oman’s coast, sparking an engine-room fire. Reuters reports that the US military said two other tankers had also been targeted by Iran, while Axios reports that US forces struck Iranian military targets near Hormuz in response to renewed attacks on commercial vessels. The commercial shipping threat level for Hormuz is raised to severe.
Late July	Majestic Maersk is expected to make the first AE15 Suez transit under the revised routing, subject to carrier schedule confirmation.

Sources: UKMTO/AP, Maersk customer advisory, Reuters, Axios. Full links in Further Reading.

Two things are worth keeping distinct. The Strait of Hormuz and the Red Sea are separate chokepoints, and the AE15 does not transit Hormuz. The July 5 Red Sea incident remains a single, unclaimed event. The Hormuz escalation does not directly change the AE15 route, but it does matter because Maersk’s advisory makes the change conditional not only on Red Sea stability, but also on the absence of wider regional escalation. As of July 9, no AE15 reversal has been announced and the advisory stands.

What the advisory actually commits to

The routing is explicitly conditional. Maersk’s advisory ties the change to continued stability in the Red Sea area and to the absence of escalation in the wider region. That regional framing matters this week: it means the reversal trigger is broader than a Red Sea attack alone.

Reversal operates at two levels. The carriers state they can revert individual sailings or move the entire service back to the Cape of Good Hope. For cargo planning, those are different events. A per-sailing reversion means your specific booking can go around Africa while the service nominally remains trans-Suez. A structural reversion resets the whole schedule.

Nothing else is moving. Maersk states there are no current plans to return other Gemini services to Suez and no consideration of a wider East–West network change. AE15 is a single-service move, which is also how February’s return was framed. Our earlier read on which lanes the AE15 shift touches is in One Gemini Service Is Back on Suez.

February is the template for what a reversal looks like

This is the second Gemini attempt at Suez this year. In early February, the cooperation announced that the IMX/ME11 service, connecting India and the Middle East with the Mediterranean, would return to the Red Sea and Suez from mid-February. By March 1, Maersk had paused future trans-Suez sailings through Bab el-Mandeb and rerouted ME11 and MECL around the Cape of Good Hope after the Middle East security situation deteriorated.

The operational lesson from that cycle sits with the cargo that was mid-plan when the reversal came. Bookings made against trans-Suez transit times were re-routed onto Cape schedules, and the transit-time assumption baked into downstream planning — inland bookings, free time windows, customer delivery commitments — was the thing that broke. The advisory changed quickly; the plans built on it took longer to unwind.

The watch list before the first transit

Confirm which routing your booking actually rides. A service-level announcement is not a per-sailing confirmation, and the carriers have reserved exactly that gap. For each AE15 booking, verify the named vessel and its routing rather than assuming the advisory applies to it.

Treat the first Majestic Maersk transit as the marker. Until the first vessel clears the canal, the return is announced rather than demonstrated. If your cargo is on a subsequent sailing, its routing risk is priced off what happens to this one.

Watch the reversal signals, not the headlines. The February cycle shows the chain: regional escalation, renewed attack risk in the Red Sea corridor, then a carrier advisory. UKMTO incident reports for the southern Red Sea and Bab el-Mandeb, war-risk insurance moves, and Gemini customer advisories are the sequence to monitor. Hormuz coverage is loud this week, but the AE15 routing decision still runs through the Red Sea corridor.

Re-check the assumptions built on the shorter transit. If a booking was shifted to AE15 for the Suez transit time, the downstream schedule inherits the reversal risk: delivery commitments, free time at destination, and any inland legs booked against the earlier arrival. Holding a Cape-equivalent buffer on critical cargo until the routing is demonstrated costs less than re-planning after an advisory.

If your team is confirming routings sailing by sailing across carrier advisories this month, walk through how ops teams track routing changes at the vessel and milestone level instead of re-checking advisory pages.