INTELLIGENCE.NAVYA portal by Maritime IntelligenceBack to In Focus
THEATRE DOSSIER / HISTORICAL VERSION 2

Strait of Hormuz / Arabian Gulf

Operating indicators, linked cases and evidence-led collection priorities.

Version recorded 08 Oct 2026 · 18:55 UTC. Related source records show their available archive versions.

Links use the site’s current access permissions.
STATUS ELEVATEDTREND SHIFTINGCONFIDENCE MODERATE

Individual evidence review 08 Oct 2026 · 18:44 UTC · Collection 16 Oct 2026 · 20:29 UTC

HISTORICAL ASSESSMENT

Reporting latency has left an unresolved interval between the reported strike and a usable casualty-status picture. Before this notice, the imported picture did not include this specific reported event on 6 October. The working picture remains limited by the source account: context reporting is not independent incident confirmation. Source checks can retrieve later publications without updating this analysis. Any wider conclusion about route availability, cargo flows, attribution or response capacity requires additional dated evidence. The next assessment should test the watch indicators below against the previous evidence basis, preserve contradictory accounts and record what changed. Traffic reception, local casualty condition and corridor access are separate questions; a change in one must not be assumed to establish a change in the others.

Dated individual analysis; the event account is not independently confirmed. Context sources are not corroborating witnesses.

Key judgments

  1. Reporting latency has left an unresolved interval between the reported strike and a usable casualty-status picture.
  2. A vessel-level event does not establish corridor-wide disruption without access, operator or traffic evidence.
  3. A fresh source check does not refresh a dated assessment or resolve an unknown vessel condition.
Geographic context around the source-reported positionAPPROXIMATE AREASOURCE MAP / GEOGRAPHIC CONTEXT

Approximate source-map area: 26.5°, 56.5°. Approximate source-map area, rounded to 0.5 degrees. Source map coordinates vary between retrievals; no precise incident fix is established. Static basemap; not a satellite image of the incident.

Previous baseline

The intelligence significance lies in the interval between the attack and confirmation of a stable vessel. The Strait of Hormuz connects Gulf energy terminals with the Gulf of Oman. The working picture remains limited by the source account: context reporting is not independent incident confirmation. Source checks can retrieve later publications without updating this analysis. Any wider conclusion about route availability, cargo flows, attribution or response capacity requires additional dated evidence. The next assessment should test the watch indicators below against the previous evidence basis, preserve contradictory accounts and record what changed. Traffic reception, local casualty condition and corridor access are separate questions; a change in one must not be assumed to establish a change in the others.

What changed

Late-reported Hormuz tanker strike leaves a gap in casualty and environmental status

Maritime operating picture

Source-reported encounters, local vessel condition and regional access are separate layers. 12 source accounts with open follow-up questions fall within the last seven days. They may concern the same event; missing follow-up does not establish that an incident remains active.

Open Hormuz baseline indicatorsOpen this theatre on the map

Critical nodes

Strait of Hormuz
Gulf access and energy transit depend on this passage.

Gulf energy terminals
Loading continuity must be checked separately from transit counts.

Musandam approaches
Connect the strait with the Gulf of Oman; reported positions can be approximate.

Relevant actors

Maritime reporting centres
Publish vessel accounts and navigation guidance; a notice is not an independent observation.

Coastal authorities
Confirm passage rules, casualty status and response coordination.

Ship operators and insurers
Operator decisions and dated cover conditions can test wider corridor effects.

Environmental exposure

A casualty can create a release pathway. No spill extent, coastal exposure or drift is inferred without a verified discharge and time-matched observations.

Sanctions & insurance

No verified current premium, P&I change or sanctions-impact metric is attached to this dossier. Source reporting and designated-vessel identity need separate verification.

Indicators & watch next

  • Authoritative vessel-status updates and confirmed release or damage.
  • Dated passage restrictions and named-operator route changes.
  • Sustained AIS crossing changes over complete, comparable UTC windows.

Trigger: a dated authority update or a verified operational change that alters the baseline. Unobserved indicators have no assigned direction or warning score.

Intelligence gaps

  • Vessel identity, damage extent and current condition are not supplied.
  • No verified environmental release, satellite observation or drift assessment is attached.
  • No independent confirmation or attacker attribution is established.
  • Coverage of pollution, insurance and AIS-independent physical traffic is incomplete.

Material-change timeline

08 Oct 2026 · 18:44 UTCLate-reported Hormuz tanker strike leaves a gap in casualty and environmental status

Reporting latency has left an unresolved interval between the reported strike and a usable casualty-status picture.

06 Oct 2026 · time not suppliedHormuz tanker attack puts casualty control and regional response on the same clock

The intelligence significance lies in the interval between the attack and confirmation of a stable vessel.

How this dossier is updated
  1. Public readers use the existing hourly collection cycle and five-minute refresh while the main watch is open. Unavailable readers retain dated records.
  2. Records are linked by named area, explicit theatre tag or reported position. Approximate positions remain labelled. Shared geography does not duplicate the article or establish a shared incident.
  3. Reviewed case judgments feed the dossier. Event confidence, editorial priority and a theatre-wide threat rating remain separate.
  4. Changed evidence, corrections and analytical states enter the version history. A repeated source check does not become a new analytical review.
  5. Open gaps guide the research queue. New substantive assessments follow the existing research stages and human publication approval.
Assessment versions & corrections

Changed analytical states are preserved from activation, up to the latest 60 versions. A collection check does not create a revision when the assessment is unchanged. Source-publication versions remain in the existing archive.

v16 · 16 Oct 2026 · 19:55 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv15 · 16 Oct 2026 · 19:08 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv14 · 16 Oct 2026 · 17:05 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv13 · 16 Oct 2026 · 10:07 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv12 · 16 Oct 2026 · 06:16 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv11 · 15 Oct 2026 · 19:58 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv10 · 15 Oct 2026 · 17:39 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv9 · 15 Oct 2026 · 12:15 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv8 · 15 Oct 2026 · 11:13 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv7 · 15 Oct 2026 · 10:37 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv6 · 14 Oct 2026 · 22:30 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv5 · 12 Oct 2026 · 20:18 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv4 · 09 Oct 2026 · 17:56 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv3 · 09 Oct 2026 · 09:03 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv2 · 08 Oct 2026 · 18:55 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv1 · 08 Oct 2026 · 18:55 UTC · INITIAL ASSESSMENT · archive begins here
Related source records · 68gCaptain · 16 Oct 2026 · 18:53 UTCFog of War Deepens in Hormuz as UKMTO Says Most Ship Attacks Go UnreportedgCaptain · 16 Oct 2026 · 15:50 UTCIEA Moves to Accelerate Oil Reserve Releases as Hormuz Crisis Drags OngCaptain · 16 Oct 2026 · 12:07 UTCSingapore fuel deliveries qualify the HSFO squeeze: procurement risk is grade- and port-specificSplash 247 · 16 Oct 2026 · 07:45 UTCSplash Wrap: A missile from RiyadhBBC · 16 Oct 2026 · 05:00 UTCShip attack reports near Hormuz reach record high as oil exports slowgCaptain · 15 Oct 2026 · 18:33 UTCU.S. Claims Control of Hormuz as Ship Attacks Hit New HighThe Maritime Executive · 14 Oct 2026 · 22:51 UTCU.S. Forces Destroy a Dhow Suspected of Conducting Surveillance for IranNYT · 14 Oct 2026 · 18:20 UTCAttacks on Ships in Strait of Hormuz Escalate SharplyBBC · 14 Oct 2026 · 15:34 UTCContainer ship hit by projectile sinks in Strait of Hormuz, Singapore saysThe Maritime Executive · 14 Oct 2026 · 14:47 UTCIran Claims Containership Hit Mine and Sank in Strait of HormuzMSCIO · 2026-10-14 11:04 · source timezone unspecifiedAttack notification puts Hormuz & Arabian Gulf on the maritime watchMSCIO · 2026-10-14 11:01 · source timezone unspecifiedContainer ship struck by unidentified projectile in Hormuz & Arabian Gulf

Assessment source references

  1. MSCIOAttributed source · 2026-10-08 14:57 · source timezone unspecified
  2. EIA · World Oil Transit Chokepoints · March 2026 review; 1H25 baselineContext reference · 03 Mar 2026 · time not supplied
  3. IEA · Middle East Maritime Chokepoints Shipping Monitor · 16 September 2026 editionContext reference · 16 Sept 2026 · time not supplied
  4. MSCIOAttributed source · 2026-10-05 19:57 · source timezone unspecified
  5. MARAD · 2026-011Context reference · 09 Sept 2026 · time not supplied
  6. EIA · World Oil Transit ChokepointsContext reference · 03 Mar 2026 · time not supplied
  7. IMO · Preparing for marine pollution incidentsContext reference
  8. Reuters · Oman tanker pollution comparatorContext reference · 12 Aug 2026 · time not supplied
  9. JMIC · Public maritime information productsContext reference
  10. Global Fishing Watch · AIS data caveatsContext reference
  11. UKMTO · UKMTO 156-26Context reference · 05 Oct 2026 · time not supplied
  12. Reuters · Reuters reports a higher weekly concentration of tanker attacks in HormuzContext reference · 07 Oct 2026 · time not supplied
  13. BBC · Three reasons Middle East oil supply is nearly back to pre-Iran war levelsContext reference · 02 Oct 2026 · 15:29 UTC
  14. NYT · Oil Flows Are Up, but Iran Is Still Menacing the Strait of HormuzContext reference · 02 Oct 2026 · time not supplied

AI-assisted synthesis of dated case evidence. No separate human analyst sign-off or theatre-wide risk rating. Node and actor profiles explain strategic relevance; they do not disclose live asset status.