sitmap.live

Corrections, Verification & Audit Log

Every report on sitmap.live carries a verification state, and states change. This page shows what we got wrong or could not stand behind, how well sourced recent events are, and each change of state as it happened.

Unofficial · verify before acting
CorrectionsWhat is marked disputed or debunked, and what was withdrawn VerificationHow well sourced the last 30 days of events are, and whether early reports held up Audit logEach recent change of an event's state, as it happened

Marked disputed or debunked

Sources contradict each other (disputed), or the report was judged false or misattributed (debunked). These stay on the site for the record.

Verification, last 30 days

6806settled incidents
182still settling (under 12 h)
182disputed now
0debunked now
266withdrawn

Incidents by verification state. An attack and the reports of its aftermath (casualties, damage, closures) linked to it are one incident, counted at the attack's state: 106 such reports are not counted again. Incidents reported in the last 12 hours are left out of the chart: corroboration takes hours, so a fresh report is unverified for want of time, not for want of sources. This says how well sourced they are, not how true: a single-source report is not a false one.

Confirmed1212%
Corroborated4136%
Single source321247%
Unverified287842%
Disputed1823%
Debunked00%

Not counted: 1067 leads (aggregator reposts that name no source).

Withdrawn events (merged away, found out of scope, or removed by review) are not listed. When an event we posted on X is later disputed, debunked or withdrawn, the post gets a reply saying so.

Do early reports hold up?

Every event on the map starts as one report. These are all 1517 events first reported since 2026-10-26 (leaving out the last 12 hours, too recent to judge), by where each stands now.

129corroborated or confirmed
10rated up with no new source
28disputed or debunked
95withdrawn
690single source
565unverified

129 (9%) were corroborated by an independent source or confirmed, a median of 5 hours after the first report. 10 (1%) reached corroborated or confirmed only when the same reports were rated again (changed rules or ratings, or a new review), with no new source: they are not counted as having held up. 28 (2%) were contradicted: marked disputed or debunked. 95 (6%) were withdrawn as out of scope or on review. 690 (45%) rest on one credible source, and 565 (37%) on no credible source: anonymous or partisan channels only, however many. Neither group has been confirmed or contradicted, which does not make them wrong.

Not counted: 338 leads, reposts by aggregator channels that name no source. Nothing in them can be checked, so they are not events until a report with a source of its own joins them.

Audit log

The newest changes of state the site has recorded, newest first, in UTC, each with why it changed. Events withdrawn from the site are not named. Recording of state changes began 2026-10-26 19:13 UTC; earlier changes were not recorded.

Since 2026-10-26: 206 moves up to corroborated or confirmed on new reports or evidence; besides, 106 reclassified by changes to the rules, ratings or settings (changes to the rules); 1 by the automated review or on review; 13 re-ratings of the same reports whose cause was not recorded. 105 moves down a level.

  1. Iranian officials say US attack hit two fishing boats off Qeshm IslandSingle source to Corroboratednew report
  2. Iran reportedly has not yet responded to US demand to abandon nuclear projectUnverified to Corroboratednew report
  3. Qatari mediators reportedly return to Tehran to push for US-Iran dealCorroborated to Confirmednew report
  4. Warplanes reportedly attacked Wadi al-Saluki in southern LebanonUnverified to Single sourceautomated review
  5. Israeli strikes reportedly hit Adsheet Al-Qasir area in South Lebanon overnightUnverified to Corroboratednew report
  6. Drone reportedly flying over Beirut's southern suburbUnverified to Corroboratednew report
  7. Machine-gun fire reported at Ibl al-Saqi in south Lebanon, attributed to Israeli forcesUnverified to Single sourcenew report
  8. Israeli forces reportedly blow up displaced Lebanese homes in Bani Hayyan, south LebanonUnverified to Corroboratednew report
  9. Israeli forces reportedly warn of demolishing facilities at northwestern Hebron entranceSingle source to Corroboratednew report
  10. Warplanes reportedly attacked Wadi al-Saluki in southern LebanonSingle source to Corroboratednew report

Changes to the rules

When the rules that set a state change, stored events are rated again on the same reports. Those moves are reclassifications, not new evidence: they are counted apart above and listed here.

  1. party rule. A party's statement about its own strikes, its interceptions or the enemy's losses no longer confirms an event; a neutral body, an authority's own record or an admission against interest still does.0 up, 61 downD32
  2. strong-origin corroboration. An established or stronger origin plus any second independent one corroborates (before, the weights had to add up to 1.2); the stored weak events with two or more origins were rated again.106 up, 0 down5a3a285 strong-origin corroboration + reverify:multi

Air-traffic signals withdrawn or lowered

Drops in air traffic are machine-detected from ADS-B counts. When a signal turns out to rest on poor receiver coverage, or is rated higher than its evidence allows, it is withdrawn or its confidence lowered, and the change is listed here.

  1. QA airspace, drop detected 2026-10-30 09:57 UTCConfidence high to mediumno airspace closure notice in force covers it, and a fall in the aircraft counted entering a FIR is never high confidence alone
  2. IQ airspace, drop detected 2026-10-30 12:36 UTCWithdrawnour receivers' coverage of the Baghdad FIR (ORBB) is thin: 69% of the polls over the 7 days before saw no aircraft inside it. A fall in the aircraft counted there is not evidence of a closure