🔔 Subscribe to ShipUniverse Weekly →
Iran’s Revolutionary Guards Navy said Wednesday that a containership carrying more than 2,500 containers struck a naval mine, caught fire and sank in waters south of the Strait of Hormuz after using what the Guards described as an unauthorized and dangerous route. The vessel was not identified by Iran, and no crew information was released. The mine strike and sinking had not been independently confirmed when the first international reports appeared; AP noted that UKMTO had not issued a corresponding mine-sinking alert. Separately, however, NAVAREA IX issued an independent warning at 03:00 UTC for the Singapore-flagged containership GFS Pride, reporting a security incident, fire and drifting approximately one nautical mile east of Ras Makhbuq in the Strait. GFS Pride is a 2,824-TEU vessel, making it broadly consistent with Iran’s description, but no authoritative source has yet confirmed that it is the ship Iran says struck the mine or that a mine caused its casualty.
Strait of Hormuz · October 14, 2026
A Mine Claim Changes the Risk Model
Missile and drone attacks threaten individual ships. A confirmed mine threat can make an entire transit corridor suspect until the waterway is surveyed, cleared or commercially accepted as safe.
IRGC CLAIM · NOT YET INDEPENDENTLY CONFIRMED
Container Ship Struck Mine and Sank
2,500+ Containers
Iran's Revolutionary Guards Navy says the vessel entered an unauthorized and dangerous route, struck a naval mine, exploded, caught fire and subsequently sank south of the Strait. Iran did not identify the ship, flag, owner or crew.
INDEPENDENT MARITIME WARNING
GFS PRIDE in Security Incident
Fire + Drifting
NAVAREA IX 371/26 names GFS PRIDE in a security incident at 26°23.70'N 056°23.60'E, approximately one nautical mile east of Ras Makhbuq. The warning reports fire and drifting but does not identify a mine or confirm a sinking.
Why GFS PRIDE Is Being Watched Closely
Vessel Type
Container Ship
Matches the broad vessel type described by the Iranian statement.
Capacity
2,824 TEU
Broadly consistent with an Iranian description of more than 2,500 containers.
Flag
Singapore
IMO 9349045, built 2008, operated in regional container services.
Identity Link
Not Confirmed
No authoritative source has publicly stated that GFS PRIDE is the mine casualty claimed by Iran.
Mine Mechanism
Area Threat
If confirmed, operators must consider whether additional mines could remain in or near commercial routes.
Shipping Lane
2 Miles Wide
Each directional Hormuz traffic lane is only about two nautical miles wide, separated by a two-mile buffer.
JMIC Threat Level
Severe
Merchant shipping was already operating under the second-highest JMIC threat category before today's mine claim.
U.S. MCM Mission
Bahrain Based
U.S. Fifth Fleet maintains mine-countermeasure capabilities in the region using modern LCS and unmanned systems.
Reporting threshold:
A security incident involving GFS PRIDE is independently documented. A mine strike and sinking are, at this stage, claims by Iran's Revolutionary Guards Navy. Until a flag state, owner, salvage authority, naval force or independent maritime-security organization confirms the mechanism, the article should not state as established fact that a naval mine sank the ship.
Evidence · Underwriting · Container Shipping · Tankers · Naval Response
What a Confirmed Mine Would Change
A projectile attack can often be treated as an individual casualty. A mine can force operators to question the safety of the route itself because the weapon may remain active without another attacker being present.
Scroll sideways for the full evidence and impact board
← →
| Issue | Current Status | What Is Supported | What Is Not Yet Established | Operational Significance | Next Confirmation Point |
|---|---|---|---|---|---|
| Naval Mine | IRGC CLAIM Not Independently Verified | Iran's Revolutionary Guards Navy says a containership struck a naval mine south of Hormuz and subsequently sank after a severe fire. | No independent forensic confirmation of the explosive mechanism, mine type, laying location or responsible party. | If confirmed, operators must consider persistent area risk rather than only attacks occurring at a specific moment. | Mine fragments, naval survey results, hull-damage analysis or confirmation from a flag state / owner. |
| Vessel Identity | POSSIBLE MATCH GFS PRIDE | NAVAREA IX independently reports GFS PRIDE in a Strait security incident with fire and drifting early October 14. | No authoritative source has linked GFS PRIDE to the IRGC mine claim or confirmed that the ship sank. | The vessel's 2,824-TEU capacity is close enough to Iran's 2,500-container description to merit attention without treating identity as settled. | Statement from GFS Ship Management, Singapore authorities, class, P&I, salvors or NAVAREA update. |
| Container Shipping | DIRECTLY EXPOSED Multiple Recent Incidents | UKMTO Warning 167 already confirmed a container vessel struck by an unknown projectile during an inbound Hormuz transit on October 11/12. | Whether today's casualty is linked to that earlier incident or represents another separate containership loss. | Container operators must now consider cargo accumulation, floating containers, reefer loss, dangerous-goods exposure and salvage in addition to hull risk. | Carrier service suspensions, blank sailings, rerouting or Gulf-port restrictions. |
| Tanker Market | ALREADY DISTORTED High Security Premium | Tanker attacks have already driven route changes, STS dependence, vessel scarcity and record freight economics. | No evidence yet that today's mine claim has caused a new formal tanker-route closure. | A confirmed minefield could restrict the exact passage required by crude, product and LNG carriers regardless of individual vessel nationality. | Charterer refusals, naval routing instructions, insurance requotes and measurable traffic reduction. |
| Marine Insurance | WAR RISK ALREADY HIGH Mine Risk Adds Persistence | Hormuz war-risk cover remains available but premiums have risen sharply during the conflict. | No authoritative market-wide repricing specifically attributable to today's mine report has yet been published. | Underwriters may need to assess not only probability of attack but whether a route is physically surveyed and cleared. | Lloyd's / JWC guidance, P&I circulars, exclusion changes and quoted additional-premium movements. |
| Naval Forces | MCM MISSION RELEVANT Survey + Clearance | U.S. Fifth Fleet maintains dedicated mine-countermeasure capability from Bahrain using LCS mission packages, unmanned systems and EOD forces. | No publicly confirmed mine-clearance operation tied specifically to today's casualty has been announced. | A credible mine threat can require route survey, classification, neutralization and repeated clearance before operators regain confidence. | NAVCENT/JMIC mine advisories, exclusion zones, convoy changes or declared cleared channels. |
Scroll sideways from either bar
← →
Why Mine Risk Is Especially Powerful in Hormuz
2 NM
Inbound Traffic Lane
2 NM
Separation Zone
2 NM
Outbound Traffic Lane
The Strait is roughly 21 miles wide at its narrowest point, but normal commercial traffic is concentrated into two narrow directional lanes. A suspected mine inside or adjacent to those lanes can therefore affect a much larger share of shipping than its physical footprint would suggest.
Ship Universe Mine Disruption Tool
Hormuz Mine-Clearance & Vessel Backlog Analyzer
Model the shipping backlog that could develop if a suspected mine forces a temporary closure followed by restricted traffic while a commercial route is surveyed or cleared.
ships/day
Editable default based on late-September JMIC-reported traffic, not a current October 14 count.
hours
% normal
days
% normal
$/day
User-entered scenario value. Actual tanker, LNG and container delay costs vary widely.
Closure Backlog
30
Ships unable to transit during the entered full-closure period.
Restricted-Period Shortfall
24
Additional vessel backlog created while traffic runs below normal throughput.
Maximum Modeled Backlog
54
Closure backlog plus restricted-throughput shortfall.
Recovery Capacity
+6/day
Additional ships per day handled above normal once full operations resume.
Backlog Clearance Time
9 days
Estimated time required to clear the modeled queue after throughput increases.
First-Day Delay Exposure
$2.7M
Maximum backlog multiplied by the entered daily delay cost.
Traffic Sequence
A mine event can create delay even after a route technically reopens because restricted passage can keep adding ships to the queue.
Normal traffic
30/day
Restricted traffic
18/day
Recovery traffic
36/day
Modeled Maximum Queue
54 ships
Under these assumptions, a one-day closure followed by two days at 60% capacity creates a queue equivalent to almost two normal days of Hormuz traffic.
Scenario limitation:
This model does not estimate mine probability or predict that Hormuz will close. It illustrates how quickly a backlog can form if naval survey, mine clearance, routing restrictions or underwriter requirements temporarily reduce transit capacity. The default 30-transit figure is a late-September reference and should be edited when newer verified traffic data are available.
Feedback Welcome
We welcome your feedback, suggestions, corrections, and ideas for enhancements.
Please click here to get in touch