Six days after the first Ukrainian drone strike on Yandex data centers, the disruption still shows up in internet traffic measurements. Cloudflare Radar reported on October 13 that traffic remained approximately 89 percent below the previous week’s level. That is a striking decline, especially because it has persisted beyond the immediate aftermath of the first attack. Whatever the full operational picture inside Yandex, the observation points to a disruption whose effects have not quickly disappeared.
#Radar traffic data continues to show decreased levels of activity 6 days after the first Ukrainian drone strike on #Yandex data centers. Relative to the prior week, traffic levels have decreased by approximately 89%.
Note: Traffic data in Radar includes both bot and human traffic. “Bot traffic” refers to automated requests to websites on Cloudflare’s network, such as crawlers and scripts, not necessarily activity on social media platforms.
https://t.co/uCadXIWkvb
— Cloudflare Radar (@CloudflareRadar) October 13, 2026
The qualification matters. Cloudflare’s figures include both human and automated requests to websites on its network. They are not a direct count of people using Yandex, a measurement of the company’s revenue, or proof that 89 percent of its computing capacity has been destroyed. Nor does “bot traffic” automatically mean propaganda accounts on social media. It includes crawlers and scripts performing ordinary automated tasks. The defensible conclusion is narrower, but still significant: the traffic Cloudflare observes has fallen sharply compared with the prior week and remains depressed six days after the first strike.
For Ukraine, that persistence suggests a potentially consequential vulnerability in Russia’s digital infrastructure. A data center can look remote from the battlefield, yet the services it supports depend on very physical things: electricity, cooling, communications equipment and buildings that must remain usable. Redundancy can distribute workloads and reduce the consequences of a failure, but it cannot be assumed to make every disruption brief or painless. The cloud, as this episode rather bluntly reminds us, has an address.
There is reason to welcome evidence that Ukraine can impose sustained costs on the country waging war against it, while keeping the interpretation proportionate to what the data actually shows. This observation does not establish which military or government functions, if any, were affected. It does show why digital infrastructure deserves attention alongside the more familiar discussion of refineries, transport routes and industrial facilities: damage can have consequences that remain visible well after the initial explosion.
The next revealing development will be the recovery. A return toward previous traffic levels would suggest that repairs, rerouting or replacement capacity are restoring activity. Continued weakness would raise further questions about the depth and duration of the disruption. For now, the notable fact is that the decline has lasted. Six days later, the effects are still measurable—and that makes this more than a fleeting headline.