Is the Strait of Hormuz Open? Four Tests Before a Restart
JMIC described neutral transit as permitted on August 16, but severe risk and unreliable AIS leave normal service unproven. Import teams need four records.
Primary lensTrade policy
Sub-topicPolicy monitoring
Evidence base10 records used
Use casePolicy monitoring
JMIC still described neutral transit through the Strait of Hormuz as permitted on August 16, and IMO continued to publish transit data through August 13. Neither record proves normal trade is back.
JMIC Update 085, dated August 16, recorded commercial traffic at reduced levels. Independent tracking showed single-digit or no tanker transits in either direction. JMIC reported three confirmed attacks during the prior 72 hours and kept the Strait of Hormuz threat level at severe.
The earlier June notice that called the strait open and moderate cannot carry an August decision. July and August attacks overtook it. JMIC Update 071 still said neutral transit was permitted, but it warned of a severe threat, mine risk, reduced traffic, heavy naval presence, and hostile action considered highly likely.
Transit permission answers one question. It does not answer whether a carrier will accept the voyage, an insurer will cover it on workable terms, a tracker can observe it accurately, or a buyer will receive a named cargo on the date used in its production plan.
A planning-baseline reset needs four records: route, voyage acceptance, corrected flow, and named arrival. A single voyage may proceed under a documented exception, but it must not reset normal lead times or contingency supply.
Transit permission is a route condition
The June open notice is useful as history, not as the current operating record. It shows how quickly a one-word status can detach from the conditions beneath it. That notice reduced the threat level to moderate, described a southern corridor as proven safe, and said blockade operations had ceased. By July 14, JMIC assessed the region at severe and reported attacks on two tankers traveling outbound along that southern route.
Neutral transit remained permitted in the August 16 record. That does not supply the capacity, predictability, or risk level that supported pre-conflict schedules. Permission to pass is not a common-service commitment.
Procurement systems like single status fields. A route marked open can flow into an ETA model, inventory assumption, supplier scorecard, or freight benchmark without carrying the conditions attached to the source. Once that happens, a cautious operational advisory becomes a false declaration of normal service.
The source should travel with the status. A route record should name the issuing body, date, threat level, recommended corridor, mine or clearance restrictions, reporting requirements, and the vessel master's remaining discretion. It should also state whether the route is open to the relevant flag, vessel profile, cargo, and direction of travel. A map that shows a navigable corridor does not prove capacity for every ship that wants to use it.
The first gate asks whether a route is available under the current operating record. Passing it means only that the company can move to the carrier and insurer questions.
The safety record still carries a high-risk signal
The active U.S. record does not describe a normal operating environment. MARAD Advisory 2026-004 says the risk of Iranian attacks against commercial shipping remains high across the Persian Gulf, the strait, and the Gulf of Oman. It identifies missile attacks, armed aerial drones, armed surface vessels, boarding history, and attempts to divert commercial ships.
MARAD also warns of significant interference, spoofing, and jamming affecting satellite navigation. It tells mariners to rely more heavily on radar ranges, visual bearings, and cross-checks against secondary navigation systems. U.S.-flagged commercial vessels are advised to coordinate voyage planning with NAVCENT shipping guidance, conduct a pre-voyage risk assessment, incorporate protective measures, and register with UKMTO 24 hours before entering the Indian Ocean Voluntary Reporting Area.
The August 16 JMIC record and the active MARAD record perform different jobs. JMIC records recent incidents, traffic conditions, permitted neutral transit, and a regional threat assessment. MARAD sets a threat posture and voyage-planning discipline for U.S.-flagged commercial vessels. A company cannot use transit permission from one record to erase the restrictions in the other.
The IMO confirmed-incident list shows why the review date matters. It recorded 65 confirmed incidents and 17 seafarer fatalities as of August 11. JMIC then recorded three attacks on August 14 and 15. The IMO's Middle East status page, with transit data through August 13, also says its evacuation process is paused and more than 20,000 seafarers remain affected.
The second gate belongs to the parties that must accept the voyage. Carrier confirmation should name the service, vessel, route, sailing window, and conditions for cancellation or diversion. Insurance confirmation should identify the covered voyage, premium, exclusions, notice duties, and any change in terms if the security posture moves. Shippers also need to know whether a booking is firm, conditional, or merely available for quotation.
A published sailing schedule is not enough. Nor is a rate request that produces a number but no accepted space. Commercial usability for a purchase order begins when the carrier has accepted the cargo and the insurer has bound coverage on terms the buyer can perform.
AIS cannot carry the proof alone
Visible ship icons create a second false shortcut. A cluster of apparent transits can look like proof that traffic has returned. The August EIA Global Energy Security Data explains why that inference is unsafe.
EIA says much of its chokepoint analysis begins with Automatic Identification System signals. Those signals can be incomplete when they are manipulated or turned off for sanctions evasion or for security in a hazardous area. To account for obscured movements, EIA supplements tracking data with origin and destination ports and other route information. It estimates waypoint dates for cargoes that were not otherwise identified as passing a chokepoint.
The agency then gives a specific warning. Since the end of February 2026, AIS data for ships transiting Hormuz have become especially unreliable. EIA says its 2026 tanker estimates are being revised frequently as better information becomes available.
The August tables remain valuable. Average Hormuz oil flows fell from 21.6 million barrels per day in the fourth quarter of 2025 to 4.9 million in the second quarter of 2026. LNG flows fell from 10.5 billion cubic feet per day to 0.8 billion over the same period. The estimates show the scale of the disruption, but they are not a live count of every vessel and do not prove the status of a particular cargo.
The third gate therefore needs a corrected flow record. It can use the WTO and AXSMarine tracker for current direction and the EIA series for a methodologically documented benchmark. The tracker captures AIS-on voyage segments, so its volumes may understate actual flows. The company record should preserve the observation date, source, commodity, direction, denominator, revision note, and known coverage gap. Port departure and destination evidence should supplement AIS where a ship went dark or its signal became unreliable.
This gate is not cleared by finding some movement. It is cleared when the observed flow is sufficient for the planning decision and the team can explain what the data may be missing. A buyer deciding whether to cancel a single emergency shipment needs different evidence from a chief financial officer restoring a quarterly freight assumption.
The company decision turns on named arrivals
Aggregate flow can improve while a named supply lane still fails. A tanker may cross the strait but carry a different commodity, serve a different destination, or wait offshore. A vessel may discharge while the buyer's container remains rolled. Cargo can clear the maritime chokepoint and then lose time at transshipment, discharge, customs, or inland handoff.
The fourth gate follows the purchase order rather than the vessel count. Keep the purchase order, bill of lading, vessel, actual transit evidence, discharge, customs event, inland handoff, receipt, and ETA variance together. The prior Traverse Analysis on Hormuz trade data explains the detailed arrival file.
Commercial use becomes measurable for the company when the named lane performs within a variance the business can absorb. One successful arrival can support one supply decision. It does not establish normal performance for every supplier, carrier, or commodity.
The same discipline works in reverse. A missed arrival does not prove that the strait is closed. It shows that the named commercial chain failed somewhere. The company should identify whether the cause was route access, security acceptance, vessel capacity, port congestion, data error, contract performance, or inland logistics before changing its broader posture.
The four-gate commercial-use matrix
The matrix below separates the status owner from the company decision. It is designed for imports that depend on a Gulf loading port or a transit through the Strait of Hormuz.
Gate
Question
Minimum evidence
A green result means
A red result requires
Route
Is a navigable route available for this voyage profile?
Current JMIC or equivalent route advisory, corridor, mine restrictions, direction, flag and vessel fit
A route can be planned
Keep the diversion or no-sail assumption
Acceptance
Will the carrier and insurer accept the named voyage on workable terms?
The movement is commercially offered and risk accepted
Preserve alternate carrier, route, or inventory cover
Flow
Does the observable record support the assumed capacity and timing?
WTO tracker, EIA benchmark, port evidence, observation date, revision and AIS limitations
The plan has a defensible market-flow basis
Treat apparent transits as provisional and shorten review intervals
Arrival
Are named cargoes reaching destination within the tolerance used by the business?
Purchase order, bill of lading, transit event, discharge, customs, inland handoff, receipt and ETA variance
The lane works for the tested cargo and decision
Keep contingency supply and investigate the failed segment
The gates are sequential for a full restart decision. A company may still authorize a single voyage when one market-wide measure remains uncertain, but the exception should be explicit. The approving officer should state which gate is unresolved, what evidence substitutes for it, how much exposure is accepted, and when the decision expires.
That exception record prevents a tactical shipment from silently resetting the planning baseline. It also lets finance distinguish a one-time risk decision from a restored lane.
Freight and inventory decisions need different thresholds
There is no universal moment when Hormuz becomes commercially usable. The threshold depends on the decision and the cost of being wrong.
A purchaser deciding whether to place an order may accept a conditional booking and a wider arrival window. A plant scheduler may need two or three successful arrivals before removing a production buffer. Treasury may keep a freight and working-capital reserve until insurance premiums, detention risk, and transit variance stabilize. A supplier manager may retain an alternate source after maritime flow improves because the original vendor has not restored allocation or loading capacity.
Each function applies a different control to a different exposure. Trouble starts when one favorable indicator is shared across the company as if it clears every threshold.
The restart memo should name the decision. It should say whether the team is authorizing one shipment, returning a supplier to normal lead time, reducing safety stock, releasing alternate capacity, or changing a quarterly cost forecast. It should then identify the evidence period and tolerance that match that action.
For a one-shipment decision, a current safe-route confirmation, accepted booking, voyage-specific insurance, and enough tracking to manage the movement may be sufficient. For a planning reset, the business needs repeat performance. A useful test is whether multiple named cargoes across the lane have completed the route without extraordinary intervention and within the variance used in inventory calculations.
The status must expire
Every green light in this file needs an expiry. Security guidance can change as mine clearance progresses or threats return. Carriers revise schedules, and AIS estimates can be corrected. A status copied into a planning system without a review date becomes stale evidence presented as a current fact.
Route and threat records should be checked against the issuing body before each high-risk voyage and whenever a material incident occurs. Carrier acceptance should be refreshed for the actual booking. Flow data should carry its observation window and revision date. Arrival performance should roll forward with each named cargo.
The company should also keep the prior state. When a source changes, the file needs the earlier status, the new status, the time the business learned of it, and the decisions made in between. That chronology matters for supplier disputes, insurance claims, forecast review, and management oversight.
Do not turn uncertainty into a permanent red status. The purpose of the file is to make a controlled restart possible. When all four records align for the chosen decision, the company can reduce contingencies with a stated basis. If they diverge again, the same file shows which control must return.
Public flow and company proof stay separate
The WTO Hormuz portal and its tracker show the broader system response. Traverse has already explained why aggregate trade data cannot prove company-level resilience. This four-gate control solves a different problem by assigning route, acceptance, measurement, and arrival status to separate records.
A late cargo is evidence about a named commercial chain, not a global closure. A rising vessel count is evidence about aggregate movement, not a reason to cancel a company's contingency plan. Keep each claim inside the record that can prove it.
The operating question belongs to the import team
For an import team, the operating question is whether the route, risk acceptance, corrected flow, and arrival record support the next commercial decision.
JMIC can report neutral transit as permitted while maintaining a severe threat level and recording reduced traffic. MARAD can maintain a high-risk posture. EIA can publish a careful flow estimate while warning that the underlying signals are unusually unreliable. A buyer can receive one cargo while the wider lane remains unstable. All four statements can be true at once.
The restart control therefore needs four gates. Keep contingency supply in place until all gates required for the decision have been cleared. Restore normal lead times only after repeat named arrivals support the assumption. Reopen the file whenever a route advisory, threat record, carrier term, flow estimate, or shipment result changes.
Transit permission is the beginning of the test. It is not the commercial answer.
Free account
Keep reading with a free account.
Today's analysis is open to everyone. A free account opens the full archive and full tool output. No card required.