26JUL

Lebanon is where the deal cracks first

3 min read

10:21UTC

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.

← Back to The €890m fine that cost more than it collects Jump to analysis ↓

TechnologyDeveloping

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 ¹; 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 ². 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" ³; 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.

Source Landscape

This story draws on centre-left-leaning sources from United States and India

United States

India

Primary parallel: The 2006 UN Security Council Resolution 1701 ended the Israel-Hezbollah war in Lebanon. The resolution required Hezbollah to withdraw north of the Litani River and Israel to withdraw from Lebanese territory, but included no enforcement mechanism.

Israel remained in pockets of southern Lebanon for months; Hezbollah never fully complied with Litani withdrawal. The Islamabad MOU's Lebanon clause faces the same gap: no enforcement body, no compliance timetable, and a state, Israel, that has declared the deal does not bind it.

Counter-parallel: The 1974 Golan Heights Disengagement Agreement between Israel and Syria established UNDOF with a physical buffer zone and daily liaison channels between Israeli and Syrian commanders. That agreement has held for over 50 years because Israel and Syria both signed and neither walked away from the text. Israel's Ben-Gvir and Smotrich have done exactly what the 1974 Syrian government did not: publicly repudiated the deal on the day of signing.

Consensus view: A ceasefire without an explicit Lebanon annex creates an automatic violation mechanism: Iran holds a ready-made complaint every time Israel fires, and the US cannot stop Israel firing. The structural problem is that Washington and Tehran are co-signatories but only one of them commands Hezbollah and the IDF, and it is not the same one.

Counter-view: The Institute for National Security Studies in Tel Aviv argues that Israel's presence in a southern Lebanese security zone is non-negotiable for any government that survives the next election, and that both Iran and the US knew this going into the Islamabad process. Tel Aviv reads Huckabee's statement, that Hezbollah is not in the deal, as Washington confirming the same implicit understanding.

Key tension: Vance's two incompatible statements on Lebanon give Iran's Foreign Minister Abbas Araghchi a documented US contradiction to cite as justification for invoking the MOU's violation clause before Friday's Geneva ceremony.

First Reported In

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

ABC News· 17 Jun 2026

Read original →

Causes and effects

Caused by

Hezbollah fired on Israel hours after signing

The 15 June Hezbollah rocket fire and Araghchi's violation-clause invocation escalated into Iran's formal retaliation threat on 16 June.

Occurred 15 Jun 2026

Read story →

Israel refuses the deal's Lebanon clause

Katz's unlimited Lebanon stay declaration on 14 June is the Israeli posture that generated the IRGC's 84-violation count and formal retaliation threat.

Occurred 14 Jun 2026

Read story →

This Event

Lebanon is where the deal cracks first

The one front the memorandum was meant to quiet is the front actively breaking it before Friday's ceremony.

Led to

Israeli minister wants Lebanon to burn

Iran's threat on the Lebanon clause (event 5) follows the earlier US-Iran dispute on whether the MOU covered Hezbollah (ID:4273).

Occurred 18 Jun 2026

Read story →

Different Perspectives

China's Ministry of Commerce

Spokesperson He Yadong said on 16 July that Beijing and the Netherlands should let firms settle the Nexperia dispute through consultation, after a Dutch ministerial visit to Beijing. The conciliatory tone contrasts with the confrontational US trade response to the same fortnight's DMA enforcement.

Samsung Electronics

Samsung entered talks reported 22 July to invest up to €1 billion in Mistral AI, part of a round valuing the French lab at roughly €20 billion alongside EQT, Novo Holdings and Santander. The Korean conglomerate, not an EU financing instrument, is positioned to anchor Europe's flagship AI lab.

Poland (Tusk government)

Donald Tusk's government proposed a mandatory sovereignty test on 21 July for state technology contracts above 5 million zloty, scoring bids on AI model-weight rights and vendor lock-in rather than waiting for an EU-wide procurement rule. The threshold targets a 20-30 per cent domestic-alternative share.

United States administration

Donald Trump ordered a Section 301 investigation into EU digital-enforcement practices on 24 July, a day after USTR's Jamieson Greer said the Google fine created massive uncertainty for US exports, noting Google's cumulative EU fines already exceed 2 per cent of the bloc's budget.

Ecosia

Ecosia said the 16 July FRAND ranking-data order would take it from answering two-thirds of queries to all of them once the obligation activates in January 2027. The Berlin-based challenger has not called the enforcement package adequate, only workable if Google complies rather than appeals.

European Commission

Teresa Ribera and Henna Virkkunen announced the €890m fine on 23 July, saying products should succeed on merit, not platform ownership; four days earlier a separate Article 6(7) order compelled Android interoperability. The Commission expects both to hold on appeal after the Court of Justice upheld its earlier €4.1bn Android fine on 2 July.