Cloudflare Publishes Yandex-Outage Analysis: Search-Crawler Traffic Fell, Yandex.Cloud Automation Moved to Other Russian Hosts, No Social-Media Shift Seen in Its Data

Date kind: publication date of Cloudflare’s post (page metadata, 2026-10-14 20:24 UTC), not the strike dates (see 2026-10-08–yandex-three-data-centres-knocked-out-by-drones-oct-8-11-reuters).

What the text says, bound to Cloudflare’s wording. Two Yandex ASNs, two different pictures. The 99.5% automated figure belongs to the search-engine ASN (AS13238), where the drop was almost entirely verified search crawlers; the cloud ASN (AS200350) was about 95% bots, unverified, and supplied about 2% of Russia-origin bot requests and 0.01% of the global total. Cloudflare’s gambling-customer case shows one workload moving from Yandex.Cloud to other Russian hosts the day of the Oct 8 disruption, with an unchanged fingerprint. Its social-media endpoints check found no unexpected shift, with the stated limit in c7.

Limits: this is Cloudflare’s own analysis of its own network; the post lists no author. The post’s text gives a pre-event baseline of 36.1% automated (global) and 35.8% (Russia), which differs from figures in its own table; the discrepancy is unexplained in the post. Cloudflare does not attribute the migrated traffic to any actor (“it does not necessarily tell us who is responsible”).