Since early August, Iran has launched roughly thirty drone and ten missile attacks weekly on Hormuz shipping, The New York Times reported from Western official data, with at least four ships hit in ten days. Washington claims an ironclad export blockade; Tehran is legislating transit fees. Dueling transit counts keep oil on a permission premium.
The Strait of Hormuz is not a switch labeled open or closed. It is a permission market operating under fire: cargoes move when a flag, a navy, an insurer, and a political exception align long enough for one voyage. That is the durable frame. What changed in the first days of October is the tempo—and the evidence that both Washington and Tehran are trying to write the rules of passage into coercion, not diplomacy alone.
The attack cadence the headlines undercount
The New York Times, citing confidential data from a Western security official, put the pace at roughly thirty drone and ten anti-ship missile attacks per week since early August, with at least four commercial ships hit in the preceding ten days as of October 2. UKMTO tallies cited in the same reporting recorded at least thirteen strikes since September 10, mostly on tankers, from voluntary crew reports that may be incomplete. Iran’s Revolutionary Guard appeared to confirm near-daily strikes in the strait—matching weeks of coastal explosions. Isolated “projectile hit” headlines understate that cadence.
On October 1, UKMTO Warning 147-26 reported a tanker struck by an unidentified projectile and ablaze; crew were safe. The vessel was identified in maritime reporting as Kuwait-flagged MT Kazimah III; India’s embassy in Oman rescued five Indian nationals. Additional UKMTO warnings covered late-September hits, including traffic near Khor Fakkan. JMIC kept the regional threat at SEVERE.
A permission market under weekly salvos is not a “thin but functioning channel.” It is a chokepoint where survival, not schedule, sets the price.
Two blockades, one strait
Washington is not only escorting tankers along Omani routes. Pete Hegseth said the United States controls Hormuz, that Iran has “gotten nothing through,” and that the export blockade is “ironclad,” with throughput he said nears pre-war levels—claims Tehran disputes and that independent counts rarely match.
On Saturday, October 4, Donald Trump told Rudaw he would decide on Iran’s “easy way or the hard way.” CBS News said Camp David hosted Vance, Rubio, Hegseth, and the Joint Chiefs on Friday for Iran and Yemen—while Trump has tied an endgame to the midterm window Culled mapped in why Tehran might wait on November.
Tehran’s parallel move is legislative. On October 2, parliament’s National Security Commission completed committee review of a bill that would preserve Iranian management of strait traffic and charge commercial vessels fees for navigation, environmental services, bunkering, insurance, security, and related services, while barring transit by Israeli-linked, “hostile,” or military cargo hulls and requiring prior authorization from Iran’s General Staff for others. The measure still needs a full parliamentary vote and Guardian Council review before it becomes law—but it is the permission market drafted in statutory form, the strongest available evidence for the thesis that passage is for sale under state control.
The transit numbers fight each other
Whether Hormuz is “functioning” depends on which sensor you trust—and honest analysis should say so.
IMF PortWatch logged one transit on September 27 against a pre-crisis baseline near eighty-five per day on its AIS methodology; other publishers show single-digit visible crossings on many days while U.S. officials cite protected throughput. Kpler says much “recovery” is bypass: about forty percent of Gulf crude now avoids Hormuz via pipelines and Gulf of Oman loadings, up from seventeen percent pre-war, plus offshore shuttle transfers. Volumes can rebound while the strait stays struck. That measurement fight is why “flows are up” and war risk can coexist—see trust deficits on reopening and markets that priced peace too fast.

Yemen widens the map; it does not merge the commands
Yemen’s Houthis claimed strikes on an Aramco site near Riyadh; smoke was reported, Saudi spokesmen called the claim misleading, and Aramco had not immediately confirmed damage. Treat that as correlated energy risk, not proof of unified Iranian command—see Mocha and Bab el-Mandeb and the Red Sea backup that is not backup.
The permission-market read holds while weekly attacks, fee legislation, and dueling transit statistics move together. It weakens only when multi-flag transits, stable war-risk terms, and a verifiable enforcement regime make the next voyage predictable—not when one VLCC or one rescued crew slips through.
Continue reading
Sources
The New York Times and syndicated reporting (Oct. 2, 2026) on Western official data for weekly drone and missile attack rates and recent hits; UKMTO warning 147-26 and gCaptain on the Oct. 1 tanker strike; Indian Embassy in Oman on MT Kazimah III crew rescue; Anadolu/WANA on Iran’s National Security Commission completing review of a Hormuz fee and authorization bill (Oct. 2); AP-carried reporting on Defense Secretary Pete Hegseth’s blockade remarks (Oct. 3); Rudaw on-camera Trump quote (Oct. 4); CBS News on the Oct. 3 Camp David Iran-Yemen session; Kpler and BBC on bypass and shuttle routes; Al Jazeera on disputed Houthi claims near an Aramco site in Riyadh.