Russian Bot Collapse

The most-shared claims, and what public sources can confirm. Tap the link icon to share a single claim.

People who spread the "bots went silent" story and have since taken it back, and the fact-checks that tested it. Newest first. We add to this list as corrections appear.

Fact-checks so far (October 12–13): Capital, Rohtext, BR24 #Faktenfuchs, netzpolitik.org, FAZ and ZDFheute (Germany), Novinky.cz (Czech Republic), Interia and Niebezpiecznik (Poland), Libération CheckNews (France), Euronews, The Verge, RFE/RL The Independent, BBC Verify, The Guardian and Mother Jones. None found evidence that Russian influence operations went quiet.

Not corrected as of October 13: Tom's Hardware's "bot traffic nearly eliminated" article (headline and date unchanged); Polish Minister Tomasz Siemoniak's statement that the ABW saw Russian bot traffic "practically stop" (no data released); and Ukraine's Center for Strategic Communications' post sharing the AfD chart.

New reporting from major outlets and official sources, listed as it appears. Our monitoring adds headlines from major outlets automatically. "Checked" means our software fetched the full report and confirmed it supports its headline. "Reviewed" means an editor checked it against its source. "Auto" items have not been checked yet. Tap a label for our note. None of this is an endorsement. Our assessment is the rating above.

• 14 Oct, 1:58 PM
  reviewed ▾

  Our note: X's own announcement; it gives no dates or per-country counts.An editor checked this report against its source. (2026-10-14)
  X suspends 13,000+ accounts in three suspected foreign influence operations (Iran, Russia, China) (X Global Government Affairs)
• 14 Oct, 11:23 AM
  checked ▾

  Our software fetched the full report and confirmed it supports its headline. Not yet reviewed by an editor. (2026-10-14)
  Government Says It Helped Yandex Migrate Systems After Data Center Attacks (The Moscow Times)
• 14 Oct, 8:00 AM
  reviewed ▾

  Our note: Russian-language report on the strikes' economic fallout: outages at Yandex's payment and banking services, disruption to banks and taxis, and supercomputers at the sites hit. It does not address bot or troll activity.An editor checked this report against its source. (2026-10-14)
  «Яндекс», банки, такси: что еще рухнет после атак ВСУ на дата-центры (Yandex, banks, taxis: what else will collapse after Ukraine's strikes on data centers) (TV Rain (YouTube))
• 14 Oct, 4:30 AM
  reviewed ▾

  An editor checked this report against its source. (2026-10-14)
  Ukrainian Drones Hit Sberbank Data Center After Yandex Attacks (The Moscow Times)
• 13 Oct, 5:00 PM
  reviewed ▾

  Our note: Graphika tested the viral claims against its maps of thousands of communities and public Reddit counts: no notable change in the AfD, MAGA or Reform UK communities; the clearest declines were in Russian-speaking spaces.An editor checked this report against its source. (2026-10-13)
  Did the Yandex Data Center Strikes Silence Russian Bots? What the Data Shows (Graphika)
• 13 Oct, 2:28 PM
  reviewed ▾

  Our note: Fact-check (German): no evidence bots went quiet; Zdechovský says he has no independently verifiable data; CeMAS sees no drop.An editor checked this report against its source. (2026-10-14)
  Angriffe auf russische Rechenzentren: Fake-Bots weiter aktiv (ZDFheute)
• 13 Oct, 1:31 PM
  reviewed ▾

  An editor checked this report against its source. (2026-10-13)
  No, Ukraine's strikes on Yandex data centers didn't cripple Russian influence ops (The Kyiv Independent)
• 13 Oct, 1:07 PM
  reviewed ▾

  Our note: Mother Jones: researchers see no evidence the strikes silenced Russian bot or troll networks; examines why the claim spread.An editor checked this report against its source. (2026-10-13)
  Drone strikes didn't take out a Russian bot farm, but we were primed to believe it (Mother Jones)
• 13 Oct, 11:13 AM
  reviewed ▾

  An editor checked this report against its source. (2026-10-13)
  Angriffe auf Yandex: Ukraine legt „russisches Google“ lahm (FAZ)
• 13 Oct, 11:13 AM
  reviewed ▾

  An editor checked this report against its source. (2026-10-13)
  Did Ukrainian strikes on Russian datacentres reduce online disinformation? (The Guardian)

All 128 sources →

Anecdotes ("everyone noticed") and the Cloudflare chart cannot move this rating. Any one of these could:

• not seenA platform report. X, Meta, TikTok, Google or OpenAI reports a decline in, or takedown of, a named Russian operation and ties it to the Yandex outage.
• not seenPosting data with controls. Independent researchers publish before-and-after counts for known influence-network accounts showing a drop timed to the strikes, checked against normal weekly swings.
• not seenInfrastructure attribution. A credible report that a named operation (Doppelgänger, Storm-1516, Matryoshka, the "Pravda" network) ran on Yandex Cloud, YandexGPT or other Yandex hosting.
• not seenPersistence. If a drop is documented, whether it lasts once Yandex dependencies are replaced or re-routed. Operations that relied on a Yandex tool can switch providers quickly.

• Three Yandex data centers were hit. Sasovo in Ryazan region overnight on October 7–8, which houses two of Yandex's three AI supercomputers (Reuters, Meduza); Kaluga, its largest, on October 9 (Reuters); and Vladimir on October 11, where Yandex said operations were "completely suspended" (Al Jazeera). The strikes followed Russian attacks on Ukrainian data centers since late September.
• The disruption is real. More than 80 Yandex Cloud services were affected (Kyiv Post), along with ride-hailing, payments, food delivery and chatbots, including Yandex Go outages in five other countries (RFE/RL). Banks, retailers and Russian Railways reported outages (Ars Technica). As of October 12 Yandex was still restoring capacity, and NetBlocks saw "no signs of recovery" (NetBlocks).
• The viral chart measures web requests, not social-media posts. Cloudflare Radar's "bot traffic" counts HTTP requests that Cloudflare scores as "likely automated" (Cloudflare docs). For Yandex's network that is mostly YandexBot, Yandex's search-engine crawler. Cloudflare's own posts describe the drop as "traffic" from Yandex's network and say nothing about bots or social media (Cloudflare Radar).
• Posting data from known networks shows no sustained drop. Researchers at dTeam, a US-based group that tracks Moscow-linked influence operations, told BBC Verify they had seen no "traffic change from known Russian accounts and bot clusters on any platform" (BBC). Valent, a company that tracks about 40 disinformation networks, said there was “no discernible change in their posting patterns” (The Guardian).
  • Matryoshka (fake news videos on X): 8 to 10 videos a day from October 5 to 9, through the first two strikes. On Monday, October 12, it posted 5, about half the usual, but earlier Mondays looked the same (see the strongest case). Its accounts were still active on October 13 (BBC).
  • Storm-1516: accounts still active on October 13 (BBC). David Colon of Sciences Po says the reach of affiliated accounts "fell significantly" over the weekend; he has not published the data (Colon).
  • The "Pravda" network (automated news sites): normal pace through the Sasovo and Kaluga strikes; about half its usual output for roughly 13 hours after the Vladimir shutdown, then recovered (chart). Ukraine's Center for Countering Disinformation reported the same (CCD).
  • InfoDefense (Telegram): the CCD reported its output halved for about 12 hours (CCD); five of its public Telegram channels that we checked showed no dip and were busier than usual after the Vladimir strike.
  • "Nod of Time": the CCD reported a similar dip (CCD); we have not checked it.
  • Other pro-Kremlin Telegram channels: 10 that we checked did not slow.
  • Pro-Russian accounts on Polish X: Res Futura Data House, a European analytic collective that tracks about 500 such accounts, found normal activity through the strikes (Res Futura); on October 13 the network's hourly activity was up 45% on the day before (Res Futura). NASK, Poland's state cybersecurity research institute, found no significant decline among the Russian disinformation accounts it monitors on X (Interia).
  • German-speaking TikTok, Telegram and X: the think tank Polisphere, monitoring almost 10,000 such accounts, found no statistically noticeable decline (Capital).
  • Pro-Russian posts on Japanese X: Kazuki Ichida, a visiting researcher at Meiji University's Cybersecurity Research Institute, counted them daily through the X API with control series. In the five days after the first strike they ran at 1.21 times the previous two weeks' level on a narrow definition and 1.03 times on a broad one, while all Ukraine-related posts rose 1.20 times; posts about Yandex and Russian bots meanwhile jumped from under 100 a day to more than 10,000 on October 10 (Ichida, in Japanese).
  • VKontakte, inside Russia: pro-government bots left about 2,000 comments on the strikes in the four days after the first one, according to Botnadzor data analysed by the independent outlet Verstka: they praised air defense, played down the damage and, when outages could not be denied, told Russians it was a good time to look up from their phones (Verstka). The project covers VKontakte only.
  No platform report or wider dataset has shown a fall in coordinated inauthentic activity tied to the strikes. Our search covered English, Polish, Russian, German and Czech sources and X. That is a search result, not proof of absence.

Every chart in circulation that names its data source measures Yandex's own infrastructure. Each shows servers going dark, which is what you would expect from destroyed data centers.

There are real ways a Yandex outage could slow a Russian operation: Yandex mail, cloud hosting, its AI and speech tools, or its payment apps. Some Russian state media do depend on Yandex. RT, the video agency Viory and the pro-Kremlin site Anti-Spiegel route their email through it. And when a known dependency breaks, it shows: the sanctioned A7A5 stablecoin's transactions collapsed with the first strike (Elliptic).

But the evidence stops there. The web fronts of known operations that we checked (the "Pravda" network and a Doppelgänger fake-news site) are hosted elsewhere. No report ties YandexGPT, Yandex Cloud or Yandex Pay to a troll operation. The posting data is mixed in one telling way. Matryoshka posted 8 to 10 videos a day on X from October 5 to 9, through the Sasovo and Kaluga strikes, according to daily logs kept by volunteer researchers, and 10 pro-Kremlin Telegram channels did not slow. But the automated "Pravda" news network lost about half its output for 13 hours after the Vladimir shutdown, while its Telegram sources were busier than usual, then recovered. That is consistent with an automated pipeline that leaned on something in a Yandex data center and quickly routed around it. It is a website network, not social-media accounts, and we cannot see which part of it failed. Ukraine's Center for Countering Disinformation, a government body, said on October 13 that it found no evidence of "a significant overall decline" in Russian bot networks' activity, but that output from the Pravda, InfoDefense and "Nod of Time" networks fell by about half for around 12 hours before recovering (CCD). It published no data. Its Pravda finding matches ours; five of InfoDefense's public Telegram channels that we checked showed no such dip, and were busier than usual after the Vladimir strike. On Monday, October 12, the first weekday after the Vladimir strike, the logs show 5 videos from two accounts, about half the usual; David Colon of Sciences Po, who also tracks the operation, counted the same (Colon, in French). On October 13, after checking his own records, Colon found similar drops on September 3 and 14 (Colon). But the same thing happened on Monday, September 14, four weeks before the strikes: two accounts set up the Friday before posted five videos between them, and no new accounts appeared. Since mid-August, Mondays have run lower than other weekdays (a median of 7.5 videos, against 10), and three earlier Mondays (August 31, September 7 and 14) looked like October 12. So a half-size Monday is not unusual for this operation; the next two weekdays will show whether output stays low.

The closest precedent points the other way from this week's evidence, and shows what a real test looks like. During a two-hour, nationwide Russian internet outage in January 2024, researchers at the Brussels think tank Bruegel found that posts from 221 X accounts popular with pro-Kremlin networks drew about 49 fewer reposts per account in the peak hour than a control group and the day before. The authors called the results preliminary (Bruegel). That outage hit the whole Russian internet; this week's strikes hit three data centers belonging to one company.

The most specific example so far comes from David Colon, who teaches about propaganda at Sciences Po: a fabricated story from the Russian operation Storm-1516 about the French candidate Raphaël Glucksmann, launched October 9, drew only tens of thousands of views in its first three days, while one the network launched on September 24 drew millions in the same span (X). It compares two stories, which can differ in topic, target and who picks them up, and the October 9 story came before the largest outage. It is worth testing across many stories.

What would make the case: posting or engagement counts for known network accounts that dip after all three strikes, more after the biggest outage, and not just on weekends. We will add such data here if it appears.

It is easy to see why the claim spread. The strikes are a real blow to Russia's largest technology company, and many people want them to have hurt the Kremlin's online operations too.

But believing it before the evidence is in has costs. If people think the troll farms have gone quiet, Russia's operations can carry on with less scrutiny. Policymakers, platforms and the public come away with the wrong picture of how these operations work: as servers that can be bombed, rather than paid people and contractors spread across many countries and tools. And a misread chart, repeated by officials and newsrooms, becomes faulty intelligence. It distorts judgments about what the strikes achieved and what still needs doing.

Ukraine and its supporters need accurate situational awareness more than good news. The strikes' documented effects, on Yandex's services, on payments and on a sanctioned stablecoin, are real and significant. Claiming effects the evidence does not show only makes the real ones harder to see.

• October 11, afternoon (UTC): Tom's Hardware publishes the Cloudflare figures under a "bot traffic" headline. Screenshots of the Cloudflare chart spread with captions about troll farms.
• October 11, evening: Zdechovský's chart (55,900 likes on X) and Wolski's "56%" post (43,800 likes) carry the claim to German and Polish politics. Antibot4Navalny posts the first detailed rebuttal two hours later.
• October 12: President Zelensky repeats the claim at the Warsaw Security Forum. UNITED24, Ukraine's state media platform, runs "Russian Bots Went Silent," though its own article says the data does not establish an effect. RFE/RL, The Verge and Euronews publish pieces questioning the evidence.

• Tom's Hardware reported Cloudflare's numbers accurately but framed them as "Russian bot traffic" and wrote that "the world is getting a break from Russian bots," without explaining that the traffic is mostly a search crawler.
• Tomáš Zdechovský, a Czech member of the European Parliament, posted the unsourced "AfD" chart with the caveat "If confirmed, this is telling."
• Jarosław Wolski, a Polish defense analyst, said AfD support online "fell 56%." On October 13 he apologized, said the chart was AI-generated and that no lasting, measurable drop in pro-AfD posts had occurred, and said he had deleted the post (Wolski).
• President Volodymyr Zelensky said "there were fewer bots" and "it's pretty clear where those bots were coming from" (RFE/RL). He did not cite data.
• Tomasz Siemoniak, Poland's minister coordinating the intelligence services, said Russian bot traffic had "practically stopped" worldwide, citing the ABW; no data was released (Rzeczpospolita).
• Mindaugas Sinkevičius, Lithuania's prime minister, asked at the Warsaw Security Forum on October 12 how allies should protect their elections from interference, said "we should ask Mr Zelensky to strike more data centres in Russia, and that might help" (LRT). Zelensky, speaking at the same forum, said that once the strikes began "it suddenly became a little easier to breathe on many social media platforms" (AFP via Malay Mail). The reports quote no data behind that. Repsense, a Vilnius company that sells narrative monitoring to governments, posted a chart on October 13 showing that posts its software rates as high-risk pro-Russian content on Lithuanian social media did not fall in the week of the strikes. They rose from a pre-strike average of about 1,400 a day to about 2,500 on October 10, continuing a climb that began in mid-September. Its method is not published (Repsense).
• Theo Francken, Belgium's defence minister, endorsed Zelensky's post on October 13 ("This.") and on October 12 shared a post claiming that "genocide" and "Free Palestine" were trending down on X after the strikes (see claim), asking whether that trend had been "a Russian/Chinese psyop" (Francken, Francken; translated from Dutch). He cited no data.
• Rep. Sarah McBride (D-Delaware) joked on X on October 12, "Was a Russian data center just destroyed or are you just happy to see me?" (about 60,000 views), then wrote that "these bot farms are engaging in psychological warfare" and called for Big Tech regulation to address foreign interference (McBride, McBride). Former Rep. Adam Kinzinger (R-Illinois) asked his 1.1 million followers on October 13, "Have you noticed fewer bots in your feed recently? Thanks to Ukraine, our social media mentions are a little less chaotic now" (Kinzinger). Neither cited data showing the strikes had affected them. Foreign influence operations are well documented; a drop after the strikes is not.
• Ukraine's Center for Strategic Communications (SPRAVDI), a government body, posted the AfD chart on October 12 as researchers' "initial conclusions" and said the strikes "coincided with a sharp decrease in bot traffic in Germany, France, Ukraine, and the United States" (StratCom). The chart is AI-generated (see the AfD claim).
• Jake Broe, a former Air Force nuclear and missile operations officer whose pro-Ukraine YouTube channel has more than 700,000 subscribers, posted a video on October 13 that strings together the viral claims rated above: collapsed bot traffic, the Reddit “80%” figure, falling views for Kremlin-friendly commentators, and collapsing online support for AfD and Reform UK. His caption: “It was all Russia. It was always Russia” (post). None of those claims holds up on the evidence above.

• Antibot4Navalny, researchers who track Russian bot and troll networks, told RFE/RL the chart "has little to do with malicious propaganda bots on social media. It measures automated requests to websites (of any kind, among which social media share is negligible)" (RFE/RL). On October 13 the group said it saw no "dramatic drop" in the activity of Kremlin-aligned trolls-for-hire targeting Russian domestic users, which it has tracked for years (Antibot4Navalny).
• Florian Roth, head of research at Nextron Systems: "Bot traffic from Russia does not automatically mean Russian propaganda bots… Where's the data showing that propaganda accounts stopped posting?" (X)
• Caroline Orr Bueno, behavioral scientist who studies online influence: “bot traffic” “measures automated requests from the Yandex search engine, not social bots or troll farm activity, and the data do not tell us anything about social media bots” (X).
• Social Media Lab at Toronto Metropolitan University, on October 11, the day the chart went viral: it shows YandexBot’s requests to websites, “not human users, political posts, likes, shares, comments, or engagement.” “Crawling, indexing, reach, and engagement are four different things” (Bluesky).
• Josef Holnburger, co-founder of the disinformation research center CeMAS: “We observe Russian campaigns. We see no drop in the number of postings that could be explained by an attack on data centers” (Capital, translated from German).
• Kate Starbird, professor at the University of Washington and co-founder of its Center for an Informed Public: charted X posts mentioning the AfD hour by hour from October 5 to 13, and minute by minute on October 7 and 10, when the first and third strikes hit. “I don’t see any significant decrease in X traffic around these times or during this period at all.” A small impact is “totally possible,” she wrote. “But the stories of a massive silencing of Russian bots making a qualitative difference on social media discourse… are very likely to have been (significantly) overstated” (Bluesky).
• Richard Schwenn, head of data analysis at the think tank Polisphere: in monitoring of almost 10,000 accounts, “neither the activity of existing bots has declined nor the rate at which new ones are created”; evidence of a drop is “at best anecdotal” (Capital, translated from German).
• Ilya Lozovsky, senior editor at the investigative network OCCRP, writing on his own account: the viral claims “have no basis in fact”; the evidence “doesn't prove that nothing happened. What it shows is that there's no proof that anything happened” (X).
• Euronews found the figures "include legitimate automated traffic, such as search-engine crawlers, and do not establish whether Kremlin-linked social media bots were affected," and that "no independently verified figures have emerged" on AfD (Euronews).
• Tom Robinson, Elliptic co-founder: A7A5's exchange moved to Yandex hosting after the stablecoin was sanctioned in August 2025, which left it "at the mercy of Ukrainian drone strikes" (X).
• Aric Toler, New York Times visual investigations reporter, writing on his own account: data supporting the idea that Russian disinformation operations are "flailing because of data center strikes" is "at best, anecdotal & coincidental" (X).
• Graphika, a network-analysis firm that tracks influence operations (analysis by founder John Kelly): assessed “with moderate confidence” that the strikes “did not silence accounts in the Western political communities viral posts named, including those around AfD, MAGA and Reform UK.” None lost its active accounts or heaviest posters. The clearest declines were in Russian-speaking spaces: Russian-language Telegram channels posted 5% to 15% less in the two days after the Vladimir strike, and r/askarussian fell after all three strikes. Graphika says its data does not show why; internet disruption inside Russia is one possibility. The claim itself circulated mostly among pro-Ukraine and NAFO accounts, which mentioned Yandex 101 times per 10,000 posts, against 4 or fewer in the communities it described (Graphika).

Research on Russian influence operations describes a decentralized business: scholars write of "entrepreneurs of influence" competing for Kremlin favor (Laruelle and Limonier, Post-Soviet Affairs, 2021) and of a disinformation labor market (Poliakoff and Kling, New Media & Society, 2026). Much of the work is done by people paid to meet quotas: the Senate Intelligence Committee documented Internet Research Agency staff with daily targets for posts and comments (Senate report, Vol. 2), in an operation researchers called "industrial" (Linvill and Warren, Political Communication, 2020). Some of it runs outside Russia: in 2020 an operation linked to former IRA associates paid people in Ghana to post for American audiences (Graphika). The trade also runs on plain profit: Leslie Iwerks' documentary Selling Lies follows young people in North Macedonia who earned large sums in 2016 running fake political news sites aimed at American readers (Selling Lies). Human-run accounts are hard to tell from real users; even research tools built to detect bots misclassify in both directions (Rauchfleisch and Kaiser, PLOS ONE, 2020). Operations that used a Yandex service, such as payments, translation or the YandexGPT model, would lose it for a time. Swapping in another provider, or a model run on their own machines, is usually quick.

That is why the data that matters is posting data from known networks. Traffic from a search company's servers cannot tell us whether those networks went quiet. The contrast is the point. Russia's domestic digital economy runs through a few large Yandex data centers, which is why the strikes did real damage there (Ars Technica). Influence operations are spread across many countries, contractors and tools.

• Posting-volume data from researchers who track named Russian networks.
• Platform statements or takedown reports from X, Meta, TikTok, Google or OpenAI.
• Whether any reported "quiet" ends as Yandex dependencies are replaced or re-routed.
• Further strikes on Russian data centers, and Russian strikes on Ukrainian ones.

• Sept. 23 onRussian strikes damage data centers of at least eight Ukrainian companies (Meduza).
• Oct. 7–8Drone strike and fire at Yandex's Sasovo data center. Yandex Cloud traffic falls about a third (Cloudflare Radar). A7A5 transactions collapse.
• Oct. 9Kaluga data center partly knocked out.
• Oct. 11Vladimir data center shut down around 00:30 UTC. Tom's Hardware publishes its "bot traffic" story; Zdechovský and Wolski post the AfD claim; Antibot4Navalny posts a rebuttal.
• Oct. 12Zelensky repeats the claim in Warsaw. RFE/RL, The Verge and Euronews question the evidence. America 2.0 opens this tracker.

If you have a validated study, a news report or credible analysis that measures Russian online activity before and after the Yandex strikes, email us at editor@america2.news with the subject “Russian Bot Tracker.” Posting or engagement counts for known network accounts are the most useful. Please include a link and say how the data was gathered. We check each submission against its source. If it holds up, it goes on this page, whichever way it points.

• RFE/RL: Zelenskyy Says Yandex Strikes Crippled Pro-Kremlin Bots But Tech Experts Question Evidence
• The Verge: Did "Russian bot traffic" really disappear after Ukrainian strikes on Yandex servers?
• Euronews: Did Ukrainian strikes on Yandex data centres cause Russian bot activity to plummet?
• Cloudflare Radar: how "bot" traffic is classified
• IODA (Georgia Tech): Yandex Cloud network signals