Strait of Hormuz & Oil
The Strait of Hormuz thread is the story of how a military operation became an energy crisis — and how the information environment processed that transformation in real time. Within hours of the first strikes on February 28, the question shifted from 'what was hit' to 'what flows through Hormuz,' and every ecosystem on earth scrambled to narrate the answer. Russian milblogs amplified the closure before Western outlets had confirmed it. Iranian state media calibrated a deliberate ambiguity — 'we haven't closed it, but it isn't open' — that proved more destabilizing than an outright blockade. Chinese, Indian, and Gulf sources negotiated passage deals bilaterally, fracturing the narrative into a patchwork of who-can-transit and who-cannot.
The arc bends through three phases. First, the shock phase (Feb 28–Mar 5): tanker suspensions, insurance cancellations, and oil price surges dominated, with Russian channels leading volume and OSINT accounts providing the visual evidence. Second, the confrontation phase (Mar 5–Mar 18): Trump's repeated promises to reopen the strait collided with Iran's operational control, producing a daily cycle of ultimatum, defiance, and market whiplash. Third, the normalization-of-blockade phase (Mar 18–present): Iran began charging transit fees, granting selective passage to 'friendly' nations, and the information environment shifted from crisis reporting to structural analysis of a new energy geography.
What makes this thread remarkable as a media-observatory subject is the inversion it reveals: the insurance industry closed Hormuz faster than the IRGC did. By editorial #65, we noted that maritime insurers canceling war-risk coverage achieved what mines and missiles could not — a de facto blockade driven by commercial risk calculus, not military force. The information environment never fully reckoned with this distinction, preferring the dramatic narrative of Iranian naval control to the mundane reality of Lloyd's of London spreadsheets.
First Signal
The items before February 28 are noise — stray keyword matches from Russian channels discussing unrelated maritime topics. The @kvmalofeev post from February 18 about Baltic piracy has nothing to do with Hormuz. The thread begins at ~07:40 UTC on Friday, February 28, when Rybar broke the strikes and immediately connected them to naval targeting.
By late morning (11:00–13:00 UTC), the Hormuz dimension crystallized rapidly. Rybar's 'Burning Sea' dispatch at 11:07 framed the naval strikes as central. Within ninety minutes, Reuters (via @intelslava at 12:26) reported major oil companies suspending Hormuz shipments, and @middle_east_spectator at 12:35 made the prescient observation: 'Oil installations are much easier to hit.' The information environment identified the energy vulnerability before the first IRGC naval response.
Coverage Widens
Saturday afternoon through Sunday morning (Feb 28, 14:00–Mar 1, 10:00 UTC): the closure narrative took hold. Boris Rozhin at 14:09 reported Iranian media announcing the Hormuz blockade; Soloviev amplified at 15:28 with the claim that tanker movement had 'completely stopped.' By 15:46, @middle_east_spectator carried the IRGC Navy's VHF announcement that no vessels could cross.
The ecosystem split was immediate. Russian channels led with maximalist framing — full blockade, oil apocalypse. BBC Persian at 19:59 took a different angle, reporting the Financial Times on insurance cancellations. The US Department of Transportation advisory (via @intelslava at 17:36) urging vessels to avoid the entire Persian Gulf confirmed the reality without the drama. By 20:02, satellite imagery of tanker clusters at the strait's entrance made the blockade visual.
Coverage Widens
Sunday March 1, 10:00–Monday March 2, 08:00 UTC: the thread's first major amplification spike. The Russian diplomatic ecosystem entered when Zakharova responded to Belgium's seizure of the tanker Ethera (37,800 views at 10:41). At 11:30, @intelslava posted footage of a Palau-flagged tanker burning in the Gulf of Oman — the first visual proof of a vessel struck. Soloviev's amplification at 11:56 (89,600 views) of the sinking tanker set the viral threshold.
Iraq and Saudi Arabia's joint call to 'protect Hormuz' (via @intelslava at 11:46) signaled Gulf states entering the narrative as stakeholders, not observers. BBC Persian at 16:31 carried Maersk's suspension of Hormuz transits — when the world's largest shipping company stops, the commercial reality overtakes military claims. The thread crossed from security reporting into global economic crisis coverage.
Coverage Widens
Monday March 2, 08:00–Tuesday March 3, 10:00 UTC: Iranian strikes on Gulf energy infrastructure dominated. Rozhin at 08:13 reported strikes on Iranian oil facilities in Ahvaz, while simultaneously Soloviev and TASS at 08:20 carried footage of Saudi Aramco burning. AbuAliExpress (Israeli OSINT) at 12:29–13:00 reported Qatar's LNG production halted — a development that would have massive downstream effects.
The ecosystem cross-pollination was striking: Iranian Tasnim at 21:47 provided expert analysis of the Aramco strike's significance, while Tengrinews (Kazakhstan, 46,300 views) carried the story for Central Asian audiences. The thread had gone genuinely global. Al Jazeera Arabic at 17:53 reported Chinese shipping lines unable to reach Iraqi ports — the supply chain disruption was no longer theoretical.
Peak Activity
Tuesday March 3, 10:00–22:00 UTC: IRGC strikes expanded to UAE (Fujairah) and Oman (Salalah port), reported by Milinfolive and Readovka at 10:28. The IRGC General Jabbari declaration — 'Not a single drop of oil will leave the Persian Gulf' (Middle East Spectator, 11:55) — became the thread's defining quote.
The US domestic dimension entered when Soloviev at 10:17 reported Congressional uproar over the administration's war justification. Al Jazeera Arabic at 15:13 and 15:50 carried WSJ reports on Trump being 'open to' regime change and Iranian weapons depletion — the American information ecosystem's internal contradictions were being amplified across every other ecosystem simultaneously.