{"id":701,"date":"2026-09-16T03:40:11","date_gmt":"2026-09-16T03:40:11","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/msc-puts-indusa-westbound-through-suez-from-23-september-as-eastbound-stays-on-the-cape\/"},"modified":"2026-09-16T05:29:55","modified_gmt":"2026-09-16T05:29:55","slug":"msc-puts-indusa-westbound-through-suez-from-23-september-as-eastbound-stays-on-the-cape","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/msc-puts-indusa-westbound-through-suez-from-23-september-as-eastbound-stays-on-the-cape\/","title":{"rendered":"MSC Puts Indusa Westbound Through Suez From 23 September as Eastbound Stays on the Cape"},"content":{"rendered":"

Mediterranean Shipping Company said it will partially restore Suez Canal transits on its Indusa service after a review of security and operational conditions in the Red Sea. The string, which connects the Indian subcontinent with the United States and Mexico, will resume Red Sea operations for westbound cargo only. The first vessel under the revised arrangement is MSC Domna X, voyage IV637A, departing Colombo on 23 September 2026. Eastbound Indusa sailings will continue to operate via the Cape of Good Hope.<\/p>\n

MSC said it will update individual booking confirmations and online schedules progressively, and that it will implement the change case by case. Contingency arrangements remain in place, so individual voyages can still be sent back around Africa if conditions change. The company put the safety of seafarers, vessels and customers\u2019 cargo as its highest priority. That is the operator-relevant sentence. A named westbound sailing through Suez is a commercial product. It is not a JMIC, UKMTO or MSCIO downgrade, and it is not a substitute for BMP Maritime Security on a Bab el-Mandeb transit.<\/p>\n

Indusa is a different trade from the Asia\u2013Europe strings that have dominated this month\u2019s canal restorations. Westbound-only Suez means India and Colombo cargo bound for the U.S. East Coast, Gulf and Mexico can take the canal and the Red Sea. Eastbound boxes from those ranges stay on the Cape. That is an asymmetric network, not a corridor reopening. Shippers who have been planning a single Cape transit time in both directions need two schedules from 23 September: a shorter westbound product that still carries a live southern-Red-Sea threat file, and an unchanged eastbound Cape product.<\/p>\n

The ship, the flag and the first sailing<\/h2>\n

MSC Domna X, IMO 9120841, is a Liberia-flagged container ship built in 1997, of 92,198 GT and 110,381 dwt, about 347 metres by 43 metres, with a reported capacity of about 9,578 TEU. Her MMSI is 636022657 and her call sign is 5LJV5. She previously sailed as Ergign Maersk. AIS services placed her on India\u2019s west coast in mid-September, with recent calls at Vizhinjam, Nhava Sheva and Mundra, which is consistent with an Indusa rotation that then offers Colombo as a westbound last-call before the Red Sea.<\/p>\n

The Liberian flag is not a footnote. Liberia has held ISPS Security Level 3 for the Red Sea and Gulf of Aden, covering the NAVCENT box south of 16\u00b0N and west of 46\u00b0E, with additional instructions on drifting mines, AIS mandatory fields and association with Israeli or Saudi interests. A westbound canal transit on a Liberian hull therefore does not reset flag security measures. It puts a Level 3 ship into a corridor that the company has judged workable for that voyage. Company security officers on MSC tonnage, and on any feeder or connecting carrier that loads to IV637A, should treat the Colombo 23 September departure as a Level 3 transit with a Suez schedule attached, not as a return to Security Level 1 because the liner map now shows the canal.<\/p>\n

Indusa\u2019s published geography has varied by schedule, but the commercial shape is stable: Indian load ports including Mundra and Nhava Sheva, a Colombo call, and discharge ranges that take in U.S. East Coast and Gulf ports and Mexico, with some rotations also showing Freeport, Veracruz and connecting Gulf calls. Port Houston\u2019s 2026 container schedule still listed INDUSA among India\/Middle East services calling Houston. Flexport\u2019s service card has described eastbound Mundra\u2013Houston and westbound Mobile\u2013Mundra legs. The 15 September MSC notice does not republish a full berth rotation. It republishes a routing rule. Westbound cargo on this string is being offered the canal. Eastbound cargo is not.<\/p>\n

A fifth MSC string, not a network-wide return<\/h2>\n

This is not MSC\u2019s first partial return to Suez. On 24 August the carrier said that, after a review of Red Sea conditions, it would restore selected eastbound and westbound sailings on four East\u2013West services: Jade (Asia\u2013Mediterranean), Albatros (Asia\u2013northern Europe), Tiger (Asia\u2013Mediterranean, both directions) and Himalaya (India\u2013Mediterranean). The first named ships were MSC Michel Cappellini on Jade, MSC Josefina on Albatros, MSC Anna and MSC Tina on Tiger, and MSC Beryl on Himalaya, with initial sailings from 20 August. Those strings are Asia\u2013Europe and India\u2013Mediterranean. Indusa is India\u2013U.S.\/Mexico. Adding a westbound-only Indusa sailing extends the canal experiment onto a transatlantic and trans-Gulf trade, where Cape extra distance is even more expensive in sea-days and where U.S. Gulf and East Coast receivers have been living with Cape-era transit times since late 2023.<\/p>\n

The competitive clock is already running. Maersk and Hapag-Lloyd said on 14 September that four more Gemini Cooperation services \u2014 AE5, AE11, AE12 and ME2 \u2014 will leave the Cape and transit Suez in both directions, joining AE15 and AE19. The first Gemini westbound sailing is Antonia Maersk, voyage 635W, on AE11 from Tanjung Pelepas on 19 September. MSC\u2019s Indusa first sailing is four days later, from Colombo, and only westbound. Linerlytica said on 14 September that COSCO and OOCL were due to start eastbound Suez transits from 15 September, and that Evergreen, ONE, HMM and Yang Ming had yet to return to the Red Sea. MSC is widening a cautious return. It is not matching Gemini\u2019s two-way restoration, and it is not declaring the southern Red Sea clear.<\/p>\n

The security file the advisory does not cancel is the same file that sits under Gemini. Houthi forces seized Mokha earlier this month, tightening the approach to Perim and the Hanish islands, and Kpler-counted Bab el-Mandeb transits have already printed as low as six ships against about 30 on a recent Friday. The Houthis declared a maritime blockade against Saudi-associated shipping on 20 July. Human Rights Watch said on 15 September that recent Houthi attacks on commercial vessels in the Red Sea and Gulf of Aden most likely amount to war crimes in at least three cases, naming Encelia, Daisy, Tihamah and Amzan among confirmed or claimed targets. A westbound Indusa ship still has to pass that coast. An eastbound Indusa ship on the Cape does not. That is why the split routing is the story, not a slogan about \u201creturning to Suez.\u201d<\/p>\n

The operational implication for cargo interests is concrete. Westbound boxes loaded in Mundra, Nhava Sheva or Colombo for Houston, the U.S. East Coast or Mexico may now show a shorter water transit and a Red Sea war-risk exposure that the Cape sailing did not carry. Eastbound boxes loaded in those U.S. and Mexican ranges will still burn Cape sea-days. Insurance declarations, bunker exposure, detention and missed-window clauses, and any Saudi-associated cargo or ownership feature that a Houthi cell might read as a target, have to be set per direction. MSC\u2019s own language leaves a reversal path. Individual voyages can still be adjusted. A 23 September Colombo departure is enough to recut transhipment and inland cut-offs. It is not enough to treat Jeddah, the southern Red Sea or the canal approaches as a peacetime lane.<\/p>\n

What Operators Should Note<\/h2>\n