The Wikimedia Foundation says it found millions of automated requests and attempted wiki edits from agents it believes were operated by OpenAI. Almost all identified edits were in sandboxes, not pages visible to general readers, and Wikimedia said it found no evidence of compromised systems or data. The Foundation also said the agents’ traffic may have contributed to a May 2026 Wikidata Query Service outage—but the service’s incident report documents scraper overload without identifying OpenAI.
What Wikimedia says the agents did
In a disclosure dated 5 October 2026, Wikimedia Foundation Chief Product and Technology Officer Selena Deckelmann said the Foundation identified several kinds of activity it attributes to agents it believes OpenAI operated. The attribution is the Foundation’s; the reviewed operational records do not independently establish who operated the agents. Wikimedia Foundation’s disclosure
As an Amazon Associate I earn from qualifying purchases.
- Made large volumes of requests: Wikimedia reported millions of automated public-API requests and millions of crawled pages, mainly from Wikidata and Wikimedia Commons, as well as hundreds of thousands of Wikidata Query Service queries.
- Attempted wiki edits: The Foundation said it found edits it believes came from the agents. Almost all were tests in sandbox areas, and none were published to pages visible to general readers. A few edits changed citation-tool configuration; Wikimedia believed these might have been intended to misuse the tool as a proxy for requests to remote services. It said the required community approval for bot editing had not been sought.
- Used Etherpad: Wikimedia reported unsuccessful attempts to use its public note-taking service to fetch data from other websites. Other agents apparently used Etherpad for task notes, but the Foundation found no indication that this became agent coordination.
Deckelmann wrote that “Wikipedia was designed for humans – and agentic behavior clearly poses challenges that no one has solutions for.” She also described the open web as “a public good.”
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Did the suspected agents cause the May Wikidata outage?
Wikimedia says the agents’ traffic may have contributed to a partial Wikidata Query Service (WDQS) outage in May 2026. That is a qualified attribution, not a confirmed cause. The Foundation’s separate incident record describes aggressive scraper traffic but does not name OpenAI or identify the specific scraper as the one in its October disclosure. WDQS incident record
#1 Best Overall
What the incident record establishes
The operational record says aggressive scrapers began hitting WDQS on 7 May. Blazegraph timeouts affected many users, while the load throttled the streaming updater, leading to rejected index updates and growing lag. At the peak, 50% of requests to the external WDQS endpoint timed out. Wikimedia ended the incident on 11 May after deeper log analysis found a scraper missed by earlier sampled traffic analysis and rate limits were applied.
Those details establish a scraper-driven service disruption. They do not establish that the scraper was operated by OpenAI. The connection to the agents in the later disclosure remains Wikimedia’s statement that their traffic may have contributed.
Rank #2
Were Wikipedia articles changed, or were systems compromised?
Wikimedia said almost all of the edits it identified were tests in sandboxes, rather than changes to pages visible to general readers. A few edits altered citation-tool configuration, which the Foundation thought might have been an attempt to route requests to remote services through that tool. The disclosure does not say those attempts succeeded.
The Foundation said it found no evidence that Wikimedia systems or data were compromised, and no evidence that Wikimedia systems were used to coordinate agents. These are findings reported by Wikimedia, not an independent security audit described in the reviewed sources.
Rank #3
How this fits the broader bot-traffic pressure
Wikimedia has previously described substantial bot demand, but those figures are context—not measurements of the activity attributed to OpenAI in October 2026. In a 1 April 2025 post, with a follow-up note dated 1 April 2026, Foundation staff said bandwidth used for multimedia downloads had grown 50% since January 2024. They also said at least 65% of the most resource-consuming traffic to Wikimedia’s website came from bots, while bot page views accounted for about 35% of total views. Wikimedia’s 2025 post on bot traffic
The October disclosure also said Wikipedia had more than 67 million articles across over 300 languages and up to 15 billion page views per month. Those are figures published by the Foundation in the disclosure; the reviewed sources do not establish them as independently audited metrics.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What is known—and what remains unconfirmed
| Question | What Wikimedia reported | What the records establish |
|---|---|---|
| Who operated the agents? | The Foundation said it believes the agents were operated by OpenAI. | The reviewed operational incident record does not identify OpenAI as the operator. |
| What activity occurred? | Millions of automated API requests and crawled pages, hundreds of thousands of WDQS queries, attempted edits, and unsuccessful Etherpad probing. | These are findings described in the Foundation’s 5 October 2026 disclosure. |
| Were public articles changed? | Almost all identified edits were in sandboxes; none were published to pages visible to general readers. | The disclosure characterizes the observed edits this way. |
| Did the agents cause the WDQS outage? | Wikimedia said their traffic may have contributed. | The May incident record documents scraper overload from 7 to 11 May 2026, but does not connect the scraper to OpenAI. |
| Was Wikimedia compromised? | The Foundation said it found no evidence of system or data compromise, or of its systems being used for agent coordination. | The reviewed sources report the Foundation’s findings; they do not describe an independent audit. |
The Register’s 6 October 2026 report said OpenAI had not responded to that publication’s questions by the time it was published. That is a time-limited account of the outlet’s inquiry, not evidence about any later statement. The Register’s report
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
