{"id":1175,"date":"2026-11-01T23:37:15","date_gmt":"2026-11-01T23:37:15","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-191-26-records-a-mayday-relayed-hormuz-projectile-hit\/"},"modified":"2026-11-01T23:37:15","modified_gmt":"2026-11-01T23:37:15","slug":"ukmto-191-26-records-a-mayday-relayed-hormuz-projectile-hit","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-191-26-records-a-mayday-relayed-hormuz-projectile-hit\/","title":{"rendered":"UKMTO 191-26 records a Mayday-relayed Hormuz projectile hit"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre published Warning 191-26 as a numbered PDF on its product board, filename 20261101-ukmto_warning_191_26.pdf<\/code>. The face of the product is titled 191-26 \u2014 ATTACK. The incident date is 1 November 2026. The incident time is 1509 UTC. The source line is Merchant Vessel. UKMTO states that it has received a report of an incident within the Strait of Hormuz. The Master of a merchant vessel has relayed a Mayday call from VHF Channel 16, stating that another vessel has been struck by an unknown projectile. Vessels are advised to transit with caution and report any suspicious activity to UKMTO, whilst authorities investigate. The location footer printed on the product is Strait of Hormuz. Emergency contacts printed on the product remain watchkeepers@ukmto.org, +44 (0)2392 222060, +44 (0)7779 966976 and +44 (0)7585 795608.<\/p>\n

That is the working primary. Sunday night\u2019s product is a same-day Attack on a Channel 16 Mayday-relay clock, not a rewrite of this afternoon\u2019s dedicated Update 110, not a late naming of unused 186-26, and not a conversion of dedicated 189-26, 188-26 or 187-26 onto a Sunday afternoon hull. It does not name a merchant hull, an IMO number, a flag, a vessel type, a cargo, an attacker, a fire, a NUC or tow line, an inbound or outbound direction, a latitude\/longitude, or a keep-clear radius. This afternoon\u2019s dedicated JMIC Update 110 piece on this desk, retrieved as jmic_advisory_update_110_01-nov-1.pdf<\/code>, still told operators that the last numbered periodic note closed at ICOD 011300 UTC on 1 November and that its newest Attack rows were 186-26 \/ RITI, 187-26 \/ Louise 1, 188-26 \/ Al Mayeda and 189-26 \/ Arzanah. 191-26 was not on that note. The 1509 UTC Mayday sits two hours after that cut-off. Masters who brief Sunday night as Update 111, as Arzanah hit again, as RITI leaving Ra\u2019s Tahir, as unused 186-26 finally reprinted, or as a named Sunday casualty will have merged four other series into a third-party relay that withholds the struck hull.<\/p>\n

What the warning actually printed<\/h2>\n

The confirmed tape is the body of 191-26. UKMTO has received a report of an incident within the Strait of Hormuz. The Master of a merchant vessel has relayed a Mayday call from VHF Channel 16, stating that another vessel has been struck by an unknown projectile. Vessels are advised to transit with caution and report any suspicious activity to UKMTO, whilst authorities investigate. That is the product. Stay with that wording. Do not invent a hull. Do not invent a flag. Do not invent a tanker, VLCC, LPG or LNG type. The PDF prints \u201canother vessel,\u201d not crude oil tanker and not LNG carrier. Do not invent a UAV, a mine, a small-boat device or a boarding. Do not invent a lat\/long on the UKMTO PDF. 191-26 does not print one. Do not invent a keep-clear radius around Musandam, Khasab, Limah or Lavan. The PDF does not print one. Do not invent a crew-safe line, a fire-extinguished line, a lost-propulsion line, or a no-environmental-impact line. Those sentences sit on Update 110\u2019s named rows. They do not sit on 191-26.<\/p>\n

The product type is the first briefing fact. 191-26 is Attack, the same family that ran dedicated 179-26 through 182-26, unused 186-26, dedicated 187-26, dedicated 188-26 and dedicated 189-26, not the Suspicious Activity family that ran 183-26, 185-26 and 190-26, and not the Advisory family that ran 184-26. UKMTO says an unknown projectile struck another vessel inside the Strait of Hormuz. It does not say a small boat attached devices. It does not say a mine in the water. It does not say a UAV. It does not say the ship is at anchor, NUC, under tow, sunk, on fire, or continuing to the next port of call. A DPA who briefs Sunday night as \u201canother Hormuz attached-device hit, crew safe\u201d has borrowed 187-26\u2019s method and Update 110\u2019s Louise 1 all-clear and has dropped the Mayday-relay clock that is the whole of this PDF. A DPA who briefs Sunday night as a completed salvage because Update 110 printed crew-safe lines on four earlier hulls has under-read a numbered Attack that still withholds crew, fire, type and onward status.<\/p>\n

Merchant Vessel, Mayday and VHF Channel 16 is the second briefing fact. The report sits on a third-party Master who relayed someone else\u2019s distress, not on a Verified source, not on a CSO of the casualty, and not on the Master of the struck ship. Channel 16, the UKMTO emergency line and the company duty officer still have to be on the night orders for any hull working the Strait, the southern Omani corridor, or the approaches to Fujairah and Khor Fakkan. Do not treat \u201cMerchant Vessel\u201d as a hull naming. Do not treat \u201cMayday\u201d as a confirmed fire, flooding or abandonment. Do not treat the missing crew and pollution lines as a clean bunker survey. The public PDF does not say whether the struck ship is still making way, whether propulsion is available, whether the relaying Master stayed in company, or where either ship went after 1509 UTC.<\/p>\n

The geography is the third briefing fact. 191-26 prints Strait of Hormuz. It does not print Khasab, Limah, Bukha, Ra\u2019s Tahir, Lavan Island, Musandam, inbound, outbound, or a TSS waypoint. This afternoon\u2019s dedicated Update 110 remains a 011300 UTC periodic note whose newest Hormuz Attacks sit on 28\u201329 October clocks. Friday night\u2019s dedicated 188-26 remains an Arabian Gulf Attack 40 nautical miles south of Lavan Island, now named Al Mayeda on Update 110 as wrap. Friday morning\u2019s dedicated 187-26 remains a Hormuz Attack 25 nautical miles northeast of Khasab, now named Louise 1 on Update 110 as wrap. Thursday afternoon\u2019s unused 186-26 remains a CSO Hormuz Attack with a Khasab footer, now named RITI on Update 110 as wrap against dedicated 420\/26. Saturday morning\u2019s dedicated 189-26 remains a time-late 28 October outbound Attack, now named Arzanah on Update 110 as wrap. 191-26 is a Sunday 1509 UTC Hormuz Attack. It is not a reprint of those four rows. Update 110 still prints the Strait of Hormuz SEVERE and the Arabian Gulf SUBSTANTIAL. A passage plan that only carried this afternoon\u2019s named table, or that treated Sunday as empty because the periodic note closed at 011300 UTC, has not budgeted a Channel 16 Mayday two hours later.<\/p>\n

Industry colour of the same clock, held separately: Middle East Eye restated the UKMTO Sunday projectile sentence and the third-party Master relay. Monitor the Situation restated the same PDF as a merchant vessel struck in the Strait of Hormuz. Those reprints are not a naming. Treat them as industry colour of the public PDF. Do not collapse them onto 191-26 as a completed identification, a TSS plot, a crew-status line, or a conversion onto Arzanah, RITI, Louise 1 or Al Mayeda.<\/p>\n

What this is not<\/h2>\n

This is not Update 110, and it is not a seventh row on that note. This afternoon\u2019s dedicated Update 110, ICOD 011300 UTC 1 November, JMIC# 001 26, remains the last numbered public periodic note, with Hormuz SEVERE, the Arabian Gulf SUBSTANTIAL, 167 incidents since 1 March, and six files since Update 109. Its confirmed-incidents table ends at 186-26 \/ RITI, 187-26 \/ Louise 1, 188-26 \/ Al Mayeda, 189-26 \/ Arzanah, MSCIO 160\/26 and 161\/26 \/ 190-26 \/ AZINI. 191-26 at 1509 UTC sits after that cut-off. It is not a completed Update 111. Do not back-fit a Sunday Mayday onto a 1300 UTC table. Do not treat Update 110\u2019s four named Attacks as the Sunday casualty.<\/p>\n

This is not a rewrite of 189-26, and it is not an Arzanah file. Saturday morning\u2019s dedicated Warning 189-26 remains a time-late unnamed crude-oil-tanker Attack, 28 October, time TBC, source Verified, outbound Hormuz, unknown projectile. Update 110 now prints ARZANAH against that file as a VLCC, identified by India\u2019s Minister of Ports, Shipping and Waterways, damaged, crew reported safe. That is a JMIC naming. It is not a UKMTO PDF revision. 189-26 is a Wednesday clock published Friday. 191-26 is a Sunday 1509 UTC Merchant Vessel Mayday. A VLCC damaged on 28 October is not \u201canother vessel\u201d struck this afternoon. Do not convert Arzanah onto 191-26 as a second hit, a late Update 001, or a completed class survey.<\/p>\n

This is not a rewrite of unused 186-26, and it is not NAVAREA IX 420\/26. Thursday afternoon\u2019s unused Warning 186-26 remains a CSO Attack: tanker struck by an unknown projectile at 1600 UTC 29 October whilst completing an outbound Hormuz transit, no reported injuries, no environmental impact report, location footer Khasab, Oman. Dedicated 420\/26, issued 300300 UTC 30 October, names oil tanker RITI, security incident causing fire onboard, anchored in 26-24.07N 056-24.72E, approximately 1 nautical mile northwest of Ra\u2019s Tahir. Update 110 now prints RITI against 186-26 and 420\/26 as one Attack row: unknown projectile outbound IVO Khasab, small fire extinguished, lost propulsion, crew safe, no environmental impact, anchored about 1 nautical mile northwest of Ra\u2019s Tahir, identified by the Royal Navy of Oman. That is this afternoon\u2019s wrap. It is not a Sunday Mayday. 186-26 is 29 October. 191-26 is 1 November. 186-26 is CSO. 191-26 is Merchant Vessel. 191-26 prints no name, no fire, no propulsion line and no anchorage. Do not convert RITI onto 191-26 as a UKMTO naming.<\/p>\n

This is not a rewrite of 188-26, and it is not this afternoon\u2019s Nakilat Al Mayeda file. Friday night\u2019s dedicated Warning 188-26 remains an unnamed vessel Attack, 1800 UTC 30 October, 40 nautical miles south of Lavan Island, unknown projectile on the port side, fire onboard, crew reported safe. This afternoon\u2019s dedicated Nakilat \/ Qatar Stock Exchange disclosure remains the company statement that Al Mayeda was hit by unidentified objects in the Arabian Gulf on Friday evening, crew uninjured, no environmental impact, vessel safe and operational. Update 110 now prints AL MAYEDA against 188-26 as an LNG carrier, identified by India\u2019s Minister of Ports, Shipping and Waterways, projectiles about 40 nautical miles south of Lavan Island, fire, crew safe. Forty nautical miles south of Lavan is Arabian Gulf water. It is not a Strait of Hormuz Mayday. A Friday 1800 UTC Master report is not a Sunday 1509 UTC relay. Do not merge Friday\u2019s Gulf Attack onto Sunday\u2019s Hormuz Attack because both print unknown projectile.<\/p>\n

This is not a rewrite of 187-26, and it is not a Louise 1 file. Friday morning\u2019s dedicated Warning 187-26 remains an unnamed outbound tanker Attack, 2212 UTC 29 October, 25 nautical miles northeast of Khasab, port-side small boat, two explosive devices attached above the waterline, engine-room fire, temporarily disabled, fire extinguished, crew safe, no environmental impact, continuing to next port of call. Update 110 now prints LOUISE 1 against that file as a crude oil tanker, identified by India\u2019s Minister of Ports, Shipping and Waterways. Twenty-five nautical miles northeast of Khasab is not a Sunday Mayday plot. An attached-device method is not an unknown projectile. A continuing tanker with a crew-safe line is not \u201canother vessel\u201d whose type and status the PDF does not print. Do not merge Thursday night\u2019s Hormuz Attack onto this afternoon\u2019s relay because both print Attack.<\/p>\n

This is not 190-26, and it is not Sunday morning\u2019s dedicated AZINI hijack. Saturday night\u2019s dedicated Warning 190-26 remains a Suspicious Activity boarding of a large fishing vessel at 1419 UTC 30 October, PAG concern, no lat\/long on the public PDF. Sunday morning\u2019s dedicated MSCIO Alert 161\/26 remains the Iranian fishing vessel AZINI, hijacked 29 October off northeastern Somalia, last reported 09-47N 055-45E. Update 110 now prints AZINI against 161\/26 and 190-26 as wrap, boarded and taken east-southeast of Socotra, suspected Pirate Action Group. 191-26 prints a Strait of Hormuz Attack and an unknown projectile. A Somali-Basin fishing-vessel hijack is not a Sunday Hormuz Mayday. Do not merge the mothership watch onto this Attack because both sat on a late-October board.<\/p>\n

This is not an International Maritime Organization 123-count, and it is not Advisory 184-26. Saturday afternoon\u2019s dedicated IMO highlighted-incidents board remains 122 confirmed \/ 24 seafarer fatalities as at 30 October. Wednesday afternoon\u2019s dedicated JMIC Advisory Note 016-26 remains the blockade visit-and-search document pack. 184-26 \/ 416\/26 remains the Gulf of Aden PAG keep-clear through 032359 UTC 3 November. Thursday\u2019s dedicated Contship Jet and Khoryv Black Sea files, Saturday\u2019s dedicated NAVWARN 775\/26, 776\/26 and 777\/26, and Sunday morning\u2019s dedicated ARN 162\/2026 remain Kaliakra, Shabla, Burgas, Galata and Romanian products. They do not belong on a Hormuz Attack. NAVAREA IX 424\/26, the new 011500 UTC 1 November Pakistan live-weapon-firing box for 0300\u20130600 UTC on 3 and 4 November, is a separate Arabian Sea keep-clear and is unused as a dedicated file this run.<\/p>\n

Operational implications<\/h2>\n

For a master already shaping a Hormuz transit, or holding at Fujairah, Khor Fakkan, Sohar or the southern Omani corridor tonight, Sunday night is a same-day Attack on a Channel 16 Mayday clock, on top of this afternoon\u2019s Update 110 named table and on top of Friday night\u2019s 40-nautical-mile south-of-Lavan projectile. Update 110 remains the last numbered JMIC note and still prints Hormuz SEVERE. 016-26 remains the working blockade document pack for hulls that still need the Strait: continuous VHF 16, follow US forces, be prepared to alter, stop or come dead in the water, and have the six signed-or-stamped PDFs ready. 191-26 adds a merchant-vessel relay that another vessel was already hit inside the Strait two hours after that note closed. A passage plan that only carried Update 110\u2019s 011300 UTC cut-off, or that treated Sunday as quiet because the periodic table ended at Arzanah, has not budgeted a 1509 UTC Mayday.<\/p>\n

Unknown projectile on an unnamed vessel, learned from a third-party Mayday, is a standoff watchkeeping problem before it is a war-risk rewrite. 191-26 is not 187-26\u2019s alongside, slow-speed, above-waterline device problem. It is a lookout, CPA, AIS-on\/AIS-off, citadel and possible-disablement problem at the same time as it is a missing-damage-line problem. BMP MS projectile and citadel guidance remains the working industry pack; 191-26 does not reprint it and does not order an armed team. It also does not authorise a master to treat every radar contact in the Strait as a confirmed Attack, or to treat every AIS-on tanker as Arzanah, RITI or Louise 1 after the fact. Log the Warning number, the 1 November date, the 1509 UTC clock, the Merchant Vessel source line, the VHF Channel 16 Mayday-relay wording, the unknown-projectile method, and the Strait of Hormuz location footer. Do not log Arzanah, RITI, Louise 1, Al Mayeda, Ghana Prosperity, a small-boat device, a mine in the water, a Lavan offset, a crew-safe line, or an IRGC attribution that the PDF does not print.<\/p>\n

The missing type, crew, fire and pollution lines are the practical damage watch, not a completed all-clear. The public PDF says none of those things. It does not say whether the struck ship is making way, whether propulsion or steering is available, whether a tug was offered, whether the hull is holed, whether the relaying Master remained on scene, or where either ship went after 1509 UTC. Those missing lines are omissions. They are not a completed \u201call well,\u201d and they are not a NUC. Next-port authorities will want a written account that 191-26 does not contain. Charterers and war-risk underwriters will now ask whether the ship was in the Strait after 1509 UTC on 1 November, whether it heard the Mayday, whether it reported, and whether it was following Update 110 and 016-26. They will not be answered by this afternoon\u2019s named RITI, Louise 1, Al Mayeda or Arzanah rows, by Saturday\u2019s 122-count, or by Sunday morning\u2019s AZINI hijack.<\/p>\n

For a DPA and an operator with crude, products, LPG, LNG or any merchant hull still using the Strait, the reporting split is the operational content. Sightings of projectiles, fire, smoke, a disabled hull, a Mayday on Channel 16 or pollution go to UKMTO on the 191-26 action line and to the company security officer. NAVCENT NCAGS remains the 016-26 blockade mailbox for hulls that still need the Strait. MSCIO remains the EU ATALANTA registration and alert desk. Registering with one mailbox is not a substitute for the others. 191-26 does not order a daylight-only transit, a deviation around a published circle, or a halt to visit-and-search compliance. Keep Update 110 Hormuz SEVERE \/ Arabian Gulf SUBSTANTIAL and 016-26 visit-and-search in the master\u2019s pack. Watch a PDF revision that names a hull, prints a type, a lat\/long, a NUC, a tow, a fire or a crew line; a NAVAREA that plots this vessel rather than RITI or Quba; a flag or class note; a JMIC Update 111; or an IMO-board row \u2014 not a headline that Sunday afternoon\u2019s named table closed Sunday night\u2019s Mayday.<\/p>\n

Keep the dedicated files on their own lines. Update 110 remains this afternoon\u2019s numbered regional note, ICOD 011300 UTC, 167 incidents, Hormuz still SEVERE. 189-26 remains Saturday morning\u2019s unnamed time-late Hormuz Attack; Arzanah on Update 110 is wrap, not a 191-26 hull. 188-26 remains Friday night\u2019s unnamed vessel Attack 40 nautical miles south of Lavan Island; Al Mayeda on this afternoon\u2019s Nakilat statement and on Update 110 is wrap, not a Strait Mayday. 187-26 remains Friday morning\u2019s unnamed outbound-tanker Attack 25 nautical miles northeast of Khasab; Louise 1 on Update 110 is wrap. 186-26 remains the unused 1600 UTC unknown-projectile Attack; RITI on 420\/26 and on Update 110 is wrap. 190-26 remains Saturday night\u2019s unnamed fishing-vessel boarding; AZINI on 161\/26 and on Update 110 is wrap. 185-26 remains Thursday\u2019s 9-nautical-mile north-of-Khasab fire sighting. 184-26 \/ 416\/26 remains the Gulf of Aden PAG keep-clear through 3 November. 182-26 remains the 23 October outbound disablement, Ghana Prosperity on Update 109 and the IMO 122-count as wrap. 016-26 remains Wednesday afternoon\u2019s blockade document pack. NAVAREA IX 424\/26 remains the unused 3\u20134 November Pakistan firing box. Do not recast 1 November night as a named Sunday casualty, as Arzanah hit again, as unused 186-26 finally republished, as Update 111, as an IMO 123-count, or as a Strait closure.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log 191-26 as a Sunday Mayday-relayed Hormuz Attack, not as an Update 110 row and not as an Arzanah rewrite.<\/strong> UKMTO Warning 191-26, incident 1 November 2026, 1509 UTC, source Merchant Vessel. Filename 20261101-ukmto_warning_191_26.pdf<\/code>. Master of a merchant vessel relayed a VHF Channel 16 Mayday stating that another vessel had been struck by an unknown projectile. Strait of Hormuz. Transit with caution. Report suspicious activity to UKMTO, watchkeepers@ukmto.org \/ +44 (0)2392 222060. Authorities are investigating. UKMTO printed neither hull, IMO, flag, type, cargo, attacker, inbound or outbound, lat\/long, anchorage, NUC, tow, fire, crew status, environmental line, nor a keep-clear radius. This is not Update 110, not 189-26, not 188-26, not 187-26, not 186-26, and not 420\/26.<\/li>\n
  • Hold the clock and the water.<\/strong> 191-26 is Attack, not Suspicious Activity. The working date is 1 November. The working time is 1509 UTC. The working source is Merchant Vessel, not Verified, not CSO, and not the Master of the casualty. The working water is the Strait of Hormuz. The working method is an unknown projectile learned from a third-party Mayday. Do not brief Sunday night as \u201cUpdate 110\u2019s Arzanah row, filed late.\u201d Do not brief Sunday night as quiet because the PDF withholds type, crew and fire.<\/li>\n
  • Hold Middle East Eye \/ Monitor the Situation colour separately.<\/strong> Both restated the public PDF. Neither reprint named a hull, a flag or a cargo type. Do not promote a wire rewrite to a 191-26 naming, a TSS plot, or a crew line. Do not promote either reprint onto RITI, Louise 1, Al Mayeda or Arzanah.<\/li>\n
  • Do not collapse Update 110\u2019s named rows onto this number.<\/strong> Update 110 remains this afternoon\u2019s dedicated note, ICOD 011300 UTC, 167 incidents. 189-26 \/ Arzanah remains the dedicated time-late 28 October VLCC Attack. 188-26 \/ Al Mayeda remains the dedicated 1800 UTC LNG-carrier Attack 40 nautical miles south of Lavan Island. 187-26 \/ Louise 1 remains the dedicated 2212 UTC attached-device Attack 25 nautical miles northeast of Khasab. 186-26 \/ RITI remains the unused 1600 UTC 29 October CSO Attack, with 420\/26 as the Ra\u2019s Tahir fire-and-anchor. Four earlier products are four products. A Sunday Mayday is a fifth. Do not make them one hull.<\/li>\n
  • Do not merge this watch onto AZINI, Aden, Al-Faw, Ghana Prosperity or Quba.<\/strong> 190-26 \/ 161\/26 remains the dedicated fishing-vessel hijack, AZINI, east-southeast of Socotra. 184-26 \/ 416\/26 remains the Gulf of Aden PAG keep-clear through 3 November. 183-26 remains the 63-nautical-mile Al-Faw fire. 182-26 remains the outbound disablement, Ghana Prosperity on Update 109 as wrap only. 185-26 remains the 0300 UTC 9-nautical-mile north-of-Khasab fire. 417\/26 remains the dedicated MSV Quba sunk file. IMO still 122 \/ 24 as at 30 October. 016-26 remains the blockade document pack. 424\/26 remains the unused 3\u20134 November Pakistan firing box.<\/li>\n
  • Treat the missing type, crew, fire and onward-status lines as open damage lines.<\/strong> The public tape does not print a vessel type, a crew-safe sentence, a fire, a survey, a hole size, a NUC interval, a tug, a next-port name or a class note. Keep Update 110 Hormuz SEVERE \/ Arabian Gulf SUBSTANTIAL and 016-26 visit-and-search in the master\u2019s pack. Watch a PDF revision that names a hull or prints a type or lat\/long; a NAVAREA that plots this vessel; a flag or class note; a JMIC Update 111; or an IMO-board row \u2014 not a headline that this afternoon\u2019s named table closed Sunday\u2019s Mayday or completed a salvage.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 191-26 against this afternoon\u2019s dedicated Update 110 and against the named 186-26 through 189-26 rows so operators can treat Sunday night\u2019s tape as a numbered Channel 16 Mayday-relay Attack inside the Strait of Hormuz, not as an Arzanah rewrite, a RITI movement, or a completed class survey.<\/p>\n","protected":false},"excerpt":{"rendered":"

    The United Kingdom Maritime Trade Operations centre published Warning 191-26 as a numbered PDF on its product board, filename 20261101-ukmto_warning_191_26.pdf. The face of the product is titled 191-26 \u2014 ATTACK. The incident date is 1 November 2026. The incident time is 1509 UTC. The source line is Merchant Vessel. UKMTO states that it has received […]<\/p>\n","protected":false},"author":1,"featured_media":1173,"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-1175","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\/1175","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=1175"}],"version-history":[{"count":0,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1175\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1173"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1175"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1175"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}