INTELLIGENCE.NAVYA portal by Maritime IntelligenceBack to In FocusPrivate intelligence environments · In preparation
THEATRE DOSSIER / HISTORICAL VERSION 30

Strait of Hormuz / Arabian Gulf

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

Version recorded 20 Oct 2026 · 00:01 UTC. Related source records show their available archive versions.

Links use the site’s current access permissions.
REPORTED EXPOSURERECENT EVIDENCE REVIEWTrend · NOT ESTABLISHED
COLLECTION STALESources checked 19 Oct 2026 · 23:00 UTCEvidence review 19 Oct 2026 · 10:13 UTCLatest source evidence 19 Oct 2026 · 20:17 UTC

Recent source accounts retain open follow-up questions. They are not a confirmed count of unique, currently active incidents.

Reports to follow up · 7D
5
Accounts, not unique incidents
Reviewed products · 7D
3
Case-level analytical updates
Evidence gaps
1 / 4
Operating dimensions to verify
HISTORICAL ASSESSMENT

The reported damage to a tug outside Hormuz exposes an additional vulnerability in the maritime-support system. The evidence does not yet establish a campaign against auxiliary vessels, service disruption, pollution or attribution. Exact event-time agreement makes MSCIO ALERT 134/26 and UKMTO 159/26 a probable same-event pair, not independent confirmations. JMIC's 11 October follow-up adds a reported loss of power and tug-assisted passage to Ras Al Khaimah to the likely linked case; it does not establish arrival or the ship's present condition. [mscio, ukmto159, jmic104] The hazardous-cargo confirmation raises the consequence profile of GFS PRIDE: response now requires cargo identification, containment checks, recovery prioritisation and environmental monitoring alongside navigation and salvage. Hazardous cargo present does not establish a hazardous release. HIGH confidence concerns the documented casualty and attributed warning; specific substances and exposure remain unresolved. GFS PRIDE · 16 OCT: hazardous cargo confirmed in the attributed MTCIT warning; no hazardous release confirmed. Cargo identification, containment, recovery and coastal monitoring are the priority requirements.

Confidence belongs to individual claims and cases below. No separately reviewed theatre-wide threat rating or comparable trend baseline is attached; event confidence is not inherited by the whole region.

No comparable, independently reviewed theatre baseline establishes improving or deteriorating conditions. A new source report or review date alone does not demonstrate a trend.

EVIDENCE → IMPLICATION → NEXT DECISION

Operating indicators

Evidence states, not live sensor readings or a regional risk score. Each indicator states what would change the judgment.

Security & vessel condition

REPORTED

Source accounts describe recent vessel-level exposure. Match identities and event times before treating notices as separate incidents.

Evidence · UKMTO 177-26 · MSCIO 150/2618 Oct 2026 · time not suppliedEvidence · ALERT 148/2616 Oct 2026 · 19:22 UTCEvidence · ALERT 147/2616 Oct 2026 · 09:00 UTC
Collection requirement & decision trigger

Collect · A dated authority or operator update matching vessel identity and event time; reconcile related notices and follow-up.

Revise when · Confirmed damage, assistance, release or a formal navigation restriction changes the vessel-level assessment.

Navigation & recovery

REVIEWED ANALYSIS

Case analysis reviewed 2026-10-17 · Analytical inference · The practical decision is whether this historical casualty has an evidenced recovery outcome. Ask for arrival, survey and clearance records before downgrading follow-up; neither a destination nor elapsed time proves completion. Do not infer wider traffic effects from this file. [jmic104, mscio]

Evidence · ALERT 134/2606 Oct 2026 · 17:09 UTC
Collection requirement & decision trigger

Collect · Name, IMO number, exact casualty position and final damage remain unresolved. [mscio, ukmto159, jmic104] No dated arrival, repair completion or current containment finding was retrieved. [jmic104]

Revise when · Obtain the explicit issuer-to-issuer and IMO-number crosswalk. A conflicting identifier would break the proposed linkage. [mscio, ukmto159, imo-candidate]

Trade & feeder connectivity

GAP

Loss of a feeder hull creates direct schedule, salvage and cargo exposure. The record does not quantify network-wide capacity loss, port closure or regional service disruption.

Evidence · IN-HOR-IA-2026-1014-0113 Oct 2026 · time not supplied
Collection requirement & decision trigger

Collect · Dated named-operator schedule changes, port notices, missed calls or comparable traffic windows; verify insurance conditions separately.

Revise when · A confirmed service suspension, port restriction or sustained comparable routing change would support a wider connectivity judgment.

Environment & observation

DOCUMENTED

16 OCT · MTCIT confirms hazardous materials among drifting containers, as reported by Times of Oman. No hazardous release, significant bunker discharge or coastal contamination is confirmed. Obtain the original warning, manifest, package condition and environmental sampling; satellite linkage remains unverified.

Evidence · IN-HOR-IA-2026-1014-0113 Oct 2026 · time not supplied
Collection requirement & decision trigger

Collect · A dated authority statement, cargo information and geolocated repeat observations with acquisition time, sensor and metocean context.

Revise when · Verified discharge or clearance, repeat discriminated observations or confirmed coastal impact would change response priorities.

LINKED INCIDENTS / CASE FOLLOW-UP

Cases in this theatre

SOURCE REPORT · FOLLOW-UP OPENEXPLICIT TAG
Tug Strike Off Khor Fakkan Extends Maritime Threat Exposure to Support Vessels Outside HormuzEvent / record date · 18 Oct 2026 · time not supplied · Case confidence MODERATE

The reported damage to a tug outside Hormuz exposes an additional vulnerability in the maritime-support system. The evidence does not yet establish a campaign against auxiliary vessels, service disruption, pollution or attribution.

Explicit theatre tag in the publication record.
SOURCE REPORT · FOLLOW-UP OPENEXPLICIT TAG
Attack notification puts Hormuz & Arabian Gulf on the maritime watchEvent / record date · 16 Oct 2026 · 19:22 UTC · Case confidence LOW

ALERT 148/26 MSCIO has received information regarding an incident at approximately 19:22 UTC on 16 October 2026, 78NM northeast of Al Jubayl, Saudi Arabia, in the Arabian Gulf.

Explicit theatre tag in the publication record.
SOURCE REPORT · FOLLOW-UP OPENEXPLICIT TAG
Tanker struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 16 Oct 2026 · 09:00 UTC · Case confidence LOW

ALERT 147/26 MSCIO has received a time-late report regarding an incident at approximately 09:00 UTC on 16 October 2026, 68NM northeast of Al Jubayl, Saudi Arabia, in the Arabian Gulf.

Explicit theatre tag in the publication record.
SOURCE REPORT · FOLLOW-UP OPENEXPLICIT TAG
Attack notification puts Hormuz & Arabian Gulf on the maritime watchEvent / record date · 13 Oct 2026 · 17:00 UTC · Case confidence LOW

ALERT 146/26 MSCIO has received a time-late report of an attack at approximately 17:00 UTC on 13 October 2026 in the Strait of Hormuz.

Explicit theatre tag in the publication record.
SOURCE REPORT · FOLLOW-UP OPENEXPLICIT TAG
Container ship struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 13 Oct 2026 · 16:40 UTC · Case confidence LOW

ALERT 145/26 MSCIO has received a time-late report regarding an incident at approximately 16:40 UTC on 13 October 2026 in the Strait of Hormuz.

Explicit theatre tag in the publication record.
DATED CASE · OUTCOME TO RECHECKEXPLICIT TAG
Tanker struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 13 Oct 2026 · time not supplied · Case confidence LOW

ALERT 144/26 MSCIO has received information regarding an incident on 13 October 2026 in the Strait of Hormuz.

Explicit theatre tag in the publication record.
DATED CASE · OUTCOME TO RECHECKEXPLICIT TAG
Container ship struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 13 Oct 2026 · time not supplied · Case confidence LOW

ALERT 143/26 MSCIO has received information regarding an incident on 13 October 2026 in the Strait of Hormuz.

Explicit theatre tag in the publication record.
HAZARDOUS CARGO · ACTIVE RESPONSEEXPLICIT TAG
Hazardous containers adrift off Musandam turn GFS PRIDE from a shipping casualty into a multi-hazard maritime response problemEvent / record date · 13 Oct 2026 · time not supplied · Case confidence HIGH

The hazardous-cargo confirmation raises the consequence profile of GFS PRIDE: response now requires cargo identification, containment checks, recovery prioritisation and environmental monitoring alongside navigation and salvage. Hazardous cargo present does not establish a hazardous release. HIGH confidence concerns the documented casualty and attributed warning; specific substances and exposure remain unresolved.

Explicit theatre tag in the publication record.
Shared approaches · Gulf of Oman / Musandam ↗

Key judgments

  1. The reported damage to a tug outside Hormuz exposes an additional vulnerability in the maritime-support system. The evidence does not yet establish a campaign against auxiliary vessels, service disruption, pollution or attribution.
  2. Exact event-time agreement makes MSCIO ALERT 134/26 and UKMTO 159/26 a probable same-event pair, not independent confirmations. JMIC's 11 October follow-up adds a reported loss of power and tug-assisted passage to Ras Al Khaimah to the likely linked case; it does not establish arrival or the ship's present condition. [mscio, ukmto159, jmic104]
  3. The hazardous-cargo confirmation raises the consequence profile of GFS PRIDE: response now requires cargo identification, containment checks, recovery prioritisation and environmental monitoring alongside navigation and salvage. Hazardous cargo present does not establish a hazardous release. HIGH confidence concerns the documented casualty and attributed warning; specific substances and exposure remain unresolved.
  4. GFS PRIDE · 16 OCT: hazardous cargo confirmed in the attributed MTCIT warning; no hazardous release confirmed. Cargo identification, containment, recovery and coastal monitoring are the priority requirements.
Khor Fakkan container port on 7 April 2017: historical contextual photograph with commercial shipping and assisting tugs; not an image of the 18 October 2026 attack.HISTORICAL CONTEXT IMAGE

Khor Fakkan container port on 7 April 2017: historical contextual photograph with commercial shipping and assisting tugs; not an image of the 18 October 2026 attack.

Original report · Intelligence.NavyIwona Rege · Wikimedia Commons · CC BY-SA 4.0 · 7 April 2017. Original photograph; Wikimedia 1280 px rendition, no editorial alteration.Reuse terms

Previous baseline

The reported damage to a tug outside Hormuz exposes an additional vulnerability in the maritime-support system. The evidence does not yet establish a campaign against auxiliary vessels, service disruption, pollution or attribution. Exact event-time agreement makes MSCIO ALERT 134/26 and UKMTO 159/26 a probable same-event pair, not independent confirmations. JMIC's 11 October follow-up adds a reported loss of power and tug-assisted passage to Ras Al Khaimah to the likely linked case; it does not establish arrival or the ship's present condition. [mscio, ukmto159, jmic104] The hazardous-cargo confirmation raises the consequence profile of GFS PRIDE: response now requires cargo identification, containment checks, recovery prioritisation and environmental monitoring alongside navigation and salvage. Hazardous cargo present does not establish a hazardous release. HIGH confidence concerns the documented casualty and attributed warning; specific substances and exposure remain unresolved. GFS PRIDE · 16 OCT: hazardous cargo confirmed in the attributed MTCIT warning; no hazardous release confirmed. Cargo identification, containment, recovery and coastal monitoring are the priority requirements.

What changed

Tug Strike Off Khor Fakkan Extends Maritime Threat Exposure to Support Vessels Outside Hormuz

Maritime operating picture

Source-reported encounters, local vessel condition and regional access are separate layers. 5 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

16 OCT · MTCIT confirms hazardous materials among drifting containers, as reported by Times of Oman. No hazardous release, significant bunker discharge or coastal contamination is confirmed. Obtain the original warning, manifest, package condition and environmental sampling; satellite linkage remains unverified.

Sanctions & insurance

No verified current premium, P&I change or sanctions-impact metric is attached. Vessel designation, insurance terms and operational effects require separate dated evidence.

Indicators & watch next

  • Publication of the tug's name or IMO number.
  • Confirmation of flag and operator.
  • Identification of vessel class and actual assignment.
  • Independent confirmation of damage and subsequent condition.
  • 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

  • 1. Vessel name and IMO.
  • 2. Flag and registered owner.
  • 3. Commercial operator.
  • 4. Tug classification and operational assignment.
  • 5. Whether a tow was attached.
  • 6. Exact incident time.
  • Theatre-wide traffic, insurance and environmental coverage are incomplete. No direct HUMINT has been collected for this dossier.

Material-change timeline

19 Oct 2026 · 10:13 UTCTug Strike Off Khor Fakkan Extends Maritime Threat Exposure to Support Vessels Outside Hormuz

The reported damage to a tug outside Hormuz exposes an additional vulnerability in the maritime-support system. The evidence does not yet establish a campaign against auxiliary vessels, service disruption, pollution or attribution.

17 Oct 2026 · 22:29 UTC6 October Hormuz tanker report: stronger notice linkage, assisted recovery still unnamed

Exact event-time agreement makes MSCIO ALERT 134/26 and UKMTO 159/26 a probable same-event pair, not independent confirmations. JMIC's 11 October follow-up adds a reported loss of power and tug-assisted passage to Ras Al Khaimah to the likely linked case; it does not establish arrival or the ship's present condition. [mscio, ukmto159, jmic104]

16 Oct 2026 · 19:00 UTCHazardous containers adrift off Musandam turn GFS PRIDE from a shipping casualty into a multi-hazard maritime response problem

UPDATED / v3 · 16 OCT 2026 · The hazardous-cargo confirmation raises the consequence profile of GFS PRIDE: response now requires cargo identification, containment checks, recovery prioritisation and environmental monitoring alongside navigation and salvage. Hazardous cargo present does not establish a hazardous release. HIGH confidence concerns the documented casualty and attributed warning; specific substances and exposure remain unresolved.

12 Oct 2026 · 20:18 UTCALERT 136/26 adds a later outbound-tanker strike, but not a vessel identity or independent confirmation

MSCIO ALERT 136/26 is best treated as a new, vessel-anonymous incident at 19:20 UTC on 10 October, not as an update to the 9 October Al Jazeera/Gem No.2 case. UKMTO WARNING 162-26 reproduces the same time, direction, impact side, fire and crew status from the master, so the two notices describe one reporting chain rather than two independently confirmed attacks. The safe-crew report reduces the immediate casualty concern, but the unresolved fire, damage, propulsion and pollution status leave the tanker’s operational outcome open.

12 Oct 2026 · 20:18 UTCALERT 137/26 extends outbound-tanker exposure into 11 October, but remains vessel-anonymous and single-chain reported

MSCIO ALERT 137/26 is best treated provisionally as a later incident report at 12:00 UTC on 11 October, distinct from ALERT 136/26 at 19:20 UTC on 10 October. UKMTO WARNING 164-26 reproduces the later time, outbound direction, port-side impact, damage, crew-safe status and no reported environmental impact from a company security officer, so MSCIO and UKMTO represent one reporting chain rather than independent confirmation. The record extends the observed hazard window for outbound tankers, but it does not identify the vessel, establish attribution, confirm its ability to proceed or demonstrate closure of the Strait.

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.

Unavailable readers represented here: UKMTO, MARAD · U.S. DOT. Retained records may predate the latest check.

Reference-only sources represented here: Reuters · editorial selection. These are not connected live readers.

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.

v35 · 20 Oct 2026 · 14:02 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv34 · 20 Oct 2026 · 09:07 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv33 · 20 Oct 2026 · 07:05 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv32 · 20 Oct 2026 · 06:03 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv31 · 20 Oct 2026 · 02:04 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv30 · 20 Oct 2026 · 00:01 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv29 · 19 Oct 2026 · 20:04 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv28 · 19 Oct 2026 · 18:05 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv27 · 19 Oct 2026 · 10:21 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv26 · 19 Oct 2026 · 04:56 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv25 · 19 Oct 2026 · 00:58 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv24 · 18 Oct 2026 · 12:39 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv23 · 18 Oct 2026 · 11:57 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv22 · 18 Oct 2026 · 00:03 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv21 · 17 Oct 2026 · 23:57 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv20 · 17 Oct 2026 · 22:31 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv19 · 17 Oct 2026 · 20:05 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv18 · 17 Oct 2026 · 15:56 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv17 · 17 Oct 2026 · 08:18 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv16 · 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 · 63Splash 247 · 20 Oct 2026 · 08:50 UTCUS moves to legitimise shadow tanker fleetThe Maritime Executive · 19 Oct 2026 · 20:17 UTCTug Attacked Near Strait of HormuzgCaptain · 19 Oct 2026 · 10:50 UTCQatar LNG Cargo Makes Rare Red Sea Journey to Get Gas to EuropeIntelligence.Navy · 19 Oct 2026 · 10:13 UTCTug Strike Off Khor Fakkan Extends Maritime Threat Exposure to Support Vessels Outside HormuzMSCIO · 2026-10-18 11:40 · source timezone unspecifiedVessel struck by unidentified projectile in Hormuz & Arabian GulfMSCIO · 2026-10-17 08:17 · source timezone unspecifiedAttack notification puts Hormuz & Arabian Gulf on the maritime watchMSCIO · 2026-10-17 08:15 · source timezone unspecifiedTanker struck by unidentified projectile in Hormuz & Arabian GulfBBC · 16 Oct 2026 · 05:00 UTCShip attack reports near Hormuz reach record high as oil exports slowNYT · 14 Oct 2026 · 18:20 UTCAttacks on Ships in Strait of Hormuz Escalate SharplyMSCIO · 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 GulfMSCIO · 2026-10-14 06:52 · source timezone unspecifiedTanker struck by unidentified projectile in Hormuz & Arabian Gulf

Assessment source references

  1. UKMTO · UKMTO 156-26Context reference · 05 Oct 2026 · time not supplied
  2. MSCIO · Alert 150/26Attributed source · 18 Oct 2026 · time not supplied
  3. Reuters via Arab News · 18 October 2026Context reference · 18 Oct 2026 · time not supplied
  4. Sharjah Ports Authority · reference portalContext reference
  5. Gulftainer · Khorfakkan Commercial TerminalContext reference
  6. Fujairah Ports Authority · oil and bunkeringContext reference
  7. Reuters · regional strategy reporting, 14 October 2026Context reference · 14 Oct 2026 · time not supplied
  8. Reuters via Internazionale · accessible reproductionContext reference · 14 Oct 2026 · time not supplied
  9. MPA Singapore · two Singapore-registered vessels struckAttributed source
  10. HYDROPAC 2978/26 · initial fire/adrift warning (cancelled)Attributed source
  11. HYDROPAC 2981/26 · GFS PRIDE sunkAttributed source
  12. HYDROPAC 2982/26 · containers adriftAttributed source
  13. Reuters · GFS PRIDE and separate Cape Dao casualtyContext reference
  14. AD Ports Group · ownership and feeder-network contextAttributed source
  15. IMO · Middle East highlighted incidents · board as at 14 October 2026Context reference
  16. Reuters Connect · corrected Copernicus Sentinel-2 handout captionContext reference · 14 Oct 2026 · time not supplied
  17. MTCIT warning, attributed by Times of Oman · 16 October 2026Context reference · 16 Oct 2026 · time not supplied
  18. Oman Maritime Law · Royal Decree 19/2023, Article 185Attributed source · 30 Mar 2023 · time not supplied
  19. Ministry of Health capability, reported by Times of Oman · 15 October 2026Context reference · 15 Oct 2026 · time not supplied
  20. MSCIO ALERT 137/26 — Attack reported in Hormuz & Arabian GulfAttributed source
  21. MSCIO ALERT 136/26 — Attack reported in Hormuz & Arabian GulfAttributed source
  22. MARAD · 2026-011Context reference · 09 Sept 2026 · time not supplied
  23. Intelligence.Navy Hormuz AIS traffic snapshotContext reference
  24. MSCIO ALERT 135/26 — 9 October incident west of Al JazeeraContext reference
  25. MSCIO · ALERT 134/26 · retained notice and dated prior assessmentAttributed source
  26. UKMTO WARNING 159-26 · 6 October 2026, 1709 UTCContext reference
  27. JMIC · Update 104 to Advisory Note · 11 October 2026 · ICOD 15:00 UTCContext reference
  28. MSCIOAttributed source · 2026-10-05 19:57 · source timezone unspecified
  29. EIA · World Oil Transit ChokepointsContext reference · 03 Mar 2026 · time not supplied
  30. IMO · Preparing for marine pollution incidentsContext reference
  31. Reuters · Oman tanker pollution comparatorContext reference · 12 Aug 2026 · time not supplied
  32. JMIC · Public maritime information productsContext reference
  33. Global Fishing Watch · AIS data caveatsContext reference
  34. Reuters · Reuters reports a higher weekly concentration of tanker attacks in HormuzContext reference · 07 Oct 2026 · time not supplied
  35. BBC · Three reasons Middle East oil supply is nearly back to pre-Iran war levelsContext reference · 02 Oct 2026 · 15:29 UTC
  36. 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.

INTELLIGENCE.NAVYA portal by Maritime Intelligence

Public sources. Clear provenance. Informed human judgment.

Naval intelligence · Satellite intelligence · Publication archive · Follow via RSS
Maritime Intelligence · MaritimeIntelligence.orgLinked to Geopolitics FoundationAbout the portal© 2026 INTELLIGENCE.NAVY
Strait of Hormuz / Arabian Gulf theatre dossier | Intelligence.Navy