Event · Strait of Hormuz

Iran says it seized a second US underwater drone

Sources through 24 Oct.

  • 27 Sep, in the strait

    Contested: Iran says it happened; the US military denies it.

    7 claims from 6 outlets say it happened; 1 disputes it.

GET https://sigb.ai/api/event/ev.hormuz.uuv-seizure.2026-09-27

{
  "schema": "sb.event.v1 (example shape)",
  "eventId": "ev.hormuz.uuv-seizure.2026-09-27",
  "eventIdState": "example — no producer gives events a lasting name yet",
  "subject": "hormuz",
  "firstSeen": "2026-09-27",
  "members": {
    "claims": 8,
    "saysItHappened": 7,
    "disputing": 1
  },
  "corroboration": {
    "state": "disputed"
  },
  "notMerged": [
    {
      "eventId": "ev.hormuz.uuv-capture.2026-09-08",
      "firstSeen": "2026-09-08",
      "claims": 6,
      "why": [
        "different-date",
        "different-object"
      ]
    }
  ],
  "groupingRule": "A claim joins the 8 Sep event if it names the Dive-LD drone or was first seen before 20 Sep; every other underwater-drone claim joins the 27 Sep event. A claim saying the seizure was denied or rejected is filed as disputing it.",
  "ledger": {
    "file": "lib/claims_hormuz.json",
    "schema": "sb.claims.v1",
    "computedAt": "2026-10-25T03:45:47+00:00"
  }
}

Example request: no event endpoint is live yet. The object is built from the same claims ledger rows this page shows.

GET https://sigb.ai/api/event/ev.hormuz.uuv-seizure.2026-09-27/where-from?expand=1

{
  "level": "event",
  "label": "Every report on this event",
  "children": [
    {
      "level": "reports",
      "label": "The IRGC has captured a new high-tech US underwater drone in less than a month, as Washington continues its bid to open the Strait of Hormuz, which Iran closed after the U.S. and Israel attacked the country in February. (Tehran Times)",
      "children": {
        "count": 1,
        "unfold": "expand=+1"
      }
    },
    {
      "level": "reports",
      "label": "Iran's Islamic Revolutionary Guard Corps (IRGC) Navy has claimed it seized a second US military underwater drone in the Strait of Hormuz. (Marine Insight)",
      "children": {
        "count": 1,
        "unfold": "expand=+1"
      }
    },
    {
      "level": "reports",
      "label": "Iran says it has captured another U.S. underwater drone in the Strait of Hormuz, with the seized REMUS 600 now under examination for its equipment and stored data. (Tehran Times)",
      "children": {
        "count": 1,
        "unfold": "expand=+1"
      }
    },
    {
      "level": "reports",
      "label": "Iran Guards claim capture of US underwater drone in Strait of Hormuz (Malay Mail)",
      "children": {
        "count": 1,
        "unfold": "expand=+1"
      }
    },
    {
      "level": "reports",
      "label": "Iran's Revolutionary Guards claim seizure of second US underwater drone in Strait of Hormuz (Euronews)",
      "children": {
        "count": 1,
        "unfold": "expand=+1"
      }
    },
    {
      "level": "reports",
      "label": "The Iranian Navy has intercepted a US Remus 600 autonomous underwater vehicle in the Strait of Hormuz, which is the second such US drone to be captured by the Iranian military, the army stated. (ITAR-TASS)",
      "children": {
        "count": 1,
        "unfold": "expand=+1"
      }
    },
    {
      "level": "reports",
      "label": "The IRGC says it captured a US Remus 600 autonomous underwater vehicle in the Strait of Hormuz. (Middle East Eye)",
      "children": {
        "count": 1,
        "unfold": "expand=+1"
      }
    },
    {
      "level": "reports",
      "label": "US rejects Iran’s claim of capturing underwater drone in Hormuz The US military has denied an Iranian claim that the Revolutionary Guard seized an advanced US underwater drone conducting surveillance in the Strait of Hormuz, Al Jazeera reported. (Middle East Eye)",
      "children": {
        "count": 1,
        "unfold": "expand=+1"
      }
    }
  ]
}

Example request, same rows. Each child unfolds one more level with expand=+1, down to the source link.

Walk the record from the Strait of Hormuz

Open where it comes from, follow a claim or a related name, and use the trail to come back. Every step says what it is, how it stands and when. Machines read the same record.

Strait of Hormuz

Situation.

Evidence
850 documents · 182 separate publishers · a match is coverage, not verification
Standing
A tracked situation; its record is kept up to date automatically from coverage
Time
first seen 24 May 2026, last seen 22 Oct 2026
Measured
51% of matching documents describe a specific action; the rest only mention it
As of
24 Oct 2026
4 links from here

What it is about (1)

Who and what is involved (2)

  • Irannamed by 2 separate outlets in its reports
  • United Statesnamed by 2 separate outlets in its reports

Related situations (1)

For machines: this record as JSON

Watch this

One event, one name

Reports join the event under one name. A similar event is kept apart, under its own name.

  • a report joins
  • a report that disputes it
The 27 Sep seizure8 claims joined · 1 dispute it
  1. 27 Sep
    First reports

    4 claims from 4 outlets: Malay Mail, Euronews, ITAR-TASS, Middle East Eye

  2. 27 Sep
    Disputes it

    US rejects Iran’s claim of capturing underwater drone in Hormuz The US military has denied an Iranian claim that the Revolutionary Guard seized an advanced US underwater drone conducting surveillance in the Strait of Hormuz, Al Jazeera reported.

  3. 28 Sep
    Joins

    Iran says it has captured another U.S. underwater drone in the Strait of Hormuz, with the seized REMUS 600 now under examination for its equipment and stored data.

  4. 29 Sep
    Joins

    Iran's Islamic Revolutionary Guard Corps (IRGC) Navy has claimed it seized a second US military underwater drone in the Strait of Hormuz.

  5. 1 Oct
    Joins

    The IRGC has captured a new high-tech US underwater drone in less than a month, as Washington continues its bid to open the Strait of Hormuz, which Iran closed after the U.S. and Israel attacked the country in February.

Not merged. Same kind of thing, same strait, same two countries. A different date, 19 days earlier. A different drone: a Dive-LD, against a REMUS 600. The 27 Sep reports call theirs the second.

The 8 Sep captureits own event · 6 claims
  1. 8 Sep
    First reports

    4 claims from 4 outlets: Al-Monitor, The Guardian, Middle East Eye, Tehran Times

  2. 9 Sep
    Joins

    2 claims from 2 outlets: Source, Tehran Times

Solid rail: the 27 Sep event. Dashed rail: the 8 Sep event, kept apart. Sharing the same parties does not make two reports one event.

Events are named by their date until they have a lasting name. How the claims are grouped: A claim joins the 8 Sep event if it names the Dive-LD drone or was first seen before 20 Sep; every other underwater-drone claim joins the 27 Sep event. A claim saying the seizure was denied or rejected is filed as disputing it.

Who reported it, who disputes it

Each list leads with the most recent report.

Says it happened

Iran’s Revolutionary Guards, as reported

Disputes it

The US military, as reported

  • 27 Sep

    US rejects Iran’s claim of capturing underwater drone in Hormuz The US military has denied an Iranian claim that the Revolutionary Guard seized an advanced US underwater drone conducting surveillance in the Strait of Hormuz, Al Jazeera reported.

    Middle East Eye

No first-hand source on file for either side: every report here comes from the press. The record read 4,373 press articles, 25 Aug to 25 Oct.

The 8 Sep event, kept apart

How the story moved

As of 25 Oct 2026, newest first: 7 claims say it happened. 3 of them keep the word “claim”, so the seizure stays Iran’s statement; the others report it as an act.

  1. 1 Oct

    Tehran Times “captured”

  2. 29 Sep

    Marine Insight “claimed” … “seized” · keeps “claim”

  3. 28 Sep

    Tehran Times “says” … “captured” … “seized”

  4. 27 Sep

    Malay Mail “claim” · keeps “claim”

  5. 27 Sep

    Euronews “claim” · keeps “claim”

  6. 27 Sep

    ITAR-TASS “intercepted” … “captured”

  7. 27 Sep

    Middle East Eye “says” … “captured”

What this rests on, and where it stops

This event is 14 sentences out of a Hormuz record of 2,984 sentences and 782 attributed statements, as of 25 Oct 2026. Grouped by the event they report, the record's 2,984 sentences make 1,853 events: 13 carried by three or more separate reports, 61 by two, and 1,779 by one. Another 968 sentences could not be placed in an event, so each is counted on its own reports. 11 older claims were retired and stay on file.

The maintained Hormuz record behind it joins 850 documents from 182 outlets, 9 Sep to 24 Oct. Sources through 24 Oct.

We count a story once, however many outlets reprint it.

How we count

What we read: 4,373 press articles, 25 Aug to 25 Oct.

  • Consensus measures reporting agreement, not reality — a uniformly repeated error passes any count.
  • Chains are collapsed by syndication tracing; residual shared-upstream risk remains.
  • Retroactive: computed 2026-10-25 over the archive, not tracked live.
  • Receipt gate: 74 extracted claim(s) excluded — no receipt whose own text supports the claim (the extractor's row binding is verified mechanically, never trusted).
  • Relative-anchor supersession: 2 claim(s) that described themselves as the most recent/last-known fact were retired because a claim from the SAME reporting thread, naming the same participants and the same measured quantity, describes a later instance of that subject — see 'retired'. Subject-matched, same-chain detection only: an anchor claim updated by a DIFFERENT outlet is not auto-retired, though its own firstSeen/lastSeen still render so a reader can judge its age.
  • Relative-anchor supersession: 9445 later same-thread claim(s) were NOT treated as replacing an anchored claim: 6597 are about different participants, a different measured quantity or a forecast, 2844 could not be read role for role or period for period, 0 compare against another time, 1 characterize or restate the same value and 3 report an earlier or the same period. A claim is replaced here only by a later report on the same participants and the same measured quantity, for a later period; every other pair keeps both claims standing.
  • Questions: 12 extracted sentence(s) were questions (a headline asking, e.g. "Trump asked on TruthSocial 'When are the Iranian people going to rise up and fight?'"), not assertions, and take no claim standing in any tier.
  • Literal-span counting (#1036): 485 extracted claim(s) were receipted by sentences that do not all assert the same proposition, and were split into 1143 separate claims, each counted only on the sources whose own sentence asserts it. Every count, disagreement and replacement here is decided on the sources' own words; the extractor's sentence is kept as a labelled paraphrase and decides nothing.
  • Domain-competence gate: 3386 kernel claim(s) and 441 frame(s) excluded — every supporting chain came from outlets confidently placed outside this subject's coverage domains (aerospace_defense, auto, energy, europe_politics, india_south_asia, iran_regime, …). An outlet counts as competent when its measured home beat intersects the domains the subject's own corpus lives in; outlets with too few observations are never branded and always count.
  • Semantic-dome membership: 9223 kernel claim(s) and 2199 frame(s) were source-faithful but failed typed-signature membership and are excluded — a claim enters this ledger only if its signature names a family entity (party, place, or authority) AND either its action class sits in the family's geopolitical profile or it names a family place outright.
  • An item is published only when it is RECEIPTED: the outlet's own source link AND the source's exact words (verbatim: a literal span of the stored document, offsets into it, content-addressed by docId). The claim text is the extracted proposition and is never a quote. Anything else is UNRECEIPTED: retained, counted here by reason, never shown; every published count is computed from receipted items only.
  • Disagreement pairing: 10 candidate pair(s) with overlapping words and different numbers were NOT shown as disagreements: 4 report separate incidents or readings (another named date or time, another vessel, or reported on another day), 6 assert different propositions (another party or quantity) and 0 could not be matched role for role. Two reports disagree here only when they give different values for the same actor, counterparty, quantity and incident: the same named date, or the same report day when no date is named.
  • Event grouping (event@2): 2984 claim(s) are source sentences; 283 were grouped into 120 multi-sentence event(s) and 1733 matched no other claim, giving 1853 event(s). 968 claim(s) could not be matched (untyped action class, no participant read, or no report day), so their count stays per sentence: could not match is not single source. The rule is mechanical and conservative (same typed action, shared participants and wording, no different named person or market, first seen within 1 day, no conflicting date, time, vessel, means (mine, missile, drone, boarding, gunfire) or value, every member matched to one anchor), so it under-groups: it measures reporting agreement about one incident, not verification.