CloudflareLai Yi OhlsenIncident / postmortem
Yandex outage: Data shows that instead of going dark, malicious bots went on the move
Summary
Reported drone strikes on Yandex data centers from October 7 to 11 caused network traffic to drop 99% below baseline for Yandex Search and 90% for Yandex.Cloud. Using Cloudflare Radar and Bot Management data, the analysis compared pre-event automation baselines with post-strike patterns on both ASNs. The Yandex Search ASN drop consisted almost entirely of verified search crawlers: 93.6% of its bot requests were verified, and 78.1% belonged to YandexBot. On Yandex.Cloud, vulnerability scanning fell 90% and plugin probing dropped 93%, but high-volume operations migrated to other Russian hosting providers, preserving identical JA4 fingerprints. Global bot traffic remained stable at 39.5%, demonstrating that malicious automation moves rather than disappears and that request behavior analysis is necessary to understand threats.
Context
The post analyzes the impact of reported drone strikes on Yandex data centers on malicious bot traffic, using Cloudflare Radar and Bot Management data to compare traffic patterns on Yandex Search (AS13238) and Yandex.Cloud (AS200350) before and after the strikes.
Approach / What changed
The post uses Cloudflare Radar and Bot Management data to examine request behavior, JA4 fingerprints, and industry segments on two Yandex ASNs, comparing pre-event baselines with post-strike patterns to determine whether malicious automation was disrupted or merely relocated.
Takeaways
The Yandex Search ASN traffic drop was almost entirely verified search crawlers (93.6% verified), not malicious bots; the main impact was reduced content discovery in Yandex Search.
Malicious automation from Yandex.Cloud migrated to other Russian hosting providers like Radist and Selectel within hours, maintaining identical JA4 fingerprints, request paths, and User-Agent strings.
Global bot traffic levels remained stable at around 39.5% of HTTP requests, indicating that network disruptions do not eliminate automated threats and that request behavior analysis is necessary.
FAQ
Did the strikes disrupt Russian bot operations?
No, malicious bots simply migrated to other networks. While vulnerability scanning temporarily dropped on Yandex.Cloud, high-volume operations quickly moved to alternative hosting providers like Radist and Selectel, and global bot traffic remained flat.
How did Cloudflare distinguish search crawlers from malicious bots?
Cloudflare classified 99.5% of Yandex Search ASN requests as automated, with 93.6% verified as legitimate crawlers like YandexBot. In contrast, none of Yandex.Cloud's bot requests were verified, and they exhibited behavior like vulnerability scanning and plugin probing.
What evidence shows bots migrated to other providers?
Identical JA4 TLS client fingerprints, uncommon request paths, and custom User-Agent strings appeared from other Russian ASNs like Radist and Selectel immediately after Yandex.Cloud traffic dropped, particularly targeting gambling sites.
Source and freshness
- Source
- blog.cloudflare.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.