Use case: LSP ops teams needing a fast, source-based view of what changed (insurance + carrier operating decisions), plus what to do in the next 72 hours.


60-second take

  • Insurance is the gating item: Multiple P&I clubs have issued war-risk cancellation notices for non-mutual / fixed-premium war-risk covers, mainly affecting Iran/Iranian waters (to 12nm) and the Persian/Arabian Gulf + adjacent waters. Many notices converge on 00:00 GMT, 05 Mar 2026 (some earlier).
  • Carrier network changes are already live: Major carriers have issued operational advisories (safe-shelter instructions, suspension of certain transits, and Cape of Good Hope reroutes). Expect immediate schedule instability, blank sailings, and rolled cargo.
  • Do not treat “Hormuz closure” claims as settled: UKMTO has reported VHF “closure” claims that cannot be independently verified. Treat the environment as highly volatile and operate off official advisories + your carriers’ instructions.

A) War-risk insurance: what changed (operational view)

What to assume: If your cargo or contracted services rely on war-risk cover under non-mutual/fixed-premium extensions, you may face rapid changes in “can we legally/commercially transit” decisions. Many clubs note that cover may be reinstated with new exclusion wording or handled via individual buy-back / special acceptance.

Issuer (examples)Notice dateEffective time (GMT)Area referenced (high level)Ops implication
Gard P&I01 Mar00:00, 05 MarIran/Iranian waters (to 12nm) + Persian/Arabian Gulf & adjacent watersExpect routing/acceptance decisions to tighten; confirm cover position per shipment/contract.
Skuld01 Mar00:00, 05 MarSame structure (Iran + Gulf/adjacent waters)Same: validate if any buy-back/individual reinstatement is available for your move.
American P&I Club01 Mar00:00, 05 MarPersian/Arabian Gulf + Gulf of Oman (as defined) and Iran/Iranian watersRe-check liability/cover assumptions for Gulf transits and service commitments.
London P&I Club01 MarTypically 05 Mar (per notice terms)Iran/Iranian waters + Persian/Arabian Gulf & adjacent watersDo not assume prior cover still applies; confirm per assured and voyage segment.
Steamship Mutual01 Mar00:00, 04 MarIran/Iranian waters + Persian/Arabian Gulf & adjacent watersEarlier effective timing than the 05 Mar cluster; prioritize checks now.
West of England P&IMar updatePer notice termsWar risks liabilities arising in Iran and the Persian/Arabian Gulf (non-mutual business)Confirm scope for fixed premium/charterers covers; mutual P&I/FD&D may be treated differently.
UK P&I Club28 Feb00:00, 03 MarNon-mutual war risks coverage changes (Iran + Gulf region)Some clubs moved earlier; don’t anchor only on “05 Mar”.
Shipowners’ Club02 MarPer notice termsNon-mutual covers (war risks cancellation / alteration notices)Validate if your cover is within scope (fixed premium / non-mutual extensions).

Practical reading: Treat insurance as a go/no-go constraint. If you do not have explicit confirmation of cover (or a documented alternative), plan as if Gulf/Hormuz legs can be delayed, rerouted, or paused on short notice.


B) Carrier advisories: what operators are doing now

CarrierDated advisoryAction (ops-relevant)What to expect downstream
Maersk01 MarPaused future Trans-Suez sailings through Bab al-Mandeb; rerouted ME11/MECL via Cape of Good Hope.Longer transit times, changed cutoffs, connection misses, rolled bookings; monitor service-specific notices.
CMA CGMUpdate #1Vessels inside/bound to Gulf instructed to proceed to shelter; Suez transits suspended; reroute via Cape.Port-call changes, alternative discharge planning, backlog risk when operations resume.
CMA CGMAdvisory #3 / #4Suspended reefer and dangerous goods bookings to/from listed Middle East/Red Sea countries until further notice.Immediate booking disruption; equipment repositioning constraints; special handling cargo most exposed.
MSCEarly MarInstructed vessels operating in / en route to Gulf region to proceed to designated safe shelter areas until further notice.High variability in ETAs; potential pauses at approach points; rapid changes to port rotations.
Hapag-LloydLate Feb / early MarPublished “Suspension of Strait of Hormuz transits due to security closure” and announced a War Risk Surcharge for Gulf-related cargo.Transit suspensions and/or extra cost layers; confirm per service and booking instruction.

Ops takeaway: When carriers diverge (shelter vs reroute vs suspend), ops teams lose time chasing updates in multiple portals. A single multi-carrier tracking view from supply chain data platform like Tradlinx helps maintain one source of truth for ETAs, exceptions, and customer updates.


C) Official threat advisories (what they actually say)

  • US MARAD MSCI Alert (2026-001A): cites significant military activity starting 28 Feb and recommends vessels keep clear where possible and maintain standoff distance guidance for US-connected commercial vessels.
  • UKMTO Advisories: describe the environment as highly volatile and warn of electronic interference (GNSS/AIS/VHF). UKMTO reports unverified VHF “closure” claims and notes they are not independently verified.
  • Industry guidance (e.g., INTERTANKO): advises delaying Hormuz transits where possible, liaising with NCAGS/EUNAVFOR/UKMTO, and applying BMP maritime security practices.

Important nuance: Some carrier statements describe an “official/security closure” posture, while UKMTO reporting emphasizes that “closure” claims have not been independently verified. Operationally, the safe assumption is exception-prone routing with high interference and fast-moving risk. Use carrier instructions for the shipment-level decision, and use MARAD/UKMTO for situational awareness and security posture.


D) 72-hour action checklist (LSP ops)

  1. Segment exposure: pull a list of shipments with legs touching Red Sea / Bab al-Mandeb / Gulf of Oman / Strait of Hormuz / Persian Gulf, including feeder connections.
  2. Confirm insurance position per move: do not rely on assumptions. Ask your insurer/broker or contractual counterpart whether cover is active, excluded, reinstated with exclusions, or available via individual acceptance/buy-back.
  3. Lock the carrier reality: for each booking, capture the latest carrier instruction (shelter, reroute, suspend, or accept). Record the timestamp and publish a “single source of truth” internally.
  4. Rebuild ETAs using buffers, not point estimates: move from “ETA date” to “ETA range + next decision point” (e.g., “next carrier update window”).
  5. Prepare alternates: pre-plan discharge and inland options for high-priority cargo (and document what requires new customs handling).
  6. Special cargo triage: reefer and DG shipments should be isolated first because booking suspensions and safety constraints can apply unevenly.
  7. Customer communications: send a short notice with (a) what changed, (b) what it means for ETA reliability, (c) when the next update is expected, (d) what decisions you need from them (priority ranking, substitution, air uplift rules).

Many teams read disruption updates but still chase milestones manually. Tradlinx provides event-based container visibility (e.g., gate-in/out, vessel departure/arrival) and API integration so workflows and alerts can run directly inside your systems.


Further Reading (official sources)

Prefer email? Contact us directly at min.so@tradlinx.com (Americas), sondre.lyndon@tradlinx.com (Europe) or henry.jo@tradlinx.com (EMEA/Asia)

Leave a Reply

Trending

Discover more from Tradlinx Blogs

Subscribe now to keep reading and get access to the full archive.

Continue reading