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

Easter ceasefire expires; violation counts diverge

3 min read
16:40UTC

Putin's truce ended at midnight Moscow time on 13 April. Kyiv logged 10,721 violations; Moscow logged 1,971. Novaya Gazeta Europe's reading of asymmetric compliance is the useful one.

ConflictDeveloping
Key takeaway

Ceremonial truces pause the wire stories, not the war.

Vladimir Putin's unilateral Orthodox Easter truce, decreed on 9 April, expired without extension at the end of 12 April. The Ukrainian General Staff tallied 10,721 Russian breaches over the period, including 119 ground assaults. The Russian Ministry of Defence tallied 1,971 Ukrainian breaches, including 258 artillery firings, 1,329 kamikaze drone strikes, and 375 munitions drops.

The Kremlin had rejected Volodymyr Zelenskyy's earlier Easter proposal targeting energy infrastructure attacks in late March . Putin's eventual decree came without any prior US diplomatic contact, per his published Kremlin calendar showing nine days of domestic engagements and no US meetings ahead of the announcement. Novaya Gazeta Europe, a Russian exile outlet based in Riga, assessed that Russia held back on strategic-strike activity throughout the pause while tactical-range fire carried on. That matches the pattern of asymmetric compliance: a partial halt on rear-area bombardment paired with unchanged close-in operations.

The timing of the window closes is the other analytic point. The decree concluded just as Hungarian polling day entered its final hours , giving Moscow a news cycle of Orthodox Easter imagery during the period the electorate was still voting. The immediate post-expiry barrage is detailed in event 4. The sequence is now a datable pattern: decree, partial compliance, expiry, return to baseline tempo. Any future Russian ceremonial ceasefire can be read against the same test, Russian long-range activity during the window, and the first 24 hours after.

Deep Analysis

In plain English

Russia's Vladimir Putin called a 32-hour ceasefire for the Orthodox Easter holiday. It ran from the evening of 11 April to midnight on 13 April. After it ended, both sides accused the other of thousands of violations during the window. Ukraine logged over 10,000 Russian violations, mostly artillery fire and small attacks along the front. Russia logged nearly 2,000 Ukrainian violations. Both sets of numbers are real in the sense that fighting continued; they differ because each side uses its own definition of what counts as a violation. The ceasefire was announced by Putin without any prior negotiation with the US or Ukraine, and it expired without any framework for extension. The night after it ended, Russia launched its largest drone barrage in days.

Deep Analysis
Root Causes

The 10,721 violation count that Ukraine logged measures a different thing than battlefield restraint: it includes every artillery round, every drone, every mortar that crossed the contact line during the 32-hour window. The Russian count of 1,971 Ukrainian violations uses the same imprecise instrument in the opposite direction. Neither count addresses whether the ceasefire altered the strategic trajectory of the war, which it did not.

The structural reason these unilateral ceasefires produce the same outcome each time: they are announced without any enforcement mechanism, without any agreed definition of a violation, and without any consequence for non-compliance. Their function is domestic Russian information management and international signal-sending, not battlefield management.

What could happen next?
  • Consequence

    The fourth unilateral Russian ceasefire decree, each producing the same violation-count dispute, establishes a pattern that makes future unilateral ceasefire claims less credible with each repetition.

  • Risk

    The ceasefire's alignment with Hungarian polling day, ending at midnight on 12 April, the day of the election, created a domestic political frame for Orbán that was disrupted when Tisza won decisively despite the timing.

First Reported In

Update #13 · Treasury kills the Russian crude waiver

Al Jazeera· 16 Apr 2026
Read original
Different Perspectives
China's foreign ministry
China's foreign ministry
Spokesman Lin Jian rejected Treasury Secretary Scott Bessent's 25 August warning that Iranian oil buyers face an "economic D-Day", saying sanctions do not help and that Beijing would safeguard its own rights and interests. China's Iranian crude imports had already halved for unrelated reasons.
Iraq's government and Erbil authorities
Iraq's government and Erbil authorities
Erbil authorities said 10 explosive-laden drones were shot down over the city on 1-2 September with no casualties. Iraq's government condemned the attacks without naming Iran as their source, and neither Washington nor Baghdad confirmed the IRGC's claim to have hit US bases there.
Bahrain Defence Force
Bahrain Defence Force
The General Command said air defences intercepted several Iranian missiles and drones on 1-2 September and called the use of such weapons against civilians and private property a flagrant violation of international humanitarian law.
Kuwait's Fire Force and foreign ministry
Kuwait's Fire Force and foreign ministry
KUNA reported a hostile Iranian drone struck a residential complex in Kuwait City on 2 September; Fire Force spokesman Brigadier General Mohammad Al-Gharib said losses were confined to property. Kuwait's foreign ministry called the attack a clear breach of its sovereignty.
Jordan's Armed Forces
Jordan's Armed Forces
Petra carried a statement that air defences intercepted eight missiles violating Jordanian airspace early on 31 August and 10 of 13 fired on 1 September. The statement named no target and did not address the IRGC's claim to have struck Camp Titin and killed US personnel.
CENTCOM
CENTCOM
CENTCOM's 1 September target list named IRGC air defence, radar, maritime and mine-laying sites in Iran but no tanker, after Axios reported anonymous officials describing a Trump-approved "tanker for tanker" drone policy. A CENTCOM spokesman declined to confirm the policy and referred questions to policymakers.