Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
European Tech Sovereignty
17MAY

Easter ceasefire expires; violation counts diverge

3 min read
14:28UTC

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
OpenForum Europe / open-source community
OpenForum Europe / open-source community
The EUR 350m Sovereign Tech Fund has no Commission host, no budget line, and no commissioner's name attached six weeks after the April conference, while Germany is already paying maintainers to staff international standards bodies. The CRA open-source guidance resolves contributor liability but leaves the financial-donations grey area open with the 11 September reporting clock running.
ASML / Christophe Fouquet
ASML / Christophe Fouquet
ASML's Q2 guidance miss of roughly EUR 300m below consensus reflects DUV revenue compression set by US export controls, not European policy. Fouquet said 2026 guidance accommodates potential outcomes of ongoing US-China trade discussions; a bipartisan US bill to tighten DUV sales further would accelerate the cross-subsidy thinning Chips Act II's equity authority is designed to address.
Anne Le Henanff / French G7 Presidency
Anne Le Henanff / French G7 Presidency
Le Henanff chairs the 29 May Bercy ministerial two days after Brussels adopts the Tech Sovereignty Package, making the G7 communique the first international read of the Omnibus enforcement split and CAIDA's scope. France's Cloud au Centre doctrine is already operational via the Scaleway Health Data Hub contract.
German federal government
German federal government
Berlin operationalises sovereignty through procurement mandates (the ODF requirement and the Sovereign Tech Standards programme) rather than waiting for Commission legislation. The Bundeskartellamt has still not received the Cohere-Aleph Alpha merger filing, leaving Germany's flagship AI champion in structural limbo six weeks after the deal resolved.
US Trade Representative
US Trade Representative
The USTR Section 301 investigation into EU digital rules closes with a 24 July 2026 final determination. CAIDA's public-sector cloud restriction sits within the criteria that triggered the 2020 Section 301 action against France's digital services tax, and the US has not signalled whether the Thales-Google S3NS arrangement resolves CLOUD Act jurisdiction concerns.
CISPE / Valentina Mingorance
CISPE / Valentina Mingorance
CISPE shipped its own pass-fail sovereignty badge in April to establish an industry-auditable floor the Commission could adopt. Whether CAIDA inherits the CISPE binary or the multi-tier SEAL approach will determine whether certification is enforceable by public contracting authorities or requires Commission discretion.