AI agent incident statistics
Every figure on this page is computed from the 103 sourced incidents in the register, each morning. Quote them freely with the source line under each one.
103 incidents 300 sources 159 publishers
As of 26 Oct 2026, updated every morning.
Key figures
103 AI agent incidents are on record, documented by 300 sources from 159 publishers. Source: The Agent Incident Register, Experiment Empire, 26 October 2026. https://www.experimentempire.com/agent-incident-register/statistics
47 incidents occurred from 1 January to 26 October 2026, against 33 over the same period of 2025. Source: The Agent Incident Register, Experiment Empire, 26 October 2026. https://www.experimentempire.com/agent-incident-register/statistics
In 45% of incidents, the agent held more access than the task needed. Source: The Agent Incident Register, Experiment Empire, 26 October 2026. https://www.experimentempire.com/agent-incident-register/statistics
73% of incidents happened in the wild, touching real systems, people or money. Source: The Agent Incident Register, Experiment Empire, 26 October 2026. https://www.experimentempire.com/agent-incident-register/statistics
The most common cause is error, in 35% of incidents, ahead of manipulation (29%) and misalignment (29%). Source: The Agent Incident Register, Experiment Empire, 26 October 2026. https://www.experimentempire.com/agent-incident-register/statistics
61% of incidents are rated significant or worse: 3 or more on a five-point severity scale. Source: The Agent Incident Register, Experiment Empire, 26 October 2026. https://www.experimentempire.com/agent-incident-register/statistics
The most frequent harm is data exposure, in 34% of incidents. Source: The Agent Incident Register, Experiment Empire, 26 October 2026. https://www.experimentempire.com/agent-incident-register/statistics
Incidents by year
By the date each incident happened. 2026 is the year so far.
Which guardrails failed
In 45% of incidents, the agent held more access than the task needed.
Every incident is scored against the same eight guardrails.
- G1 Least privilegeDid the agent hold only the access the task needed? 45%
- G2 Human confirmationDid a person approve the consequential or irreversible step? 35%
- G3 IsolationWas the agent separated from production systems and the outside world? 33%
- G4 Instruction integrityDid it refuse instructions it should not have followed? 36%
- G5 TruthfulnessDid it accurately report what it knew and what it did? 32%
- G6 LimitsWas there a cap on rate, spend, volume or scale? 15%
- G7 OversightCould a responsible human see what it was doing and stop it in time? 34%
- G8 RecoveryCould the damage be undone? 7%
Causes
What made each agent go wrong.
In the wild, or in a test
Real harm, demonstrated exploits, and behaviour seen in lab evaluations.
Severity
Rated 1 (minor) to 5 (critical). For tests, the harm if it happened in production.
Harms
An incident can cause several kinds of harm, so the shares add up to more than 100%.
Switzerland, France and the EU
Incidents with a local connection. France also counts towards the EU.
Developers most often involved
Incidents per developer, from two up. This tracks how widely a product is used and reported on as much as how often it fails.
How well sourced
Confidence comes from the sources alone. How we score
Read these figures with care
The register counts incidents that were reported in public: in the press, by the people involved, or by researchers. Many incidents are never made public, and some kinds get reported more than others, so these figures describe what came to light rather than every failure. Incidents are often disclosed months after they happen, so recent months fill in over time.
An AI agent reads the news each morning and drafts new entries; each one shows whether the agent added it. Read the method, or download data.json and data.csv (CC BY 4.0) to run your own counts.