Skip to content
Welcome, thoughtbot's Giant Robots listeners!Start here
Autonomous Systems: Land & Sea
13JUN

Easter ceasefire expires; violation counts diverge

3 min read
11:07UTC

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.

TechnologyDeveloping
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
DNV and Fassmer
DNV and Fassmer
Signed a memorandum at SMM in Hamburg, announced on 10 September, to seek an approval in principle for autonomous naval vessels. DNV's Rasmus Stute said autonomy is "becoming one of the key pillars in defence".
Belgian Ministry of Defence
Belgian Ministry of Defence
Awarded Exail Robotics Belgium €9.87m on 14 September, without competition, for three TRIDENT systems carrying the K-STER C mine-disposal vehicle for Ukraine. It had tendered separately in July for twelve tethered ROVs, not yet bought.
IRGC Navy (Iran)
IRGC Navy (Iran)
IRGC spokesman Hossein Mohebbi said the IRGC Navy seized a US Kingfish mine-hunting vehicle in the Strait of Hormuz on 27 September, valuing it at several million dollars. US Central Command calls the claim "clearly desperate"; no verified imagery exists.
UK Defence Intelligence and Kraken
UK Defence Intelligence and Kraken
Defence Intelligence said the 12 September clash "almost certainly marks the first time" Russian and Ukrainian USVs engaged directly. Kraken meanwhile trialled an unarmed Saab radar picket boat on 5 and 6 October.
Ukrainian forces and ARX Robotics
Ukrainian forces and ARX Robotics
A Ukrainian Sargan-3000 destroyed a Russian robot boat on 12 September, and the first ARX GEREON ground robots reached Ukraine on 29 September. The Sargan-3000 carries a mounted gun.
Indian Register of Shipping
Indian Register of Shipping
Certified Accurate Industrial Controls' ISACA collision-avoidance software to IMO standards after five audited milestones and 2,500 hours of trials. The firm plans to use it converting six Indian Navy patrol boats.

Written with AI from Lowdown's published reporting. Not individually reviewed by an editor. Editorial standards.