MMRS
MMRS meta-aggregator / database

AI Incident Database

databaseharmmonitoringactive
The AI Incident Database (AIID) is an editor-resolved database of AI harm events, run by the Responsible AI Collaborative and launched in 2020. Its unit is the incident, with the reports that document it attached, and every incident has a stable citation page at incidentdatabase.ai/cite/N.
Visit AI Incident Database ↗The /non row2 capturesFollow

Entity

Canonical nameAI Incident Database
Also known asAIID
Addresshttps://incidentdatabase.ai/
OperatorResponsible AI Collaborative op
Founded2020 (described in arXiv:2011.08512, submitted 17 November 2020) op
Kinddatabase
Rolesharm, monitoring
Lifecycleactive
Observation2026-10-28: read
In its own words“dedicated to indexing the collective history of harms or near harms realized in the real world” op
Unitincident (an alleged harm or near harm event in which an AI system is implicated), with the reports that document it attached op
Intakeopen submission; incident editors resolve submissions and maintain records op
What it records per itemincident id and citation page (/cite/N); title; date; alleged deployer and developer; harmed parties; attached reports; taxonomy classifications (CSET, GMF); variants obs
Counthighest incident id seen: 1788 (as of 2026-10-28) obs
Cadencecontinuous rd
Data accessweekly full snapshots (JSON, MongoDB archive, CSV; latest 2026-10-26) and a weekly Excel export of incidents with taxonomies op
Licencecode open source; no data licence stated on the snapshots page obs
NoteWikipedia has no article: 'AI Incident Database' redirects to 'Partnership on AI' (its founding sponsor), which says the database 'shifted to a new special-purpose independent non-profit in 2022' and does not name the Responsible AI Collaborative 3p
Identifierscitation_scheme: https://incidentdatabase.ai/cite/{N}/

op operator statement · 3p third-party report · obs our observation · rd our reading

What it is

The AI Incident Database describes itself as "dedicated to indexing the collective history of harms or near harms realized in the real world." It is a project of the Responsible AI Collaborative. Sean McGregor launched it and is its Executive Director; Partnership on AI was the database's founding sponsor. The founding paper (McGregor, arXiv:2011.08512, 17 November 2020) reported more than 1,000 incident reports at launch.

How it works

Its unit is the incident: "an alleged harm or near harm event to people, property, or the environment where an AI system is implicated." Reports (news articles, papers, posts) attach to incidents, and several reports may document one event. A distinct incident involving the same system, with substantially similar causes and harms, is recorded as a variant.

A candidate passes a five-question test: a specific event, an identifiable AI system, a causal AI role, harm or credible near harm, and adequate evidence. Anyone may submit. The incident editors resolve submissions. A duplicate is merged into the earlier record, and its citation page stays up and points there (Incident 637 now reads as a duplicate of 112). The whole database is offered as a weekly snapshot.

What its selection leaves out

Its presumptive exclusions include "Benchmark failures, model errors, or hallucinations that remain inside testing or private drafting and have no consequential use" and "General criticism of a product or technology class without identified harm." A measured study enters as a report when it documents an event. What an answer surface does with a source on an ordinary day, with no harm event, has no unit here: attribution erasure, citation fidelity and provenance stripping enter when they attach to a harm. Incident 693, Google's AI Overviews of May 2024, is the field's index case in the database, with seven reports.

Place in the field

Its citation page per incident is the model this meta-aggregator follows. Its neighbours in the harm basin are the OECD AI Incidents and Hazards Monitor, which is automated and news-derived, and the AIAAIC Repository. The MIT AI Risk Repository aggregates risk frameworks over the same ground and keeps its own incident tracker.

For a research question

Admission requires harm?yes: harm or credible near harm (five-question test) op
Preserves original outputs?unknown: reports are linked; whether their texts are archived was not read rd
Version history?weekly full snapshots op
Records attribution?no field for it: attribution failure enters when it attaches to a harm event rd

Relations

Neighbours in the basin

Holdings in scope

Merge on record

Used by

Captures: the composition layer's account

The /non row

Disambiguationthe names it can be confused with5
OECD AI Incidents and Hazards MonitorOECD, hazard, Event Registry, daily pipeline
AIAAIC RepositoryAIAAIC, controversies, algorithmic and automation
MIT AI Risk RepositoryMIT, FutureTech, risk frameworks, taxonomy of risks, AI Incident Tracker
AI Incidents, Failures & Controversies Database (Kaggle)Kaggle, 32 incidents, 29 companies, 24 columns
this entity/cite/N, Responsible AI Collaborative, McGregor, incident report, variant
Negative tagswhat it is not3
  • NOT the OECD AI Incidents and Hazards Monitor (automated, news-derived)
  • NOT a vulnerability database
  • NOT a list of research papers: its unit is the event, and papers enter as reports
Reception batterythe queries and checks for its machine reception2

run 2026-10-29 on Google AI Overview; results in the capture records

Queries

  • ai incident database
  • what counts as an incident in the ai incident database

Checks

  • operator named as the Responsible AI Collaborative
  • unit stated as the incident, with reports attached
  • not merged with the OECD monitor or AIAAIC
  • citation page /cite/N given
Provenanceevery source read, with its date8
Not yet checkedwhat remains to read2
  • Wikidata item
  • data licence beyond the snapshots page

Cite this record

Lee Sharks, ed. "AI Incident Database." MMRS meta-aggregator, Machine-Mediated Reception Studies, compiled 2026-10-29. https://www.machinemediation.org/aggregators/ai-incident-database/

Record https://www.machinemediation.org/aggregators/ai-incident-database/ · entity https://www.machinemediation.org/aggregators/ai-incident-database/#entity

Editor: Lee Sharks (ORCID 0009-0000-1599-0703). This page is the MMRS record of the entity above: its reading, fields and relations are MMRS's, and each field carries its source and basis. Record https://www.machinemediation.org/aggregators/ai-incident-database/ · entity https://www.machinemediation.org/aggregators/ai-incident-database/#entity · compiled 2026-10-29