Telegram log shows Israeli artillery and airstrikes across at least six locations in southern Lebanon on 2 September 2026
The Telegram channel @wfwitness logged Israeli artillery and airstrike activity across at least six southern Lebanese locations between 20:45 and 21:41 UTC on 2 September 2026, with the channel alone claiming bunker-buster use on the Ali al-Taher heights.

The open-source war-monitoring channel @wfwitness posted nine items on 2 September 2026 describing Israeli artillery and airstrike activity across southern Lebanon between 20:45 and 21:54 UTC, with Kfar Romman, Qantara, Touline, Wadi Salouq, Wadi Hujeir and the Ali al-Taher heights all named in the log. Two items also referenced Madrid, an unrelated topic.
What the log carries is time, place, and one munition claim from a single channel. What it does not carry is any IDF Spokesperson statement, any Lebanese or UNIFIL response, any casualty figure on either side, or any identification of the specific assets struck. The bunker-buster attribution in particular is the channel's report, not an Israeli confirmation: the post at 21:41 UTC frames the use of bunker busters as a wfwitness channel claim, and the available items do not establish the munition type from an IDF source.
What the channel posted, and when
The log begins at 20:45 UTC with Israeli artillery bombardment of the Dawhat neighbourhood of Kfar Romman, southern Lebanon. A second item at 20:49 UTC repeated the Kfar Romman strike, and a third at 20:50 UTC added what the channel labelled renewed artillery fire in the same village. Three minutes later, at 20:55 UTC, the channel logged Israeli artillery fire on Qantara, southern Lebanon. At 20:57 UTC, the same channel posted that Israeli artillery fire had been reported in Touline, southern Lebanon, and the same update added Wadi Salouq and Wadi Hujeir as locations receiving Israeli artillery fire alongside Touline. The 20:55 and 20:57 UTC items also carry preview text that already mentions the adjacent Qantara and Touline locations.
At 21:25 UTC, the channel reported that an Israeli airstrike had targeted the Ali al-Taher heights in southern Lebanon. The final Lebanon-relevant item in the available set, posted at 21:41 UTC, logged multiple Israeli airstrikes on the same heights and added the channel's bunker-buster claim: 'The IDF used bunker busters,' per wfwitness. That is the only item in the available set that names a specific munition category, and it does so in connection with the Ali al-Taher strikes rather than the village-level artillery fire logged earlier in the evening. Two further items in the same window, posted at 21:54 and 22:04 UTC, address an unrelated topic, mass protests in Madrid, and are not part of the southern Lebanon sequence.
What the log does and does not establish
The log establishes the posting-time sequence and the named geography. It does not establish casualty figures on either side of the border, the identity of any armed-formation assets struck at the Ali al-Taher heights, the specific type of bunker-buster munition, the scale of each strike, or whether ground forces moved into any of the affected villages. The available items do not specify whether the IDF Spokesperson, the Lebanese army, Hezbollah, or UNIFIL issued statements on the evening's bombardment.
A small analytical caveat applies to the posting pattern. Telegram timestamps reflect posting time, not event time, and the 20:49 UTC and 20:50 UTC entries on Kfar Romman may document the same underlying round of fire recorded at slightly different intervals. Monexus reads the Kfar Romman cluster as one operational event with three Telegram entries rather than three distinct bombardments; the village-level items on Qantara and Touline are treated as distinct given the separate posting windows. The preview text in the 20:55 and 20:57 UTC posts, which already names the adjacent village, is a reminder that Telegram posts on this feed are not always strictly sequenced by event.
The attribution problem the log cannot resolve
The bunker-buster attribution is the load-bearing detail of the evening's log, and it is the one the available evidence is least able to support. The 21:41 UTC post frames the IDF's use of bunker-buster munitions as a wfwitness channel claim. The draft of this article initially read that claim as an established fact; on review, it is properly read as the channel's assertion, which is a meaningful attribution shift. Until an IDF Spokesperson briefing or an Israeli wire report confirms the specific munition, the bunker-buster line sits on a single Telegram channel and not on a primary source. The same caveat applies, with different force, to every other claim in the log: the village names, the timing, and the strike count are all wfwitness reporting, not IDF-confirmed action.
Monexus assessment: read together, the nine Lebanon-relevant items describe a multi-axis evening of fire along the southern Lebanese frontier, with the channel alone supplying the geometry, the timing, and the bunker-buster claim. The log does not tell a reader whether the sequence was retaliation for a specific incident, part of a pre-planned clearing operation, or preparatory action ahead of further operations; those framings remain open on the Telegram evidence.
What to watch next
Three threads would close the open questions. First, an IDF Spokesperson briefing identifying the targets struck at the Ali al-Taher heights and confirming or revising the munition-type claim. Second, a Lebanese health ministry or local civil defence statement giving casualty and damage figures for Kfar Romman, Qantara, Touline, Wadi Salouq and Wadi Hujeir. Third, any UNIFIL statement on cross-border activity in the sector for 2 September 2026. Until at least one of those is on the record, the Telegram log remains the most that can be cited with confidence, and the wider read of the evening remains a read, not a finding.
Desk note: Monexus framed this as a what-the-log-says piece. The Telegram source set gives time, place and one munition claim from a single channel, but does not give death tolls, command-level attributions, or statements from Israeli, Lebanese or UNIFIL spokespeople, and the article is built accordingly.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/wfwitness/109549
- https://t.me/wfwitness/109550
- https://t.me/wfwitness/109551
- https://t.me/wfwitness/109552
- https://t.me/wfwitness/109553
- https://t.me/wfwitness/109556
- https://t.me/wfwitness/109557
- https://t.me/wfwitness/109559
- https://t.me/wfwitness/109560