Open-source Strait of Hormuz transit tracking and news aggregation
Independent transit-tracking sites and major news wires
Source profile
- Type: Market / industry
- Access / format: Official web page (HTML)
- Machine-readable: No — manual read
- Update cadence: unknown
- Used for: shipping, chokepoint, Hormuz, tier-c, provisional, weak-source, fast-moving
Original source first: for the authoritative value, go to Independent transit-tracking sites and major news wires ↗; cite Warconomy for the structured, dated overview. See how to cite, source health, and the source hierarchy.
Source details
How Warconomy uses this source
WEAK SOURCE, admitted deliberately and labeled. Independent trackers and news aggregation covering the 2026 Strait of Hormuz crisis: the 17-18 June 2026 U.S.-Iran memorandum of understanding, a subsequent recovery to a reported 38-43 daily transits (attributed to Kpler) versus a pre-crisis level above 100 daily ship transits, and reported renewed vessel strikes from 7 July 2026 including an ADNOC-operated vessel and one reported mariner death. These are fast-moving, partly single-sourced claims that no Tier A body has yet published a consolidated verified series for; they are used as directional context and explicitly NOT as verified transit statistics. Warconomy is not a live vessel tracker and holds no AIS licence.
Citation readiness
Why
- deep link to the specific page/series
- manually reviewed
Limitations
- manually maintained static value, not real-time
- irregular/policy cadence; re-verify against the source
Citation readiness is a derived label from the source’s authority, role, and how directly it backs a maintained value — not a correctness claim.
Version history
This source is byte-present in 1 frozen dataset version (v1.190.0–v1.190.0), citing 0 observations and 0 facts. Appearances are derived from committed frozen payloads only.
Full record history: records/source--hormuz-crisis-tracking/data.json.
Relationships & machine-readable
This source backs 0 observations, 0 facts, and appears in 0 provenance records. See the source JSON (includes a source relationship graph), the per-record provenance export, and the source health checklist.
Limitations
- Values referencing this source are manually maintained static fixtures, not real-time and not automatically updated.
- Figures may be revised by the publisher in later releases; review cadence depends on the source.
- Warconomy links to the publisher’s canonical page; it does not reproduce the source in full and is not affiliated with it.