Skip to content
You can now search across every topic, entity and event.What's new
Iran Conflict 2026
18JUN

Lebanon is where the deal cracks first

3 min read
10:02UTC

The IRGC says Israel breached the Lebanon ceasefire 84 times in two days; Iran's military threatened retaliation while the US and Iran dispute whether the deal even covers Hezbollah.

ConflictDeveloping
Key takeaway

Lebanon's disputed scope gives Iran a ready violation claim before Friday's Geneva ceremony.

Lebanon was the one front the memorandum was meant to quiet, and it is breaking the deal first. The Islamic Revolutionary Guard Corps (IRGC) says Israel violated the Lebanon ceasefire 84 times in two days 1; the Israel Defense Forces (IDF) confirmed intercepting Hezbollah rockets fired at its troops in the south . On Tuesday 16 June Iran's military command issued a formal threat of retaliation if Israel's southern Lebanon offensive continues 2. That threat, already on the record, is the fuse that can detonate the ceasefire before Friday's Geneva ceremony. Israel's Defence Minister says troops stay inside a 25-mile "security zone".

The two sides do not even agree the deal covers Lebanon. US Ambassador to Israel Mike Huckabee stated flatly that "Hezbollah is not included in the deal" 3; Iran and Pakistan insist it covers all fronts, Lebanon included. JD Vance has said both that the memorandum is "not conditioned on Israel withdrawing from Lebanon" and that it "envisioned a ceasefire that covers both Iran and Lebanon". Those two formulations cannot both hold.

The gap between them hands Iran's foreign minister Abbas Araghchi a ready-made violation claim to carry into Geneva. A ceasefire with no agreed scope is a ceasefire either side can declare broken at the moment it suits them, and Araghchi already holds the 84-violation count as his pretext. Israel's cabinet has separately repudiated the deal outright , so Lebanon is contested both across the front line and from inside Jerusalem's own government.

Deep Analysis

In plain English

Iran and the US signed a ceasefire, but they couldn't agree whether it covered the fighting in Lebanon between Israel and Hezbollah. The US ambassador to Israel said Hezbollah was not in the deal; Iran and Pakistan said it was. Meanwhile, the fighting continued: Iran claimed Israel broke the Lebanon ceasefire 84 times in two days, and Israeli troops confirmed they fired back at Hezbollah rockets. To make things more complicated, the US Vice President Vance made two different public statements about whether the deal required Israel to pull its troops out of Lebanon. He said both yes and no. That contradiction gives Iran an easy excuse to say the deal is already broken, before the formal ceremony has even happened on Friday.

Deep Analysis
Root Causes

Lebanon's ambiguous status in the MOU has a direct cause: Israel was excluded from the negotiations. Qatar, Pakistan, Saudi Arabia and Turkey brokered the text. None of them can commit Israel to a ceasefire.

Washington declined to make Israeli Lebanon withdrawal a precondition for US signatures. The result is a ceasefire text that both Iran and the US read to their domestic audiences as covering or excluding Lebanon, depending on which statement Vance made most recently.

What could happen next?
  • Risk

    Iran can invoke the MOU's violation clause over Lebanon ceasefire breaches before Friday's Geneva ceremony, using Vance's two incompatible statements as evidence of US bad faith.

  • Risk

    Without an explicit Lebanon annex with enforcement mechanisms, Israeli-Hezbollah exchanges provide Iran a permanent trigger to suspend MOU compliance throughout the 60-day nuclear window.

First Reported In

Update #130 · Trump signed the war over; it kept going

ABC News· 17 Jun 2026
Read original
Different Perspectives
Lloyd's Market Association
Lloyd's Market Association
War-risk underwriters price the Houthis' Red Sea attacks because the group announces its targets in advance, but the unclaimed Damietta drone gives insurers a hit with no author to price against. An attack nobody claims costs shipping more than one that is claimed, since premiums are set against a known pattern, not raw damage.
US Central Command
US Central Command
CENTCOM has announced no strike on Iran since resuming bombing on 30 July within hours of an IRGC salvo on Jordan, and centcom.mil did not respond to requests to confirm any pause. The command has gone quiet before while a larger operation was being weighed, so silence alone proves nothing about what it has or has not done.
Hengaw
Hengaw
Hengaw recorded at least 67 executions in Iran during July, of which the state acknowledged only eight, and reported the 1 August execution of protest detainee Arvin Kheirkhahan at Shahrud with no advance notice to his family. A family's first notice of a death sentence is now usually the instruction to collect a body.
Egypt
Egypt
Egypt's government asked media on 2 August to report the Damietta attack accurately, named no author, and said no findings will be published before its own investigation concludes. Cairo holds the debris and jurisdiction over an attack on its own soil, and naming a culprit now would pull it into a dispute it has avoided for five months.
Iran's Foreign Ministry
Iran's Foreign Ministry
Araghchi called the Hormuz talks with Oman final-stage on 2 August, four days after his own deputy rejected Oman's lane proposal, and denied the Damietta drone strike as an Israeli false flag while two Iranian officials privately claimed it for Tehran. Iran's public position now contradicts itself on both files at once.
Bahrain and Kuwait
Bahrain and Kuwait
Bahraini and Kuwaiti aircraft flew their own strikes on Iranian depots in July with Emirati air cover behind them, and Ynetnews reports some Gulf capitals wanted the 2 August strike to proceed rather than stop. States that have already taken fire see a closing window on Iranian weakness, not a reason to pause.