Five tanker incidents in the Gulf, and a US blockade strike in the Gulf of Oman
9 incidents in seven days, seven of them in the Strait of Hormuz, the Gulf of Oman and the Arabian Gulf. Two seafarers were killed. Every incident is sourced and plotted on the map.
This week at a glance
Incidents by region · Palaemon summary
High activity7South-East Asia
Active2Gulf of Aden & Somali Basin
Quiet0Red Sea & Bab el-Mandeb
Quiet0Black Sea
Quiet0Gulf of Guinea
Quiet0Americas
Quiet0
Counts are Palaemon's own tally of the incidents listed in this report. The Palaemon summary is based only on this week's count: 0 = Quiet, 1–2 = Active, 3–5 = Elevated, 6 or more = High activity. It is not a threat assessment.
Where it happened
Tap a marker for the summary. Positions are approximate, taken from the source reports.
Region by region
All times are UTC unless marked local. Vessel types are as reported. We don't name vessels.
Hormuz, Gulf of Oman & Arabian Gulf
High activityIndian-flagged dhow
Strait of Hormuz, near Limah, Oman (outbound transit)
An Indian-flagged dhow with 14 Indian crew was hit while sailing outbound through the strait. India's Ministry of External Affairs said one crew member died of his injuries and the other 13 were rescued. UKMTO said the Royal Navy of Oman rescued the surviving crew and that the status of the vessel was unknown. India's shipping minister said the dhow had been struck by an unidentified aerial object.
Source: UKMTO Warning 194-26; Anadolu Agency; The Maritime Executive
Tanker (VLCC)
Strait of Hormuz, 14 NM north-east of Lima, Oman
The tanker's Company Security Officer reported that it had been struck by two unknown projectiles in the engine room. No casualties or environmental impact were reported at the time. Trade press described the vessel as a VLCC. It was the third strike off Lima in three days, after a tanker on 1 Nov (UKMTO 193) and the dhow on 2 Nov (UKMTO 194-26).
Source: UKMTO Incident 195-26; Ship & Bunker; Seatrade Maritime News
Marshall Islands-flagged tanker
Central Arabian Gulf, 50 NM north of Madinat ash Shamal, Qatar
The tanker was struck by two unidentified projectiles. MSCIO put the time at about 23:20 UTC on 4 Nov; UKMTO lists it on 5 Nov. On 7 Nov the Philippines' Department of Migrant Workers confirmed that one Filipino crew member had been killed and another injured; all 22 crew were Filipino. The ship's manager said the crew put out a fire caused by the explosion and that no pollution was reported. The vessel was taken to Khalifa Bin Salman Port, Bahrain, for the hull damage to be assessed.
Source: UKMTO Warning 196-26; MSCIO Alert 170/26; The Maritime Executive; GMA News (Philippine DMW)
Tanker
Strait of Hormuz, 16 NM east of Khasab, Oman (outbound transit)
The master reported an explosion at the waterline on the port side. UKMTO received the report late and issued its warning at about 12:00 UTC on 6 Nov. All crew were safe and accounted for, and the tanker stayed under its own power and continued its voyage. UKMTO did not state the cause or the extent of the damage; authorities are investigating. MSCIO also reported it (171/26).
Source: UKMTO Warning 197-26; JMIC Advisory Update 112 (8 Nov)
Tanker
Strait of Hormuz, 8 NM north-west of Khasab, Oman
UKMTO received a time-late report that military authorities said a tanker was on fire and its crew had been evacuated. UKMTO did not state the cause of the fire, the vessel's flag, the number of crew or whether anyone was hurt; authorities are investigating. Separately, Iran's IRGC Navy claimed that two tankers caught fire after hitting naval mines that day. No official source has linked that claim to this incident.
Source: UKMTO Warning 199-26; Arab Times; JMIC Advisory Update 112 (8 Nov)
Tanker
Strait of Hormuz, outbound transit (exact position not published)
About an hour after the fire off Khasab, the Company Security Officer of a second tanker reported that it had been struck by an unknown projectile while transiting outbound. All crew were safe and accounted for, and no environmental impact was reported. MSCIO put the time at about 20:20 UTC. JMIC counted it as one of two attacks in the strait in the 72 hours to 8 Nov.
Source: UKMTO Warning 200-26; MSCIO Alert 174/26; JMIC Advisory Update 112 (8 Nov); The Maritime Executive
St Kitts-flagged bulk carrier
Gulf of Oman, about 18 NM east of Khor Fakkan, UAE
US Central Command said a US military aircraft fired precision munitions at the stern of the vessel, disabling it, after the crew ignored repeated warnings and tried to breach the US naval blockade of Iran after visiting an Iranian port. CENTCOM said it had first directed the crew to leave the targeted spaces. Crew status and damage were not given. On 8 Nov the UAE National Guard said it had rescued 22 crew from a cargo ship on fire in the Gulf of Oman, all in stable condition; it did not identify the ship, and no source has officially linked the rescue to the strike.
Source: UKMTO Advisory 198-26; US Central Command (DVIDS); Gulf News
South-East Asia
ActiveBulk carrier
Singapore Strait, eastbound lane of the TSS, about 9.7 NM off Pulau Cula, Indonesia
Three perpetrators armed with what ReCAAP ISC describes as a gun-like object were seen in the engine-room workshop. The alarm was raised and the crew mustered. One crew member was tied up and suffered a minor hand injury that needed no medical attention. Some engine spares were stolen. Singapore VTIS, the Republic of Singapore Navy and the Police Coast Guard were informed, and the information was shared with the Indonesian authorities.
Bulk carrier
Singapore Strait, eastbound lane of the TSS, about 9.4 NM off Pulau Iyu Kecil, Indonesia
Duty crew saw eight unarmed perpetrators on the poop deck trying to get into the accommodation (ReCAAP ISC reports seven to eight). The alarm was raised and the crew mustered, and the perpetrators jumped overboard and escaped. Nothing was stolen and no one was hurt. The Singapore Police Coast Guard boarded the vessel to investigate.
Source: IMB PRC live piracy map, 058-26; ReCAAP ISC list of incidents 2026
How many barriers would your vessel need?
Pick a vessel class or enter your own dimensions, then choose how much of the hull to protect. You'll see the barrier sets, pallets and deck space involved.
(1 m each)
(12 sets each)
(1000 × 1300 mm pallets)
This is an indicative estimate: one barrier set covers 1 m of guard rail, and 12 sets fit on a 1000 × 1300 mm pallet. Coverage is tailored to each vessel. We'll reply with a vessel-specific quote within one working day.
Gulf of Aden & Somali Basin
QuietRed Sea & Bab el-Mandeb
QuietBlack Sea
QuietGulf of Guinea
QuietAmericas
QuietThe week in numbers
Advisories: new and in force
New this week
- NEW8 NovJMIC Update 112 keeps the Strait of Hormuz at SEVERE, with deliberate hostile action considered highly likely, and advises mariners to stay alert to attempted mining within and next to the TSS. The Arabian Gulf, Gulf of Aden and Bab el-Mandeb/southern Red Sea are SUBSTANTIAL; the Gulf of Oman is MODERATE, with the US naval blockade still enforced through monitoring, hailing and verification queries near the approaches to Iranian ports. Source: JMIC Advisory Update 112 (8 Nov)
- NEW8 NovJMIC: vessels stationary for long periods, or keeping AIS on while at anchor, may face a higher risk of being targeted in the Arabian Gulf. Large backlogs remain at the anchorages east of the strait (about 162 vessels off Fujairah and Khor Fakkan on 8 Nov). Source: JMIC Advisory Update 112 (8 Nov)
- NEW2 – 9 NovUKMTO issued eight incident reports (numbers 193 to 200) after last week's report. Source: UKMTO recent incidents
Regulatory / insurance
- JWLA-035The Joint War Committee (LMA/IUA) amended its Hull War, Piracy, Terrorism and Related Perils Listed Areas in circular JWLA-035, dated 16 Sep 2026 and reported in the trade press on 3 Nov. The Black Sea entry now reads: “Black Sea excluding territorial waters of adjoining countries other than Russia and Ukraine”. In effect, the listed area covers the whole Black Sea, including international waters and EEZs, and the territorial waters of Russia and Ukraine, but not the territorial waters of Türkiye, Bulgaria, Romania or Georgia. The Sea of Azov and Ukraine's inland waters are also listed. Under standard war-risk terms, a vessel entering a listed area must notify its war-risk underwriters, and cover may be subject to additional premium or conditions. Source: JWC circular JWLA-035 (16 Sep 2026); MaritimeCyprus (3 Nov 2026)
Advisories in force
- MARAD 2026-011Persian Gulf, Strait of Hormuz and Gulf of Oman: Iranian attacks on commercial vessels · in force 9 Sep 2026 – 8 Mar 2027
- MARAD 2026-013Red Sea, Bab el-Mandeb, Gulf of Aden, Arabian Sea and Somali Basin: Houthi attacks on commercial vessels · in force 23 Sep 2026 – 22 Mar 2027
- MARAD 2026-010Gulf of Aden, Arabian Sea and Indian Ocean: piracy, armed robbery and kidnap for ransom · in force 7 Aug 2026 – 4 Feb 2027
- MARAD 2026-012Black Sea and Sea of Azov: military combat operations · in force 23 Sep 2026 – 22 Mar 2027
- MARAD 2026-009Gulf of Guinea: piracy, armed robbery and kidnap for ransom · in force 24 Jun 2026 – 21 Dec 2026
- MARAD 2026-014Worldwide: foreign adversarial technological, physical and cyber influence · in force 21 Oct 2026 – 19 Apr 2027
- GuidanceBMP Maritime Security (BMP MS, June 2026 edition) is the industry guidance UKMTO and MSCIO refer vessels to.
Also reported (not in the count)
- Strait of Hormuz, unverified claims: Iran's navy and the IRGC Navy said on 2, 3, 5 and 7–8 Nov that tankers (and on 5 Nov a tug) had hit naval mines or caught fire after using routes Tehran calls unauthorised. None of the claims gave a vessel, position or time, and UKMTO, JMIC and MSCIO have not confirmed them. One tanker fire off Khasab on 7 Nov (UKMTO 199-26) is counted above on its own report, not on the IRGC claim. Source: Shafaq News (2 Nov); Reuters via Arab News (5 Nov); The Hindu / IRNA (8 Nov)
- Black Sea, unverified claims: Russia's Defence Ministry claimed strikes on cargo ships at sea and in the ports of Pivdennyi (3 Nov), Odesa (4 and 6 Nov) and Chornomorsk (8 Nov), plus a container ship bound for Odesa and a dry cargo ship south-west of Odesa (8 Nov). Reuters could not independently verify the 8 Nov claims and Ukraine had not commented. No vessel, flag, position or damage was given. Source: Reuters via gCaptain (8 Nov); TradeWinds (4 Nov); FLANK (6 Nov claim)
- Strait of Hormuz, late report from last week: a tanker was struck by an unknown projectile about 9 NM north-east of Lima, Oman, at about 20:20 UTC on 1 Nov (UKMTO 193; MSCIO 166/26). The master reported a hole on the starboard side; the vessel and crew were safe. It fell in last week's window but was not in last week's report. It is on the Palaemon heat map. Source: MSCIO Alert 166/26; UKMTO recent incidents (entry 193); Gulf News (AFP)
Plan barriers for your next transit
Tell us the vessel and the route. We'll come back with a vessel-specific quote for anti-piracy barriers within one working day.
Sources
- UKMTO incident report 194-26
- Anadolu Agency: India condemns attack on ship off Oman after national killed (3 Nov 2026)
- The Maritime Executive: Indian seafarer killed in strike in Strait of Hormuz (3 Nov 2026)
- UKMTO incident report 195-26
- Ship & Bunker: tanker hit by two projectiles in engine room off Oman (4 Nov 2026)
- Seatrade Maritime News: VLCC engine room struck in latest Hormuz attack (4 Nov 2026)
- UKMTO incident report 196-26
- MSCIO alerts (Alert 170/26)
- The Maritime Executive: one seafarer reported killed in strike on a tanker off Qatar (5 Nov 2026)
- GMA News: DMW says Filipino seafarer killed, another hurt in Persian Gulf tanker attack (7 Nov 2026)
- UKMTO incident report 197-26
- JMIC Advisory Update 112 (8 Nov)
- UKMTO incident report 199-26
- Arab Times: tanker catches fire off Khasab, crew evacuated (8 Nov 2026)
- UKMTO incident report 200-26
- MSCIO Alert 174/26
- The Maritime Executive: tanker burns after strike in Strait of Hormuz (8 Nov 2026)
- UKMTO incident report 198-26
- US Central Command via DVIDS: US forces disable cargo vessel attempting to violate naval blockade (7 Nov 2026)
- Gulf News: UAE rescues 22 after cargo ship fire in Gulf of Oman (8 Nov 2026)
- ReCAAP ISC list of incidents 2026
- IMB Piracy Reporting Centre: live piracy map (058-26)
- Hindustan Times: Navy rescues crew of hijacked Iranian vessel (3 Nov 2026)
- MSCIO Alert 168/26
- MSCIO Alert 172/26
- Reuters via gCaptain (8 Nov)
- TradeWinds (4 Nov)
- MARAD 2026-009: MARAD 2026-009
- UKMTO recent incidents
- JWC circular JWLA-035 (16 Sep 2026)
- MaritimeCyprus (3 Nov 2026)
- MARAD 2026-011: Persian Gulf, Strait of Hormuz and Gulf of Oman: Iranian attacks on commercial vessels
- MARAD 2026-013: Red Sea, Bab el-Mandeb, Gulf of Aden, Arabian Sea and Somali Basin: Houthi attacks on commercial vessels
- MARAD 2026-010: Gulf of Aden, Arabian Sea and Indian Ocean: piracy, armed robbery and kidnap for ransom
- MARAD 2026-012: Black Sea and Sea of Azov: military combat operations
- MARAD 2026-014: Worldwide: foreign adversarial technological, physical and cyber influence
- Shafaq News (2 Nov)
- Reuters via Arab News (5 Nov)
- The Hindu / IRNA (8 Nov)
- FLANK (6 Nov claim)
- MSCIO Alert 166/26
- UKMTO recent incidents (entry 193)
- Gulf News (AFP)
Method: this report covers incidents with a reported date between 09:00 UTC on 2 Nov and 09:00 UTC on 9 Nov 2026. It starts from the confirmed incidents on the Palaemon piracy heat map and cross-checks them against UKMTO's incident feed, JMIC advisory updates, MSCIO alerts, the IMB PRC live piracy map, ReCAAP ISC's 2026 incident list, MARAD advisories and reputable press. The count is Palaemon's own tally of the incidents listed. Two incidents dated 2 Nov before 09:00 UTC were in last week's report and are not counted again. Claims that no official centre has confirmed are listed separately as unverified and are not counted. Positions on the map are approximate.
This report sets out reported incidents only. It is not a risk assessment or advice for a specific voyage. Coastlines: Natural Earth (public domain).
