Supply Chain Disruption Persists Amidst India-Pakistan Conflict: Port Omissions and Vessel Obscurity Raise Concerns
2025-06-10 05:26

Supply Chain Disruption Persists Amidst India-Pakistan Conflict: Port Omissions and Vessel Obscurity Raise Concerns

by John Kuiyaki
Supply Chain Disruption Persists Amidst India-Pakistan Conflict: Port Omissions and Vessel Obscurity Raise Concerns

Despite a ceasefire declaration, the maritime supply chain across the Indian subcontinent continues to face disruption as a result of the recent India-Pakistan conflict. The eeSea has been closely monitoring the evolving situation, and our latest data points to a growing pattern of port omissions, vessel behavior anomalies, and a reconfiguration of regional transshipment hubs.

From a service deployment perspective, several ocean carriers have taken decisive steps to reroute their services, with Karachi port being notably impacted. On the CMA CGM operated MEDEX service, Karachi has been entirely removed from the rotation. Similarly, the ONE operated TIG service has also omitted Karachi, reflecting heightened geopolitical risk assessments and operational concerns in Pakistan’s maritime domain.

In contrast, Sri Lanka’s Colombo port appears to be benefiting from these changes. With the removal of Karachi from several rotations, Colombo is emerging as a key transshipment hub. Carriers are increasingly relying on Colombo to serve as an interim node for cargo that would have previously been routed through now omitted Pakistani ports. This shift underscores Colombo’s strategic relevance and the adaptive capacity of supply chain networks in volatile contexts.

Adding to the complexity, a troubling trend has been observed in vessel tracking data. Multiple vessels have gone dark, disabling AIS transmissions particularly while calling or approaching Indian ports close to the Pakistan border. Last week, the ONE COMPETENCE went dark during its call at Pipavav, raising security and transparency concerns. Similar incidents were recorded on the PS3 service, operated by the Premier Alliance, with the YM UNICORN ceasing AIS transmission just prior to its Pipavav call. Additionally, the SEASPAN JAKARTA, deployed on the HL-UGS | ML-M01 service experienced an AIS blackout immediately after calling Pipavav, staying dark for the nine hours that the vessel was docked in the port.

As the region navigates a fragile post-conflict phase, the ripple effects on maritime logistics are far from over. For ongoing updates and vessel tracking insights, eeSea continues to provide data-driven visibility into evolving service deployments and network performance across impacted regions.