Skip to content
Foundations rebuilt, and the first new thing is here: search across every topic, entity, and event.Try search
European Tech Sovereignty
10JUN

Easter ceasefire expires; violation counts diverge

3 min read
10:31UTC

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.

← Back to Sovereignty law adopted; $40bn US chip buyJump to analysis ↓
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.

Sources:Al Jazeera
Mentions:Vladimir Putin →Ukrainian General Staff →Novaya Gazeta Europe →Orthodox Easter ceasefire →France →Moscow →Russian Ministry of Defence →Volodymyr Zelenskyy →Ukraine →Kyiv →Kremlin →Brookings Institution →Russia →
First Reported In

Update #13 · Treasury kills the Russian crude waiver

Al Jazeera· 16 Apr 2026
Read original →
Causes and effects
Caused by
Putin calls solo 32-hour Easter truce
Putin's 32-hour Easter ceasefire decree directly produced the expiry event and the ceasefire violation counts.
Occurred 9 Apr 2026
Read story →
This Event
Easter ceasefire expires; violation counts diverge
The expiry establishes the decree as a messaging instrument rather than a pause in operations, and sets a baseline for reading the next Russian Easter-style gesture.
Led to
Kyiv calls Putin truce offer theatrical
Zelenskyy's theatrical characterisation draws directly on the Easter expiry record of 10,721 Russian violations as evidence of pattern behaviour
Occurred 30 Apr 2026
Read story →
Three ceasefires collapsed with zero instruments signed
Easter ceasefire expiry with 10,721 logged violations established the violation-tally precedent the 6 May Ukrainian ceasefire replicated.
Occurred 8 May 2026
Read story →
Different Perspectives
European cloud and open-source industry
European cloud and open-source industry
European cloud providers gain a binding procurement mandate from CADA, confirmed by Gartner's $12.6bn sovereign-cloud figure for 2026. The $40bn Pax Silica commitment signals Brussels will not extend sovereignty discipline to the silicon layer, and the missing €350m Sovereign Tech Fund leaves open-source maintenance infrastructure unfunded beneath those same clouds.
United Kingdom
United Kingdom
Science Secretary Kendall's £1.1bn Hardware Plan on 8 June chose demand-side instruments, advancing £150m to British chip startups via the British Business Bank, where Brussels chose supply-side alliance membership. Britain joined Pax Silica before the EU and has no collective EU procurement leverage; the Hardware Plan is the bilateral answer to the same silicon gap.
United States
United States
Pax Silica, a State Department initiative launched in December 2025, secured EU membership the same afternoon Brussels adopted its cloud sovereignty law. Ambassador Puzder had named CADA a red line against the EU-US trade framework; the narrowed CADA scope and the $40bn chip commitment together represent the settlement Washington sought.
France
France
France was the only EU state to oppose Pax Silica accession at COREPER on 3 June, asking the Commission to clarify the Council's steering role inside the alliance. Paris backed CADA and hosts Mistral AI; a $40bn US-chip commitment contractually narrows the commercial space for the sovereign AI model that France is trying to scale.
European Commission
European Commission
Von der Leyen framed CADA on 3 June as keeping 'most of our market open to like-minded partners', and the Commission's EVP Virkkunen simultaneously required majority-European ownership for the €4.12bn AI Gigafactories call. Brussels is managing rather than resolving the silicon dependency by asserting regulatory control at the cloud layer while formalising the chip relationship through Pax Silica.
European Central Bank
European Central Bank
The ECB's digital euro pilot drew more than 50 PSP applications and is naming 10 to 30 participants in July, advancing on its own monetary mandate without requiring a Commission act. Its trajectory this week is the inverse of CAIDA's: the sovereignty instrument that restricts no US firm is the only one keeping its published calendar.