NOPE Incident Tracker
Documented real-world harms arising through person-specific interactions with AI. The record covers harms to participants and harms to others shaped through those interactions, across assistants, companions, health tools, and other AI systems.
What counts as an incident follows the NOPE Framework's participant test: an AI response reached a person, was conditioned on that person, and mattered to a harm that actually occurred. Full inclusion criteria.
90 incidents reported since 2016
152
Directly Affected
30
Lawsuits
7
Regulatory
24
Affecting Minors
Timeline
2 of 90 incidents
Mount Shasta climb planned with Google Gemini: night stranding, knee injury and rescue (Siskiyou County, California)
Three novice hikers from Roseville, California, planned a Mount Shasta summit attempt with Google's Gemini, which the Siskiyou County Sheriff's Office said advised them to carry far less food and water than their group needed for what became a multi-day ordeal. After reaching the summit at 7 p.m. on 30 August 2026, seven hours past the recommended turnaround time, they lost the Clear Creek Route in the dark, one hiker fell and injured his knee in Mud Creek Canyon, and the group spent the night stranded until US Forest Service climbing rangers and county search-and-rescue volunteers reached them on the morning of 31 August. The sheriff's office called the reliance on Gemini 'a critical misstep'.
Delayed emergency care for a transient ischemic attack after ChatGPT reassurance (GZO Hospital Wetzikon, Switzerland)
A 63-year-old man who developed repeated, self-limiting episodes of double vision four days after a catheter ablation for atrial fibrillation asked ChatGPT (GPT-3.5) whether visual disturbance was possible after the procedure. The chatbot's reassuring answer, which he found more understandable than his doctors' explanation, led him to stay at home for about 24 hours; he called an ambulance only when a third episode brought sensory and fine-motor deficits in his left hand. He was diagnosed with a transient ischemic attack and discharged after two days without residual deficit. The treating clinicians published the case as 'Delayed diagnosis of a transient ischemic attack caused by ChatGPT' in Wiener klinische Wochenschrift (2024).
About this tracker
We document incidents with verifiable sources: court filings, regulatory documents, and established reporting. New public entries must be verified or credible. Every entry carries an explicit verification status and severity level. Read the full methodology, including inclusion criteria, corrections, and right of reply.
Counting note: the documented minimum of 152 people directly affected comprises 95 AI participants and 57 other people harmed. 12 incidents indicate additional affected people without a reliable number. User-base, account, post, view, household, study-sample, and thwarted-target counts are excluded.
Have documentation of an incident we should include? Contact us.
Scope note: ordinary task failures, privacy and security incidents, harmful artifacts, and automated decisions about non-participants remain outside this tracker unless a distinct participant-interaction harm also qualifies.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.
Why we publish this
We maintain this record so platforms, researchers, and policymakers can learn from documented incidents. That includes platforms that never work with us. The full dataset is free to cite and export (CC BY 4.0).