The International Maritime Organization\u2019s highlighted-incidents board, as at 9 November, now prints 131 confirmed incidents in the Strait of Hormuz and the wider Middle East, with 25 confirmed seafarer fatalities. Monday midday\u2019s dedicated conversion on this desk sat at 130 as at 6 November, with 25 dead, and with Vieila\u2019s 5 November row 16 nautical miles east of Khasab as the named top line. The as-at date has moved. The confirmed-incident count has moved by one. The fatality line has not moved. What arrived overnight on the public English page is a later as-at stamp and one new named row at the top of the table. IMO now prints HUDA, IMO 9197088, dated 7 November, 17 nautical miles from the coast of Oman, damaged, no pollution. Tuesday morning is the first official IMO print of that hull.<\/p>\n
The count is an IMO product. It is not a UKMTO warning, not a rewrite of Sunday night\u2019s dedicated Update 112, not a rewrite of Saturday night\u2019s dedicated Advisory 198-26, not a rewrite of Monday midday\u2019s dedicated 130-count naming, and not a rewrite of Friday night\u2019s dedicated Warning 197-26. Update 112, ICOD 081300 UTC 8 November, already named HUDA against dedicated 198-26 as wrap and still withholds 197-26, 199-26 and 200-26. UKMTO\u2019s 198-26 PDF still prints an unnamed bulk carrier, military forces, 18 nautical miles east of Khor Fakkan, incident time TBC, and crew \/ damage \/ environment unknown. Those are different instruments from IMO\u2019s 131. Masters who brief Tuesday morning as Update 112 finally becoming an IMO table, as UKMTO finally printing that hull on the original PDF, as a 26th fatality, or as a Hormuz reopen will have misread the sheet. Monday midday\u2019s dedicated file on this desk correctly held the count at 130 as at 6 November. Tuesday morning\u2019s board has added a 131st named row and has moved the as-at date to 9 November. Log the move. Do not invent a second new hull to explain it.<\/p>\n
Monday midday\u2019s English page was 130 confirmed incidents, 25 dead, as at 6 November, with VIEILA as the operational top row of that snapshot \u2014 damaged, no pollution \u2014 and with VELOS SAPPHIRE, LARGO ATOM, SELAT STORM, AL MAYEDA, RITI, LOUISE 1, ARZANAH, GHANA PROSPERITY, LEONORA KOSAN, SOYIA, CHLOE (MIVERVA V), AL DASMA, JIF BARRACUDA, LOYALTY, ST3, GFS PRIDE, GFS GISELLE, AL SAADIYAT, DP WORLD KAVERI, KITION M, EVER VICT, AL MAQAM, ANGOLA PROSPERITY and PETRO DOLPHIN already on the sheet. Tuesday morning\u2019s English page is 131 as at 9 November, 25 dead. The increment is one confirmed incident. The as-at date has moved three days, from 6 November to 9 November. One new named row sits at the top of the table, above Monday\u2019s Vieila line. That arithmetic is a single-row move on a later as-at date. Do not invent a second new name. Do not treat the +1 as a silent conversion of Sunday morning\u2019s dedicated 199-26, Sunday morning\u2019s dedicated 200-26, Friday night\u2019s dedicated 197-26, Tuesday night\u2019s dedicated 195-26, Tuesday night\u2019s dedicated 194-26, Monday night\u2019s dedicated 193-26, Sunday night\u2019s dedicated 191-26, Tuesday afternoon\u2019s dedicated Al Jusufi statements, AZINI or Quba. Those products remain unnamed on this board as new Tuesday rows. Do not treat the +1 as a Contship Jet conversion. That hull does not belong on this Middle East table. One increment from the earlier 114-to-119 jump is still unnamed on this public sheet. The fatality line is still 25, on Velos Sapphire, not on this new row.<\/p>\n
The new row is HUDA, IMO 9197088, 7 November, 17NM from the coast of Oman, damaged, no pollution. Saturday night\u2019s dedicated Advisory 198-26 remains an unnamed bulk-carrier Advisory, incident time TBC, source Military authorities, location footer Khor Fakkan, UAE: UKMTO has received a report of an incident involving a bulk carrier and military forces in the Gulf of Oman, approximately 18 nautical miles east of Khor Fakkan; status of crew, damage assessment and environmental impact are unknown at time of report. Sunday night\u2019s companion Update 112 reprints 198-26 as HUDA, bulk carrier, Blockade Enforcement, Gulf of Oman, identified by US CENTCOM, disabled by military forces approximately 18 NM east of Khor Fakkan. IMO does not print 198-26, TBC, \u201cbulk carrier,\u201d \u201cmilitary forces,\u201d \u201c18 NM east of Khor Fakkan,\u201d \u201cBlockade Enforcement,\u201d \u201cCENTCOM,\u201d \u201cdisabled,\u201d \u201cprecision munitions\u201d or a stern line. It prints Huda, 9197088, damaged, no pollution, 17 nautical miles from the coast of Oman, on a 7 November date. That is a tighter hull finding than the PDF, and it is a different offset wording from both the PDF and Update 112. It is also a different damage and pollution line from the PDF, which printed neither \u201cdamaged\u201d nor \u201cno pollution.\u201d The fatality total is still 25. This new row does not carry a casualty line. It is not a completed class survey. It is not a UKMTO PDF revision. It is not an Update 112 rewrite.<\/p>\n
Hold the nearby Oman-coast plots. VIEILA remains 5 November, IMO 9234654, 16NM east of Khasab, Oman, damaged, no pollution, on this same table \u2014 Monday midday\u2019s dedicated 130th row. Seventeen nautical miles from the coast of Oman is not 16 nautical miles east of Khasab. Do not promote Vieila onto the new Huda row. Do not promote a 5 November clock, a Damaged\/no-pollution line from Vieila, or IMO 9234654 onto Saturday night\u2019s dedicated 198-26. Monday midday\u2019s dedicated file already held Vieila on 197-26\u2019s east-of-Khasab offset. Tuesday morning\u2019s IMO print does not collapse that split. LOUISE 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, Oman, damaged, no pollution. SIDR remains 31 August, IMO 9854715, 17NM east of Khasab, damaged, no pollution, two seafarer fatalities. Those earlier Oman-coast rows are still on the sheet. They are not this 7 November hull.<\/p>\n
Hold the clocks. UKMTO dates 198-26\u2019s report to 7 November with incident time TBC. IMO dates the Huda row to 7 November without a time. Update 112, ICOD 081300 UTC 8 November, already named Huda against that 198-26 clock as wrap. The IMO as-at date is now 9 November. Those are separate official instruments, not one collapsed Attack. Do not invent which UKMTO number is the 7 November Huda row as a PDF fact. The 198-26 PDF has not been revised this morning. Do not collapse Huda, Vieila, Velos Sapphire, Largo Atom and Selat Storm into one early-November Attack because all five now sit near the top of the sheet. Huda is Tuesday morning\u2019s first official IMO print. Vieila remains Monday midday\u2019s dedicated 130-count print. Velos Sapphire remains Thursday night\u2019s dedicated 129-count print, converted Friday afternoon to a fatality. Largo Atom, Selat Storm and Arzanah remain Wednesday morning\u2019s dedicated 128-count prints.<\/p>\n
Official wording keeps HUDA. Industry and open-register reprints of the same 7 November Khor Fakkan clock often restated CENTCOM\u2019s St. Kitts-and-Nevis-flagged M\/V Huda line, a stern strike and a blockade-disablement. Hold that colour separately. IMO prints HUDA. It does not print a flag. It does not print \u201cM\/V.\u201d It does not print a stern. It does not print blockade. Do not tidy the board into a CENTCOM press line. Do not promote a sinking line, a spill line, an IRGC attribution, a cargo grade or a flag onto this row. IMO printed damaged and no pollution. It did not print sunk, abandoned, NUC, tow, a pollution volume, a seafarer casualty or an attacker.<\/p>\n
The rest of Monday midday\u2019s sheet is still there. VIEILA remains 5 November, IMO 9234654, 16NM east of Khasab, Oman, damaged, no pollution. VELOS SAPPHIRE remains 4 November, IMO 9321201, 50NM north of Madinat ash Shamal, Qatar, damaged, no pollution, one seafarer fatality. LARGO ATOM remains 1 November, IMO 1034747, 72NM East of Ras Al Khafji, Saudi Arabia, damaged, no pollution. SELAT STORM remains 1 November, IMO 9266657, Strait of Hormuz, damaged, pollution unknown. ARZANAH remains 28 October, IMO 9928023, Strait of Hormuz, damaged, no pollution. AL MAYEDA remains 30 October, IMO 9397298, 40NM South of Lavan Island, Iran, damaged, no pollution. RITI remains 29 October, IMO 9249075, Strait of Hormuz, damaged, no pollution. LOUISE 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, Oman, damaged, no pollution. PETRO DOLPHIN remains two seafarers missing at Sohar Anchorage. EL GAIA remains two seafarers missing. MINOAN PIONEER remains one seafarer missing. None of those rows is the Tuesday morning move. The move is the confirmed-incident count from 130 to 131, the as-at date from 6 November to 9 November, and the new Huda top row. The fatality line is unchanged at 25.<\/p>\n
Advisory 198-26 remains an unnamed PDF. The working primary on that dedicated Saturday-night file is still: ADVISORY, report date 7 November 2026, incident time TBC, source Military authorities, bulk carrier and military forces, approximately 18 nautical miles east of Khor Fakkan, UAE, status of crew, damage assessment and environmental impact unknown at time of report, location footer Khor Fakkan, UAE, filename 20261107-ukmto_advisory-198-26.pdf. UKMTO printed neither a ship name, an IMO number, a flag, a cargo, a service, a munition, a boarding, a fire, a NUC or tow line, an anchorage, a damaged line, a no-pollution line nor a latitude\/longitude beyond the 18-nautical-mile east-of-Khor Fakkan offset. Tuesday morning\u2019s IMO row does not revise that PDF. A DPA who briefs Tuesday morning as \u201cUKMTO has now named 198-26\u201d has over-read a highlighted-incidents table that does not print a warning number.<\/p>\n
Sunday night\u2019s companion Update 112, retrieved from jmic_advisory_update_112_08-nov.pdf, ICOD 081300 UTC 8 November, remains wrap on dedicated 198-26: first JMIC naming of HUDA, bulk carrier, Blockade Enforcement, Gulf of Oman, identified by US CENTCOM, disabled by military forces approximately 18 NM east of Khor Fakkan. Update 112 does print Huda. It does not print IMO 9197088. It does not print \u201c17NM from the coast of Oman.\u201d It does not print \u201cdamaged, no pollution.\u201d Update 113 was not retrieved this run. IMO\u2019s sheet is tighter on the IMO number, the 17-nautical-mile Oman-coast offset and the damaged\/no-pollution lines, and thinner on the method. It prints neither Blockade Enforcement nor CENTCOM. Hold the official lines separately. A DPA who briefs IMO\u2019s \u201cdamaged, no pollution\u201d as a UKMTO revision of 198-26 will over-read the PDF. The PDF has not been revised this morning. A DPA who briefs Update 112 as having printed 17 NM from the Oman coast, or as having printed IMO 9197088, will over-read a JMIC table that used a different offset and did not print that IMO number.<\/p>\n
CENTCOM\u2019s 7 November public statement naming St. Kitts-and-Nevis-flagged M\/V Huda, precision munitions at the stern, blockade-violation and disablement remains wrap on dedicated 198-26, unused as a completed PDF naming. That colour sits behind Update 112\u2019s \u201cidentified by US CENTCOM\u201d sourcing line. It is not an IMO flag print. It is not an IMO method print. IMO printed Huda, 9197088, 17 NM from the coast of Oman, damaged, no pollution. It did not print St. Kitts and Nevis, M\/V, stern, precision munitions, blockade or disabled. Do not promote those CENTCOM extras onto this row. Distinct from dedicated Vieila on this same table, 5 November, IMO 9234654, 16NM east of Khasab. Distinct from dedicated 199-26, Sunday morning\u2019s unnamed tanker fire, 8 NM northwest of Khasab. Distinct from dedicated 200-26, Sunday morning\u2019s unnamed outbound Hormuz projectile, 2020 UTC 7 November. Do not fold Huda onto those later 7 November tanker clocks because the IMO date is also 7 November.<\/p>\n
The 130-to-131 conversion is the briefing fact. Monday midday\u2019s dedicated 130-count file printed 130 confirmed \/ 25 dead as at 6 November, with Vieila as the named top row. Tuesday morning\u2019s board prints 131 confirmed \/ 25 dead as at 9 November, with Huda as the named top row and Vieila as the second row. The as-at date moved. The fatality line did not move. A war-risk file that still treats IMO\u2019s public sheet as 130 with Vieila on top, as at 6 November, has under-read the current table. A master\u2019s pack that treats 198-26\u2019s unnamed bulk carrier as now closed because IMO said Huda has collapsed two instruments. Monday midday\u2019s dedicated file was right to refuse a 131st incident from a board that had not added one. Tuesday morning\u2019s dedicated file is the conversion, not a restatement of that refusal.<\/p>\n
This is not Advisory 198-26. Saturday night\u2019s dedicated UKMTO Advisory remains an unnamed military-authorities report, incident time TBC, bulk carrier and military forces, 18 nautical miles east of Khor Fakkan, crew \/ damage \/ environment unknown. IMO has taken a 7 November date, the hull, the IMO number, a 17-nautical-mile Oman-coast offset and the damaged\/no-pollution lines. It has not revised the PDF. Sunday night\u2019s companion Update 112 remains the first JMIC naming against that clock, wrap, not a PDF naming.<\/p>\n
This is not a 26th fatality, and it is not a Velos Sapphire rewrite. The fatality line is still 25, on Velos Sapphire, 4 November, 50NM north of Madinat ash Shamal, Qatar, damaged, no pollution, one seafarer fatality. Huda\u2019s row prints no casualty. Do not convert Damaged. No pollution. into a death. Do not brief Tuesday morning as \u201cIMO has now moved the fatality off Velos Sapphire.\u201d PETRO DOLPHIN remains two seafarers missing at Sohar Anchorage. EL GAIA remains two seafarers missing. MINOAN PIONEER remains one seafarer missing. Those earlier missing lines did not move the fatality count this morning.<\/p>\n
This is not Update 112, and it is not Update 113. Sunday night\u2019s dedicated JMIC note remains Update 112 to the advisory, 1 March\u20138 November 2026, ICOD 081300 UTC, JMIC# 001 26, regional threat SEVERE, 177 incidents since 1 March, printed correction that Update 110 should have read 166 not 167, five counted since last report including 198-26 as HUDA \/ Blockade Enforcement. That note named Huda against dedicated 198-26 and still withheld 197-26, 199-26 and 200-26. It did not print IMO 9197088. It did not print 17 NM from the coast of Oman. It did not print damaged, no pollution. No Update 113 was retrieved this run. Do not promote IMO\u2019s 131st incident onto Update 112 as a completed JMIC reprint. Do not invent an ICOD move that the JMIC PDF has not printed.<\/p>\n
This is not 199-26, 200-26 or 197-26. Sunday morning\u2019s dedicated 199-26 remains an unnamed tanker fire, Suspicious Activity, 8 NM northwest of Khasab. Sunday morning\u2019s dedicated 200-26 remains an unnamed tanker Attack, unknown projectile, outbound Hormuz, 2020 UTC 7 November, crew safe, no environmental impact on the PDF. Friday night\u2019s dedicated 197-26 remains an unnamed tanker Attack, waterline explosion port side, 16 NM east of Khasab, 2200 UTC 5 November, crew safe, own power. Monday midday\u2019s dedicated 130-count remains the first IMO print of Vieila against that 5 November Khasab offset. IMO has not named 200-26, 199-26 or 197-26 as new Tuesday rows. A DPA who briefs Tuesday morning as \u201cIMO has now named the northwest-of-Khasab fire\u201d or as \u201cIMO has now named the outbound Hormuz projectile\u201d has invented a row the sheet does not print. A 7 November date on Huda is not a 199-26 conversion and not a 200-26 conversion.<\/p>\n
This is not Vieila, and it is not a 5 November Khasab rewrite. Dedicated Vieila remains 5 November, IMO 9234654, 16NM east of Khasab, damaged, no pollution \u2014 Monday midday\u2019s 130th row, still the second row this morning. Huda remains 7 November, IMO 9197088, 17NM from the coast of Oman, damaged, no pollution. Two days and a different offset wording still separate those lines. Do not brief Tuesday morning as Vieila reprinted. Official wording still keeps VIEILA on that earlier row. Do not tidy it into Vieira on this sheet either.<\/p>\n
This is not 195-26, 194-26, 193-26, 192-26, 191-26, 425\/26 or Al Jusufi. Tuesday night\u2019s dedicated 195-26 remains an unnamed tanker, two unknown projectiles into the engine room, 14 NM northeast of Lima, no casualties printed on that PDF. Tuesday night\u2019s dedicated 194-26 remains an Indian-crewed dhow Attack outbound through Hormuz; Tuesday afternoon\u2019s dedicated Indian statements remain the Al Jusufi national-statement primary. Monday night\u2019s dedicated 193-26 remains an unnamed vessel, hole starboard, 9 NM northeast of Lima. Wednesday morning\u2019s dedicated 128-count remains the first IMO print of Largo Atom and Selat Storm. Sunday night\u2019s dedicated 191-26 remains an unnamed Mayday-relay Attack. Sunday night\u2019s dedicated 425\/26 remains tug Selat Storm sunk 0.6 NM west of Jazirat Um Al Ghanam. IMO\u2019s 131st incident is printed against Huda, not against those files. India\u2019s dedicated Al Jusufi fatality remains a national-statement death on a different clock and a different hull; it is still not a new IMO row this morning, and it is not the 25th line on this sheet.<\/p>\n
This is not last night\u2019s dedicated NAVAREA IX 434\/26, not last night\u2019s dedicated NAVWARN 815\/26, and not this morning\u2019s companion NAVWARN 1366\/26. 434\/26 remains the Northern Gulf \/ Kuwait bathymetric survey on six named hulls. 815\/26 remains the 10 November four-hour naval-exercise box south of Cape Kaliakra. 1366\/26 is this morning\u2019s other dedicated file: a two-day Elefsina \/ Skaragka parachute-jumping disc. None of those products belongs on this Middle East highlighted-incidents table. Official English 816\/26 and 817\/26 remain wrap on dedicated 815\/26. Official Cyprus 345\/26, NAVAREA III 0170\/26 and NAVAREA IX 433\/26 remain unused as dedicated. UKMTO still ends at dedicated 200-26 on the Attack line, dedicated 199-26 on the Suspicious Activity line, and dedicated 198-26 on the Advisory line. NAVAREA IX still lists dedicated 434\/26 as the first row atop unused 433\/26. No UKMTO 201-26, no Update 113, no IMO 132, no ARN 169, no 435\/26 and no official NAVWARN 818 this run.<\/p>\n
For a master still holding a Khor Fakkan east offset, a Gulf of Oman coastal passage, or a war-risk file opened against Saturday night\u2019s unnamed 198-26 PDF, Tuesday morning is a hull-naming problem before it is a new-attack problem. IMO has added a 131st confirmed incident. It has named Huda, IMO 9197088, 7 November, 17 nautical miles from the coast of Oman, damaged, no pollution, with an as-at date now of 9 November. Charterers and underwriters who copied Monday midday\u2019s \u201c130 confirmed, Vieila on top, as at 6 November, do not invent a 131st row\u201d language into Tuesday\u2019s pack now have an official naming on a new hull and a later as-at stamp. That is not a licence to treat 198-26 as closed. The PDF still withholds the name. Update 112 already named Huda against that clock as wrap, with a different offset and without IMO 9197088. IMO now prints Huda, 9197088, 17 NM from the Oman coast, damaged, no pollution. Carry all three lines. Do not brief a single \u201chull: Huda on 198-26.\u201d Do not brief a single \u201chull: unnamed.\u201d Write the instrument next to the finding.<\/p>\n
The ISM and war-risk split is the operational content a DPA has to get right. Monday midday\u2019s dedicated file told operators not to convert the 130-count into a 131st incident because the table had not done so, and not to treat Update 112\u2019s Huda naming as an IMO row. Tuesday morning\u2019s table has done the IMO conversion. A safety-management report that still says \u201cIMO: 130 confirmed, top row Vieila, as at 6 November\u201d is stale against the current sheet. A safety-management report that says \u201cUKMTO 198-26: Huda, IMO 9197088, damaged, no pollution, 17 NM from the Oman coast\u201d is over-read against a PDF that still withholds the hull, still prints 18 NM east of Khor Fakkan, and still prints damage unknown. Notify the CSO, the P&I correspondent and the war-risk underwriter that IMO\u2019s public highlighted-incidents board as at 9 November now reads 131 confirmed \/ 25 dead and that the new top row is HUDA, IMO 9197088, 7 November, 17NM from the coast of Oman, damaged, no pollution. Keep 198-26 on the unnamed-PDF sheet. Keep Update 112 on the JMIC Huda \/ Blockade Enforcement \/ 18 NM east of Khor Fakkan sheet. Do not merge the three into one closed casualty file without a PDF revision, a later JMIC update, or a flag-state statement this desk has not retrieved. Do not write a CENTCOM flag or a stern-munition line onto the IMO row because Update 112 sourced the identification to US CENTCOM. IMO printed HUDA, 9197088, damaged, no pollution.<\/p>\n
The unnamed remainder is unchanged and still matters. 200-26, 199-26, 197-26, 195-26, 194-26, 193-26 and 191-26 are still unnamed on this board as new rows. Al Jusufi is still a national-statement hull, not a new IMO row. AZINI and Quba are still unnamed here. A 114-to-119 increment is still unnamed. PETRO DOLPHIN, EL GAIA and MINOAN PIONEER still carry missing lines that have not moved the 25. A DPA who treats Tuesday morning as \u201cthe board is now complete through 9 November\u201d has ignored those gaps. A DPA who treats the 131st incident as Sunday morning\u2019s 199-26 fire or as Sunday morning\u2019s 200-26 projectile has borrowed a 7 November tanker clock and dropped Huda\u2019s 17-nautical-mile Oman-coast offset. A DPA who treats the as-at move from 6 November to 9 November as three new confirmed attacks has over-read a table that added one named row.<\/p>\n
Keep the dedicated files on their own lines. Monday midday\u2019s dedicated 130-count remains Vieila, as at 6 November, 130 confirmed \/ 25 dead. Friday afternoon\u2019s dedicated 25-fatality conversion remains Velos Sapphire, as at 6 November, 129 confirmed \/ 25 dead. Thursday night\u2019s dedicated 129-count remains the first IMO print of Velos Sapphire. Sunday night\u2019s dedicated Update 112 remains the JMIC 177-count \/ SEVERE note with Huda named against 198-26 and with 197-26, 199-26 and 200-26 withheld. Saturday night\u2019s dedicated 198-26 remains the unnamed Khor Fakkan bulk carrier. Friday night\u2019s dedicated 197-26 remains the unnamed Khasab tanker Attack. Sunday morning\u2019s dedicated 199-26 and 200-26 remain unnamed PDFs. Last night\u2019s dedicated 434\/26 remains the Kuwait bathymetric survey. Last night\u2019s dedicated 815\/26 remains the Kaliakra four-hour box. This morning\u2019s companion 1366\/26 remains the Elefsina parachute disc. Do not recast 10 November morning as a 198-26 PDF naming, as an Update 112 reprint, as a 26th fatality, or as a completed 7 November tanker tape.<\/p>\n
Regulas Shipping will keep lining Tuesday morning\u2019s IMO board as at 9 November \u2014 131 confirmed, 25 dead, Huda now the named top row \u2014 against Saturday night\u2019s unnamed 198-26 PDF and against Sunday night\u2019s Update 112 Huda \/ Blockade Enforcement row so operators can treat the 131st incident as an IMO naming on a new hull, not as a UKMTO naming, a JMIC reprint, or a 26th fatality.<\/p>\n","protected":false},"excerpt":{"rendered":"
The International Maritime Organization\u2019s highlighted-incidents board, as at 9 November, now prints 131 confirmed incidents in the Strait of Hormuz and the wider Middle East, with 25 confirmed seafarer fatalities. Monday midday\u2019s dedicated conversion on this desk sat at 130 as at 6 November, with 25 dead, and with Vieila\u2019s 5 November row 16 nautical […]<\/p>\n","protected":false},"author":1,"featured_media":1299,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wpai_generated_summary":"","wpai_meta_description":"","footnotes":""},"categories":[26,18,4],"tags":[],"class_list":["post-1301","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-highlights","category-maritime-industry","category-maritime-security"],"_links":{"self":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1301","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/comments?post=1301"}],"version-history":[{"count":0,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1301\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1299"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1301"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1301"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1301"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}