Debunked · Zarit ·
The Home Front Command issued hostile aircraft (drone) alerts for Zarit and Shomera around 04:10 UTC and told residents to enter protected spaces. The IDF later said the sirens were a false identification, and it later said residents could leave protected spaces, and Western Galilee sirens were reported in the same period.
Unofficial; built automatically from public posts and can be wrong. Verify before acting.
Verification
Debunked: 7 independent sources. Set aside: not shown on the map.
Verification describes the available evidence, not certainty that an event occurred.
The reports point to this being false or misattributed, so it is kept for the record. It is a judgement from the available evidence and can be revised. A siren warns of a possible threat; it does not mean anything struck there.
What we know and what remains unclear
Each detail the reports give, by how many independent origins reported it. An origin is the outlet or channel where a claim first appeared; reposts count once. Confidence in the event is not confidence in each detail. This counts reports: it is not a measure of accuracy, and it does not change the event's status. "Reports differ" means two origins gave values that cannot both be true; it is about that detail, not about whether the incident happened.
Reported by one source or disputed
- Place: Zarit, Israel · 3 origins, not corroborated
- Time: 8 Nov, 04:10 UTC · 2 origins, not corroborated
- Who did it: IDF (same side as another named) · 1 origin
- Who did it: Israel (same side as another named) · 1 origin
All details
| Detail | Reported | Reported by | Status |
|---|---|---|---|
| Place | Zarit, Israel | @PikudHaOref_all (Telegram); IDF (via @alhadath_brk (Telegram), @mtvlebanonnews (Telegram), @ynetalerts (Telegram)); The Jerusalem Post; consistent with it: @wfwitness (Telegram); @TPOnow (Telegram); The Times of Israel | 3 origins, not corroborated; limited by the event's status |
| Time | 8 Nov, 04:10 UTC | @wfwitness (Telegram); @PikudHaOref_all (Telegram) | 2 origins, not corroborated; limited by the event's status |
| Who did it | IDF (same side as another named) | IDF (via @alhadath_brk (Telegram), @mtvlebanonnews (Telegram), @ynetalerts (Telegram)) | One origin |
| Who did it | Israel (same side as another named) | IDF (via @alhadath_brk (Telegram), @mtvlebanonnews (Telegram), @ynetalerts (Telegram)) | One origin |
Official alerts for 2 localities, all from Home Front Command. An alert shows that it was issued, not that anything was hit.
No detail reads as independently reported while the event itself is not corroborated.
Sources
- Home Front Command alerts (via Tzeva Adom),
- @PikudHaOref_all (Telegram),
- Home Front Command alerts (via Tzeva Adom),
- @PikudHaOref_all (Telegram),
- @TPOnow (Telegram),
- @wfwitness (Telegram),
- @ynetalerts (Telegram),
- ME Observer (Telegram),
- IDF (official),
- @alhadath_brk (Telegram),
- The Times of Israel,
- @PikudHaOref_all (Telegram),
- @ynetalerts (Telegram),
- @alhadath_brk (Telegram),
- @mtvlebanonnews (Telegram),
- The Jerusalem Post,
- The Jerusalem Post,
- IDF (official),
- @ynetalerts (Telegram),
- Middle East Eye,
Changes
Changed 2 times. This event in the corrections and audit log
- : Unverified
- : Unverified to Confirmed
- : Confirmed to Debunked (set aside)
First reported · Last updated
Lebanon: latest reports · All reports on 8 November 2026 · Live map · How this works · Corrections and audit log