Yandex-network bot traffic falls to 0.4% of its two-week peak after Ukrainian drone strikes

The 0.4% is a share of the highest request count in the past two weeks ^[2]. Any outage at the sending network pushes that ratio toward zero, whatever caused the outage.

Tom's Hardware gives two readings of the same series. The first, about 57% of peak on Oct. 8, followed the Sasovo strike ^[5]. The larger Kaluga campus went down after that ^[1]. Between the first reading and the latest, the series fell by a factor of about 140 ^[12].

NetBlocks reports a milder picture. It put Yandex Cloud traffic at 30% and Yandex LLC at 63% ^[7], which is drops of 70% and 37% ^[13]. Bot requests fell 99.6% ^[11]. The two series use different units and different baselines, and NetBlocks' reference period is not reported. The gap would mean the bot hosts sat mostly in the damaged facilities only if they sat mostly in Sasovo and Kaluga, a point the sources do not test.

Reach is the weaker half of the claim. None of the reporting shows a change in global traffic. Cloudflare's figure describes requests from the Yandex network ^[2].

Dependency is better documented. Yandex Cloud's status page lists at least 84 services offline ^[6]. Runtimewire reports disruption from cloud computing to taxi bookings ^[3]. It also counts three data centers hit in four days ^[3], while the Tom's Hardware report names two, Sasovo and Kaluga ^[5][1], and neither identifies the third.

A site operator who watches Yandex-sourced requests vanish from its logs sees this series from the receiving side. With no Yandex recovery timeline in either report, the drop gives that operator no way to know when the requests return.