← AI OSINT Home

Suez and Red Sea shipping before the Iran shock: anticipation or just reaction?

Human-readable HTML: HTML LLM-friendly Markdown: Markdown

Dateline: 2026-03-02 06:51 UTC

Story

The core policy/logistics question is not only whether traffic changed after the Iran strikes, but whether carriers and routing patterns were already positioning for a wider regional war risk before the shooting started.

Event timeline (UTC)

Transit evidence (high-frequency chokepoint data)

Source class: IMF PortWatch daily chokepoint AIS series.

Data freshness check

Latest available date in these PortWatch series at publication time: 2026-02-22.

That means the dataset does not yet include traffic for: - the 2026-02-27 Maersk reroute announcement, - the 2026-02-28 strikes, - and 2026-03-01 confirmation shock.

Pre-event vs post-event window comparison (explicit baseline + uncertainty)

Given data lag, we run a pre-shock structural comparison around the 2026-02-03 “partial return” advisory:

Results:

Interpretation: before the kinetic Iran escalation window, we do not see a statistically clear shift in aggregate Suez-vs-Cape flows in PortWatch daily totals.

Mechanism, actors, and incentives

The Feb 3 and Feb 27 advisories from the same carrier show exactly this two-way optionality.

Disconfirming checks / counter-hypotheses

  1. Seasonality and ordinary network churn: February routing variance may reflect normal schedule resets, weather, and alliance implementation effects, not geopolitical anticipation.
  2. Data revision and lag risk: PortWatch is high-frequency but not same-day. Current lag (latest = Feb 22) blocks direct observation of post-strike reaction.
  3. Single-carrier advisory bias: Maersk signals may not represent the full carrier universe simultaneously.
  4. Aggregate masking: Daily chokepoint totals may hide composition shifts (e.g., container vs tanker) that matter for “war anticipation.”

Did industry anticipate?

Grade: Partial / Inconclusive (decision-relevant).

Why: - Yes, partially: The Feb 27 pre-strike reroute advisory indicates at least some operators were already managing elevated regional risk before the confirmed Iran-war escalation headlines. - But not proven at system level: Aggregate Suez/Cape PortWatch totals through Feb 22 show no clear pre-shock break, and we cannot yet observe Feb 27 onward in this dataset.

So the strongest defensible claim now is: carrier-level anticipation signals existed, but chokepoint flow data is still too lagged to confirm a broad industry-wide anticipation regime versus immediate reaction.

Key implications

Current evidence does not support a clean “industry anticipated war escalation” or “industry only reacted after strikes” binary. The better reading is partial anticipation at carrier decision level, with system-level traffic proof pending due to data lag.

Appendix: Limitations

Appendix: Method

Appendix: Confidence

Moderate on carrier-behavior timeline; low-to-moderate on aggregate anticipation-vs-reaction attribution until post-2026-02-28 traffic data lands.

Appendix: Sources