War-risk underwriting runs on paperwork, and Tuesday's stack got thicker. Security firm Ambrey reported that the Egyptian Navy responded to the stricken tanker Amzan's calls after Monday's strike 63 nautical miles west of Yanbu, adding a naval asset to an incident file that already holds a UKMTO advisory, a main-deck fire and 320,926 deadweight tonnes of Saudi-flagged crude carrier built in 2014. [1]

Houthi spokesman Yahya Saree claimed the hit as enforcement of the group's declared ban on Saudi shipping, folding it into a wider wave that by Houthi account included convoys and weapons trucks; Bahri's own statement conceded only an incident, hostile but unattributed. Both documents are now in underwriters' hands. [1][3]

Yesterday's insurer-response watch predicted the premium notices would say what the market believes; what arrived first was the ambiguity removal. Reuters' Cairo wire still ran under no Saudi confirmation while the vessel's own owner acknowledged a hostile incident — a lag that matters to nobody adjusting a rate. [2][3] For underwriters the sequence converts an unknown-projectile event into a named loss on a named corridor: additional-premium memos for Jeddah-Yanbu transits, tighter hull conditions, charterers shuffling loading windows around new exclusions. [3]

The base rates were already moving before the missile. Lloyd's List calculates Yanbu exports have fallen by at least a third since northern Red Sea attacks began, from roughly four million barrels a day. [1] Premiums follow demonstrated reach; reach has been demonstrated at the loading zone, twice confirmed, once billed.

Watch the notices, not the adjectives. They arrive without bylines and they settle the argument.

-- DARA OSEI, London