Water
Seahound / SeaLens
Maritime chokepoints, ports, routes, commodities, advisories, and operational state.
Strait of Hormuz State Report
A due-diligence style corridor report that tells the user whether the operating state is normal, abnormal, recovering, or deteriorating.
Review recommended before relying on AIS-only coverage.
Overall Corridor State
Abnormal
Activity state departed sharply from the local baseline.
Disruption Score
77.7
Extreme state displacement on Apr 11.
Recovery Status
Partial
Apr 23 improved but remained outside baseline.
AIS Dependence
Low
Assessment does not rely on AIS as ground truth.
Report Summary
The front page should read like an operational record, not a methods section.
Seahound flags the Strait of Hormuz as an abnormal corridor state during the April 2026 observation window, with Apr 11 as the peak anomaly and Apr 23 showing partial recovery.
The result matters because AIS-only systems can lose coverage exactly when corridor visibility matters most. This report is designed to show the state of the corridor, the confidence behind that state, and the operational implications.
What happened?
Corridor activity departed from baseline.
Why care?
Hormuz is a high-consequence energy route.
What next?
Maintain watch and compare related Gulf corridors.
Key Findings
Carfax-style flags: clear, caution, flagged.
The corridor entered an abnormal maritime state during the April observation window.
The Apr 11 observation was the most extreme state in the available sequence.
AIS can underrepresent both self-protective and evasive behavior in contested waters.
The abnormal state remains visible after separating weather-like effects from activity-like structure.
The Apr 23 state fell well below the Apr 11 extreme, suggesting the event did not persist at peak intensity.
Exposure Snapshot
The report should connect state changes to who might care.
Energy transit risk
Hormuz is a critical crude oil and LNG corridor.
Insurance and routing
Abnormal corridor states can affect underwriting, war-risk review, and route planning.
Security posture
The anomaly should be compared against regional advisories and naval activity.
Observation Timeline
A readable state history that can later become a PDF section.
Normal operating envelope
Oct 2025 - Feb 2026
Historical scenes define the local baseline for Hormuz corridor activity.
Suppression signal
Mar 06 and Mar 30
Traffic-like activity was depressed relative to baseline expectations.
Peak anomaly
Apr 11
The report flags the corridor as an extreme abnormal operating state.
Partial recovery
Apr 23
The corridor improved but did not fully return to the baseline envelope.
Recommended Actions
This is where the report becomes useful to an operator, insurer, or analyst.
Monitor
Keep Hormuz on enhanced watch through the next SAR collection cycle.
Compare
Check whether related Gulf corridors show matching state shifts.
Escalate
Review advisories, insurance exposure, and energy transit dependencies.
Report Inputs
Kept compact here; implementation details belong in the appendix.
Technical Appendix
These details support the judgment but should not lead the customer-facing report.
SAR residual evidence
Observed radar backscatter and modeled sea-state response diverge in a way that is not consistent with a simple weather replay.
Physics correction
Metocean context and CMOD residualization separate wind-driven surface effects from activity-like structure.
Dynamic geoEmbedding
Scene-level vectors encode the corridor state at each observation time and support baseline, weather, and trajectory comparisons.
AIS treatment
AIS is partial context rather than ground truth. Cooperative actors may go dark for safety; adversarial actors may go dark for evasion.
Backend implication
Build the backend around a generated corridor report object: AOI, observations, state assessment, findings, exposure, recommendations, appendix evidence, and API-ready JSON. The map is evidence, not the product.