# INVESTIGATION: GasLog Shanghai, the LNG carrier identified by cross-checking in the Strait of Hormuz


- Author: Maxime Marquette
- Publisher: MadMax (https://mad-max.co)
- Section: Investigation
- Published: 2026-08-01
- Canonical URL: https://mad-max.co/en/article/gaslog-shanghai-the-lng-carrier-identified-by-cross-checking-in-the-strait-of-hormuz

## A Qatari LNG carrier struck, identified by private security firms

### What the owning company confirmed itself

### A temporary blackout, a crew unharmed

According to **gCaptain**, **GasLog** confirmed that its **LNG** carrier **GasLog Shanghai** was involved in an incident on **July 31** while exiting the Strait of Hormuz. This direct confirmation from the owning company is the strongest piece of evidence in this file: it comes not from a third party or anonymous source, but from the entity that owns and operates the vessel itself. *A company confirming its own vessel leaves no room for doubt about its identity.*

Per **Moneycontrol**, the vessel was carrying a **cargo originating from Qatar** and was struck by a projectile, causing a **temporary blackout**. This technical detail — a brief power failure rather than a fire or major explosion — places the incident's severity within a specific range, neither trivial nor catastrophic based on available information.

### Vanguard Tech and Marisks, two security firms that cross-checked the identification

According to **Moneycontrol**, private maritime security firms **Vanguard Tech** and **Marisks** identified the vessel as the **GasLog Shanghai**. This cross-check, carried out by two entities independent of each other, ahead of GasLog's own official confirmation, illustrates the methodical identification work that preceded the final confirmation.

## Crew safe, vessel stable: what GasLog stated

### An emergency response plan activated quickly

According to **gCaptain**, the company stated that the entire **crew was safe**, that the vessel was **stable**, and that an **emergency response plan** had been activated. This rapid communication from the company, within hours of the incident, directly addresses the most immediate concern: the safety of those on board.

None of the sources reviewed for this file report any **injury or loss of life** tied to this specific incident, which sets this file apart from other, more severe episodes in the same region during the broader conflict. *An unharmed crew doesn't make the incident trivial — it only limits the worst-case scenario.*

### What "stable vessel" actually means

The statement that the vessel remains **stable** after impact suggests the hull did not suffer a breach compromising the **LNG** carrier's buoyancy, a crucial technical point for a vessel carrying **liquefied natural gas**, a cargo whose flammability imposes particularly strict safety standards.

## A witness eleven nautical miles away saw the explosion

### A third-party vessel's account, with no damage reported

According to the **New York Post**, a vessel flying a **Liberian flag**, located **eleven nautical miles** away, reported seeing a "**significant splash and an explosion**," with no damage recorded for that witness vessel itself. This indirect account, from a third party not directly involved in the incident, corroborates that a violent event occurred visibly at a distance, independent of the version provided by GasLog or the security firms.

That distance of **eleven nautical miles** — roughly twenty kilometers — gives a scale to the reported explosion's visibility: an event significant enough to be observed and reported at this distance deserves to be taken seriously, even absent any damage to the witness itself. *An explosion visible twenty kilometers away is never a minor incident.*

### What this third-party account does not confirm

This account alone does not confirm the exact origin of the projectile or the identity of whoever fired it. It confirms only that a visible, audible event genuinely occurred in this zone, at this precise moment, leaving the question of who actually fired it entirely open for now, as it honestly should remain.

## A Bermudian flag, a southern route, an AIS switched off

### What Al Mayadeen adds to the identification file

According to **Al Mayadeen**, the vessel identified as **GasLog Shanghai** was sailing under a **Bermudian flag** in the strait's southern shipping lane, and had switched off its **AIS** (automatic identification system) while transiting this route. This technical detail, if accurate, deserves to be noted without being automatically read as suspicious: many commercial vessels disable their **AIS** in high-risk zones precisely to avoid being targeted more easily.

This practice of **disabling AIS** in conflict zones, documented elsewhere in maritime security literature, paradoxically complicates independent vessel identification while aiming to protect ships from identification by hostile actors. *Going dark for protection also makes it harder to later prove you were exactly where you say you were.*

### A paradox of modern maritime security

This **paradox** — becoming invisible for protection, at the cost of complicating any later investigation — runs through all the maritime incidents in the Strait of Hormuz over recent months, according to the documentary context available for this file. Insurers and flag registries face the same tension: the safety logic that argues for silence is the same logic that later makes accountability harder to establish.

## An American evacuation warning, published the same day

### What American embassies recommended

According to the **Associated Press**, relayed by the **New York Post**, **American embassies in the Middle East** recommended that American citizens leave the region because of an **anticipated large-scale military operation**, led by the United States and Israel and aimed at **Iran**'s energy sector. This diplomatic warning, published the same day as the GasLog Shanghai incident, substantially raises the geopolitical stakes of this file beyond the maritime incident alone.

This account refrains from establishing a **direct, proven causal link** between this evacuation warning and the specific incident affecting the GasLog Shanghai: both pieces of information are reported by the same outlet on the same day, with nothing reviewed explicitly connecting them beyond that simultaneity. *Two pieces of news published the same day don't automatically tell the same story.*

### What this warning changes in how the file reads

This warning, if confirmed in the days following its publication, would place the GasLog Shanghai incident within a context of **maximum tension** rather than an isolated episode of disrupted commercial shipping.

## The link to the two UKMTO alerts remains, per gCaptain, unestablished

### What the British maritime security body reported separately

According to **gCaptain**, the British maritime security body **UKMTO** reported **two new attacks** in the same period, without the link between those alerts and the specific GasLog Shanghai incident being established by the source itself. This account scrupulously respects that methodological caveat expressed by gCaptain, rather than artificially merging this information into a single, coherent narrative that would exceed what the sources allow to be affirmed.

This documentary caution from gCaptain, a publication specialized in the commercial maritime sector, strengthens the credibility of its overall coverage: a source that explicitly acknowledges the limits of what it can confirm deserves more trust regarding what it does affirm. *A source that admits its limits earns more credibility for what it does claim.*

### Why this distinction between incidents matters

Treating each **UKMTO** alert as a potentially distinct event, rather than a simple repetition of the same incident, avoids artificially inflating the number of confirmed attacks in the Strait of Hormuz over this precise period.

## The UN had already named this cycle of deadly attacks in July

### An earlier condemnation that situates the incident within a continuity

A **UN** agency had published, earlier in **July 2026**, a statement condemning repeated **deadly attacks** in the Strait of Hormuz, under the explicit title "**Cycle of escalation must end**." This earlier condemnation, distinct from the specific GasLog Shanghai incident, documents an **international concern already expressed** before this particular episode occurred.

This account cites that earlier statement to situate the incident within a documented trajectory, without claiming it specifically concerns the July **31** attack on the GasLog Shanghai. The two elements remain **factually distinct**, even as they belong to the same zone of prolonged tension.

### What this documentary continuity does not erase

Each maritime incident in the Strait of Hormuz remains an event to be documented individually, with its own sources and its own degree of confirmation, even when it fits within a broader regional trend.

## An American precedent: a merchant vessel seized twice in a week

### What Centcom has documented in the past

The **American military command for the Middle East** published, during a separate, earlier episode, a statement documenting the seizure of a **second merchant vessel within a week** by **Iran**. This precedent, though not directly tied to the GasLog Shanghai incident, establishes a **documentary context** of recurring maritime incidents affecting commercial vessels in this precise region.

This historical parallel helps explain why the rapid, methodical identification of the GasLog Shanghai by several independent security firms is not an isolated exercise: it fits within a **now-routine practice** of cross-checking in response to recurring maritime incidents in the Strait of Hormuz. *A repeated identification exercise becomes a skill, not a coincidence.*

### A region where rapid identification has become an operational necessity

This recurrence of incidents has likely contributed to the development of **private maritime-tracking capabilities**, such as those used by Vanguard Tech and Marisks, capable of identifying a struck vessel within hours.

## A French-language precedent documented three weeks earlier

### La Presse already reported three vessels attacked in a single day

A leading Canadian French-language outlet documented, on **July 7, 2026**, a separate episode in which **three vessels** were attacked in a single day in the same broader region. This precedent, occurring nearly a month before the GasLog Shanghai incident, illustrates an **already-elevated frequency** of maritime incidents in this zone, well before the episode documented in this file.

This earlier documentation, from a first-hand French-language source, strengthens the diversity of documentary origins in this file, avoiding exclusive reliance on English-language sources or sources directly tied to parties involved in the region. *A month of documented history beats a sudden discovery with no context.*

### What this elevated frequency implies for reading the current file

If incidents of this nature have been occurring at a close pace for several weeks, the GasLog Shanghai episode fits within an **already well-established trend** rather than an isolated, unexpected event.

## Private security firms fill a gap governments don't always cover

### Faster identification than official diplomatic channels

The role played by **Vanguard Tech** and **Marisks** in this file illustrates a notable shift in the maritime security landscape: **specialized private firms** now handle a significant share of the identification and tracking work that official diplomatic or military channels don't always provide as quickly.

This account has no information on the **exact methodology** used by these two firms to identify the GasLog Shanghai — satellite imagery, historical **AIS** data, private maritime intelligence networks. This lack of methodological detail does not invalidate their identification, independently confirmed by GasLog itself, but it limits this file's ability to assess the general reliability of their methods. *A confirmed identification doesn't need to reveal its method to be credible.*

### What this shift reveals about modern maritime security

This rise of specialized private actors in maritime tracking reflects a **growing demand** from **insurance companies**, shipowners, and charterers for fast, reliable information in zones of prolonged tension like the Strait of Hormuz, where waiting for an official government confirmation can cost hours that a shipping schedule or an insurance claim cannot always absorb.

## The attacker remains, at this stage, unidentified

### No claim directly tied to the GasLog Shanghai in the sources reviewed

Unlike the file devoted to the two tankers claimed by the **IRGC** on July **31**, none of the sources reviewed for this specific file report any **direct, named claim** regarding the attack on the GasLog Shanghai. This account avoids drawing an automatic link between the two files, despite their temporal and geographic proximity.

This absence of a named claim sets this file apart from the tanker file, where the **IRGC** had explicitly communicated about its action. Here, the exact origin of the **projectile** mentioned by Moneycontrol remains, at this stage, unattributed by any source reviewed for this specific investigation. *An attack without a named claim is still an attack, but not yet an established responsibility.*

### Why this distinction between the two files must be maintained

Merging these two distinct files — the tankers claimed by the **IRGC** and the GasLog Shanghai **LNG** carrier — would produce an inaccurate reading that would lend this second incident an attribution the sources do not allow to be established. *Two distinct files deserve two distinct attributions.*

## Assembling fragments rather than imposing a linear narrative

### An investigative method built on cross-checking, not storytelling

The method structuring this file relies on **assembling fragments** from distinct, independent sources — an owning company, two private security firms, a third-party witness, a news agency relaying a government statement — rather than a single linear narrative that would erase the real uncertainties between these different pieces.

This **cross-checking approach** reflects the very nature of the material available for this file: fragmentary, sometimes indirect, requiring careful assembly rather than being told as if each element naturally followed the last. *A body of fragmentary evidence beats a smooth but invented narrative.*

### What this method requires from readers

Readers of this file must accept reconstructing part of the overall **coherence** themselves, rather than receiving a fully pre-built story that would hide the real **blind spots** of this investigation. That extra effort is the price of an account that refuses to manufacture certainty where the record itself offers only convergence.

## An owned limit on the conflict's outcome, without projection

### No projection on the future of maritime security in the strait

This account makes **no projection** on the future evolution of maritime security in the Strait of Hormuz beyond the time of writing. The sources reviewed document a specific incident and its immediate context, not a verifiable future timeline for the entire region.

Likewise, no **precise intent** is attributed to any particular state actor beyond what the sources explicitly allow to be established about this specific incident. The evacuation warning reported by the New York Post remains documented as is, with no further extrapolation. *Documenting a warning doesn't require guessing at the war it might herald.*

### The presumption of caution governing this investigation

Facing a maritime incident in a zone of **active military tension**, this text consistently favors attributed phrasing and **named sources**, in keeping with the rigor this kind of investigation demands.

## The silence over the projectile's origin remains the missing piece

### A missing piece this text names rather than fills

The absence of a **named attribution** for the projectile that struck the GasLog Shanghai is the most significant missing piece in this investigation. This account chooses to explicitly name this gap rather than fill it with a guess tied to no verified source for this specific file.

This absence in no way diminishes the solidity of the other established elements: the vessel's identity, the nature of the cargo, the condition of the crew and vessel, and the heightened geopolitical context documented the same day by the American evacuation warning. *A missing piece doesn't make the other pieces any less solid.*

### Why this methodological honesty matters especially here

In an investigation built on assembling **fragments** from multiple sources, naming precisely what remains unestablished is as important as documenting what is confirmed. A file that only lists what it knows, without naming what it doesn't, quietly misleads readers into assuming more certainty than the sources actually provide.

## What the GasLog Shanghai says about the vulnerability of gas flows

### A shipping incident turned into concrete proof

The identification of the **GasLog Shanghai**, cross-checked by several independent sources and private maritime tracking data, turns a shipping incident into **concrete proof** of the vulnerability of gas flows through the Strait of Hormuz. This is no longer an abstract military claim: it is a named **LNG** carrier, a company that confirms, security firms that cross-check, and a third-party witness who corroborates an explosion visible twenty kilometers away. *A named vessel carries more weight than an anonymous claim.*

This file documents what the sources allow to be established with an unusual level of cross-checking for this type of maritime incident: the vessel's identity, the nature of its cargo, the condition of its crew, and the tense geopolitical context surrounding this precise day of August **1, 2026**. What remains absent — the named attribution of the attack — is not hidden, but named as this investigation's honest limit.

### The question this file leaves for readers

How many more **LNG** carriers will need to be identified through cross-checking before the security of this shipping route stops depending on the work of **private companies** rather than a stable international guarantee? Nothing in the record assembled here suggests that shift is coming soon, and this account resists pretending otherwise for the sake of a tidier ending.

**By Maxime Marquette, columnist**

## Columnist's transparency note

### Editorial stance

I am not a journalist but a **columnist and analyst**. My expertise lies in observing and analysing the geopolitical, economic and strategic dynamics that shape our world. My work is to take political strategies apart, to understand global economic movements, to put the decisions of international actors in context and to offer analytical perspectives on the changes that are redefining our societies.

I do not claim the cold objectivity of traditional journalism, which stops at reporting facts. **I claim analytical clarity**, rigorous interpretation and a deep understanding of the complex issues that concern us all. My role is to give meaning to the facts, to place them in their historical and strategic context, and to offer a critical reading of events.

### Method and sources

This text keeps the basic distinction between **verified facts and interpretive analysis**. The rule never changes: a factual claim is published only when a verifiable source supports it, and the sources this article actually used are listed under **Sources**, never here.

**Primary source families** used by the publication, when the story has them: official statements from governments and international institutions, public statements by political leaders, reports from intergovernmental organisations, dispatches from recognised international news agencies.

**Secondary source families**: specialised publications, internationally recognised news media, analyses from established research institutions, reports from industry organisations.

When an article cites statistical, economic or geopolitical data, it comes from the institutions that produce it (intergovernmental organisations, central banks, national statistics offices), and the exact institution is named under **Sources**.

### Nature of the analysis

The analyses, interpretations and perspectives in the analytical sections of this article are a **critical, contextual synthesis** based on the information available, the trends observed and the expert comments cited in the sources consulted.

My role is to interpret these facts, to set them in the context of today's geopolitical and economic dynamics, and to give them a coherent meaning within the larger story of the changes shaping our time. These analyses reflect expertise built through continuous observation of international affairs and an understanding of the strategic mechanisms that drive global actors.

This article describes a documented state of affairs on its publication date, not a prediction: later developments may shift its outlook. No update is promised in advance; when an article is corrected or completed, the change is dated in the text.

## Sources

### Primary sources

- [UN News — 'Cycle of escalation must end': UN condemns deadly Strait of Hormuz attacks](https://news.un.org/en/story/2026/07/1167936)

- [US Central Command — U.S. Strikes Iran in Response to Attack on Commercial Vessel](https://www.centcom.mil/MEDIA/PUBLIC-RELEASES/Article/4528341/us-strikes-iran-in-response-to-attack-on-commercial-vessel/)

### Secondary sources

- [gCaptain — GasLog LNG Carrier Damaged Exiting Hormuz as UKMTO Reports Two New Attacks](https://gcaptain.com/gaslog-lng-carrier-damaged-exiting-hormuz-as-ukmto-reports-two-new-attacks/)

- [Moneycontrol — Tanker carrying Qatari LNG struck while transiting Strait of Hormuz](https://www.moneycontrol.com/news/business/tanker-carrying-qatari-lng-struck-while-transiting-strait-of-hormuz-13990983.html)

- [New York Post — Tanker carrying natural gas through Strait of Hormuz attacked — as Americans urged to leave Middle East](https://nypost.com/2026/08/01/world-news/tanker-carrying-natural-gas-through-strait-of-hormuz-struck-by-missile-overnight-report/)

- [Al Mayadeen — LNG carrier carrying Qatari Gas struck near Strait of Hormuz](https://english.almayadeen.net/news/politics/lng-carrier-carrying-qatari-gas-struck-near-strait-of-hormuz)

- [La Presse — Trois navires attaqués en une journée](https://www.lapresse.ca/international/moyen-orient/2026-07-07/detroit-d-ormuz/trois-navires-attaques-en-une-journee.php)

---

Source: Maxime Marquette, MadMax. When citing, name the author and link https://mad-max.co/en/article/gaslog-shanghai-the-lng-carrier-identified-by-cross-checking-in-the-strait-of-hormuz