Treasury
3-MO 3.83% +1bp 6-MO 3.98% unch 1-YR 4.08% +4bp 2-YR 4.28% +5bp 3-YR 4.34% +4bp 5-YR 4.45% +7bp 7-YR 4.59% +7bp 10-YR 4.75% +7bp 20-YR 5.28% +6bp 30-YR 5.27% +6bp 3-MO 3.83% +1bp 6-MO 3.98% unch 1-YR 4.08% +4bp 2-YR 4.28% +5bp 3-YR 4.34% +4bp 5-YR 4.45% +7bp 7-YR 4.59% +7bp 10-YR 4.75% +7bp 20-YR 5.28% +6bp 30-YR 5.27% +6bp 3-MO 3.83% +1bp 6-MO 3.98% unch 1-YR 4.08% +4bp 2-YR 4.28% +5bp 3-YR 4.34% +4bp 5-YR 4.45% +7bp 7-YR 4.59% +7bp 10-YR 4.75% +7bp 20-YR 5.28% +6bp 30-YR 5.27% +6bp 3-MO 3.83% +1bp 6-MO 3.98% unch 1-YR 4.08% +4bp 2-YR 4.28% +5bp 3-YR 4.34% +4bp 5-YR 4.45% +7bp 7-YR 4.59% +7bp 10-YR 4.75% +7bp 20-YR 5.28% +6bp 30-YR 5.27% +6bp 3-MO 3.83% +1bp 6-MO 3.98% unch 1-YR 4.08% +4bp 2-YR 4.28% +5bp 3-YR 4.34% +4bp 5-YR 4.45% +7bp 7-YR 4.59% +7bp 10-YR 4.75% +7bp 20-YR 5.28% +6bp 30-YR 5.27% +6bp 3-MO 3.83% +1bp 6-MO 3.98% unch 1-YR 4.08% +4bp 2-YR 4.28% +5bp 3-YR 4.34% +4bp 5-YR 4.45% +7bp 7-YR 4.59% +7bp 10-YR 4.75% +7bp 20-YR 5.28% +6bp 30-YR 5.27% +6bp
US Treasury par yield curve · Jul 31 · Source: U.S. Treasury
Sunday, August 2, 2026
U.S. Edition
Hormuz

The Hormuz incident log recorded its first attacks in eleven days on the night of 31 July, and GasLog broke a silence running back to 2024 to post statements on two of its ships

A close photograph of a dark green succulent rosette filling most of the frame, its pointed leaves spiralling outward in even rings from a tight centre, each leaf tipped and edged in deep red and fringed with fine pale hairs along its margin. Further rosettes sit in deep shadow to the right. No text, lettering, brand mark, person, vessel or place is in view.
Photo: Wyxina Tresse / Pexels

Two entries now sit above warning 098-26.

Until the night of 31 July, the newest item on the incident list kept by United Kingdom Maritime Trade Operations was an advisory dated 27 July, describing a master who heard an explosion while transiting the southern Red Sea. This site read that list on 30 July, counted 22 reports, and wrote that an empty log is not the same thing as an empty sea. Read again on Sunday morning, it states 24.

Both of the new entries are classed as attacks.

Warning 102-26 gives an incident time of 2206 UTC on 31 July and a position 21 nautical miles northeast of Khasab, Oman. The master of a tanker reported seeing a large splash and an explosion close to the ship, and no damage. Warning 101-26 carries a report time of 2330 UTC the same night, an issue date of 1 August, and a company security officer as its source: a tanker 11 nautical miles northeast off Lima, Oman, struck by an unknown projectile, damage to the engine room, the vessel not under command, the regional coast guard informed. Neither report describes casualties or pollution.

The earlier incident carries the later number.

Before these two, the last attack logged anywhere was warning 095-26 on 22 July, off Saudi Arabia in the Red Sea. The last one logged in the Hormuz approaches was 094-26 on 20 July, 8 nautical miles northeast of Limah, the same Omani village that 101-26 spells Lima. That is a gap of eleven days.

The operator posted twice on one day

On 1 August GasLog Ltd published two statements. One says an incident occurred on 31 July on the LNG carrier GasLog Shanghai while the vessel was exiting the Strait of Hormuz, that everyone onboard "is safe and accounted for," and that the vessel "is stable." The other says an incident occurred on 29 July on board the GasLog Salem while that ship was alongside at Damietta, in Egypt, that "all crew members are safe," and that there were no injuries and no pollution.

Neither statement says what happened. Neither uses the word attack. Both record that the company activated its emergency procedures and notified the authorities, and the Salem statement adds that the cause is being investigated. The item below them on that news page is dated 21 October 2024.

Reported by Mike Schuler at gCaptain, the Shanghai is a 155,000 cubic metre carrier built in 2013 and on bareboat charter to GasLog. That account covers the Shanghai and both UKMTO warnings, and states that whether the Shanghai incident is connected to either of them was not immediately clear. It does not mention the Salem.

Nothing here closes that gap. GasLog puts the Shanghai in the Strait of Hormuz on 31 July, and UKMTO puts two tankers off northern Oman the same night, which is an agreement about place and date rather than an identification. UKMTO names no vessel in either warning, as it never does.

Two things the record does not explain

The numbering runs unbroken from 077-26 on 1 July to 098-26 on 27 July, and then goes to 101 and 102. No entry numbered 099-26 or 100-26 appears, and the page gives no reason.

The second is the question this site set on 30 July, and it stays open. The test then was whether reports would resume before traffic returned to the strait or after, because the first would say something about intent and the second only about how few ships were there to file one. Settling it needs a current count of transits, and this desk did not obtain one today from a source it could cite.

Where we read it: Mike Schuler at gCaptain. Read their story.

The document: United Kingdom Maritime Trade Operations, Recent Incidents, read in full in the in-app browser on 2 August 2026 at approximately 10.15 a.m. Eastern. Access note, unchanged from this site's 30 July reading and worth repeating because the failure is silent: the page is a mapping application, and a plain command line fetch returns HTTP 200 together with a page reading zero reports, which looks exactly like an authority with nothing to say. It is not. Opened in a browser the same URL renders the full numbered list. The page stated '24 reports', against 22 when this desk read it on 30 July. The two new entries were transcribed in full and no fetch-tool summary was relied on for either. As verified, entry headed 'Attack UKMTO #102', page dated 1 August 2026: 'UKMTO WARNING 102-26 ATTACK Incident Date: 31 Jul 2026 Incident Time 2206UTC UKMTO has received a report of an incident 21NM northeast of Khasab, Oman. The Master of a tanker reports seeing a large splash and explosion in close proximity to the vessel. No damage to the vessel has been reported at this time. Authorities are investigating.' As verified, entry headed 'Attack UKMTO #101', page dated 31 July 2026: 'UKMTO WARNING 101-26 - ATTACK Report Date:31 Jul 2026 Report Time: 2330UTC Issue Date: 01 Aug 2026 Source Company Security Officer UKMTO has received a report of an incident 11NM northeast off Lima, Oman. The CSO of a tanker reports the vessel has been struck by an unknown projectile which has caused damage to the engine room. The tanker is not under command and the regional Coast Guard have been informed. There are no reported casualties or environmental impact. Authorities are investigating.' The prior newest entry was advisory 098-26 of 27 July, southern Red Sea. The prior newest entry classed as an attack anywhere on the list was 095-26 of 22 July, 70NM southwest of Al Shuqaiq, Saudi Arabia. The prior newest attack in the Hormuz approaches was 094-26 of 20 July, 8NM northeast of Limah, Oman. The numbering as it appears on the page runs 077 through 098 without a gap and then jumps to 101 and 102; no entry numbered 099-26 or 100-26 appears, and the page states no reason. Entry 101-26 spells the Omani village 'Lima' where entries 080-26, 086-26, 087-26 and 094-26 spell it 'Limah'. Neither new warning names a vessel, an operator or a flag. Second and third primary documents, both read in full at https://www.gaslogltd.com/statement-regarding-the-incident-on-gaslog-shanghai/ and https://www.gaslogltd.com/statement-regarding-the-incident-on-gaslog-salem/, listed on GasLog Ltd's investor news index at https://www.gaslogltd.com/investors/news/ as 'General | 2026-08-01 Statement Regarding the Incident on GasLog Shanghai' and 'Other news | 2026-08-01 Statement Regarding the Incident on GasLog Salem'. Shanghai statement, verbatim: 'On 31 July 2026, an incident occurred on our LNG vessel GASLOG SHANGHAI while exiting the Strait of Hormuz. Everyone onboard is safe and accounted for and the vessel is stable. GasLog LNG services immediately activated their emergency plan, notified all relevant authorities and currently assessing the condition of the vessel and assure the safety of our people.' Salem statement, verbatim in relevant part: 'On 29 July 2026, an incident occurred on board our LNG vessel GasLog Salem while the vessel was alongside in Damietta, Egypt. Our immediate priority was, and continues to be, the safety and wellbeing of our people. We are pleased to confirm that all crew members are safe. There were no injuries and no pollution resulting from the incident. The situation was brought under control promptly through the professionalism and preparedness of our crew. GasLog immediately activated its emergency response procedures, notified the relevant authorities, and continues to work closely with them as the cause of the incident is investigated.' Neither statement states a cause and neither uses the word attack. The item immediately below the two on that news index is dated 2024-10-21 and headed 'GIC to Acquire BlackRock's Shareholding in GasLog Ltd.' The credited gCaptain report by Mike Schuler, datePublished 2026-08-01T13:20:01+00:00 in the page's own structured data, supplies the vessel particulars used here, 155,000 cbm and built 2013 and on bareboat charter to GasLog, and states that it was not immediately clear whether the GasLog Shanghai incident is connected to either of the UKMTO reports. It does not mention the GasLog Salem. Two further routes were tried and are recorded here as holes rather than as findings. The Egyptian Ministry of Petroleum and Mineral Resources news index at petroleum.gov.eg returns HTTP 200 and is a JavaScript application that yields no article text to curl, so no Egyptian government statement on Damietta was read for this brief. And gCaptain's account of traffic through the strait carries author '@id' https://gcaptain.com/author/bloomberg/ in its structured data, making it a syndication of a blocked outlet rather than independent reporting, so it was not used and no transit or price figure appears in this brief..