Victory Day truce collapses as Moscow and Kyiv trade claims of violations in Donetsk

A ceasefire is supposed to simplify a war for a moment. This one did the opposite. Russia and Ukraine announced separate holiday pauses on separate calendars, with separate political goals, and the whole thing started breaking down before Moscow’s Victory Day window even arrived. By May 6, Volodymyr Zelensky said Russian forces had already violated Ukraine’s proposed ceasefire 1,820 times in 10 hours. ### What was the truce actually supposed to be? There wasn’t one shared truce. That’s the core problem. Vladimir Putin declared a unilateral pause for May 8–9 around Russia’s Victory Day commemorations in Moscow. Zelensky answered with a different offer — a ceasefire starting at midnight on May 6 — and framed it as a real test of whether Russia wanted silence on the battlefield rather than just safety for a parade. (meduza.io) ### Why did Kyiv reject Moscow’s version? Kyiv’s view was basically this: a two-day pause built around Red Square is not a peace process. Ukrainian officials said they saw no reason to honor a truce designed for a Russian state ceremony after Russia kept attacking during Ukraine’s earlier proposed pause. Zelensky also said Moscow never properly worked through the terms with Kyiv, which made the Kremlin’s offer look more like a public message than a negotiated mechanism. (meduza.io) ### What happened on May 6? The Ukrainian side says the answer is simple — the ceasefire was dead on arrival. Zelensky said Russia committed 1,820 violations by 10 a.m. local time, including shelling, air attacks, drone strikes, and attempted ground assaults. Ukrainian reporting from the same day also described overnight attacks involving missiles and more than 100 drones. Russia, for its part, said it had intercepted dozens of Ukrainian drones and accused Kyiv of striking Russian territory and occupied Crimea. (meduza.io) ### Why does Donetsk matter here? Because this is where “ceasefire” meets trench reality. Donetsk remains one of the main pressure points of the war, with constant artillery, drones, and probing assaults. In that environment, a truce only works if both sides agree on the start time, the scope, the enforcement, and what counts as a violation. None of that existed here. So each side could keep fighting and still claim the other side broke the deal first. That is exactly what happened. (politico.eu) ### Why was Victory Day part of the story at all? Victory Day is one of the Kremlin’s most symbolically important dates. Moscow uses the May 9 parade to project strength, legitimacy, and wartime continuity with the Soviet victory in World War II. That made the truce politically useful even if it was militarily flimsy. Ukraine’s response was to say, in effect, that civilian deaths and frontline combat do not pause just because the Kremlin wants a cleaner backdrop for a ceremony. (meduza.io) ### Is this a one-off failure? Not really. Short holiday ceasefires in this war have a bad record. The same pattern showed up around Orthodox Easter, when both sides also accused each other of repeated violations. That history matters because it means neither army treats a brief unilateral pause as trustworthy. The battlefield logic overwhelms the holiday logic almost immediately. (politico.eu) ### So what changed after this collapse? The immediate change is political, not strategic. Kyiv signaled it no longer considered itself bound by Moscow’s May 8–9 truce after the May 6 violations. That strips away even the thin fiction of a mutually observed pause. It also shows how far the war is from any enforceable broader ceasefire — if the sides cannot align on two days, they are nowhere near aligning on a real settlement. (defensenews.com) ### Bottom line? This was less a truce than a duel of announcements. Russia wanted calm around Victory Day. Ukraine wanted proof that Russia could stop shooting. Neither side trusted the other enough to build one shared pause, so the battlefield kept talking. (meduza.io) (politico.eu)