
Open repository cataloging real-world AI harms and failures.
By Tanmay Verma, Founder · Last verified 03 Jul 2026
In short
Aiid — Open repository cataloging real-world AI harms and failures. Best for AI safety researchers studying failure patterns across domains, Developers auditing their own AI systems against known harms, Policy analysts drafting AI regulation or guidelines. Free to use.
See what real users actually say. We scan live discussions, reviews and complaints across the web and hand you an honest verdict — in under a minute.
3 free scans · no card needed · downloadable report
If you're serious about AI safety, the AIID is an essential reference. It's free, open, and constantly updated. But don't expect real-time alerts or automated analysis—it's a manual research tool, not a monitoring system.
Compare with: Aiid vs WolframAlpha, Aiid vs Paxton AI, Aiid vs Goodfire
Last verified: July 2026
Across the latest 4 updates: 4 news mentions.
AIID blog post on corporate and government roles in AI safety ecosystem.
Quarterly roundup of new AI incidents added to the database.
Roundup of incidents from Nov 2025 to Jan 2026.
First post in a series on AI Incident Database funding.
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
5 mentions across 1 source (Lemmy).
How likely is Aiid to still be operational in 12 months? Based on 4 signals — momentum (how recently it shipped), wrapper dependency, revenue model, and web presence.
Last calculated: July 2026
How we score →The AI Incident Database (AIID) is a free, community-driven public repository that systematically collects, classifies, and shares reports of real-world incidents where AI systems have caused or contributed to harm. With over 1,500 entries—from autonomous vehicle fatalities to algorithmic bias and AI-generated hallucinations in legal filings—it serves as a collective memory for the AI ecosystem. It's built for researchers, developers, product managers, policymakers, and journalists to understand failure patterns, conduct risk assessments, and inform regulation. The platform offers multiple ways to explore incidents: a table view for sorting, a spatial map for geographic trends, entity and taxonomy filters, and a random incident feature. Users can submit new incident reports, which undergo editorial review. The database is open-source, governed by the Responsible AI Collaborative, and funded through donations and grants. All features—including dataset downloads, API access, and the blog with curated roundups—are free and require no registration. Recent additions (as of June 2026) include incidents involving AI-generated hallucinated citations in a KPMG report, the use of Grok to create child sexual abuse material, and alleged price coordination via AI at California gas stations. The database continues to grow, with quarterly roundups and guidance for corporations and governments. Unlike commercial risk assessment tools, the AIID is a historical archive, not a real-time monitor. Its strength lies in breadth and openness, but incident report quality varies with source credibility. It complements active safety testing by providing a reference library of past failures.
The AI Incident Database is a public good in the truest sense. It's one of the few places where you can browse a curated, searchable archive of AI failures—from self-driving car crashes to generative AI hallucinations. We'd reach for this when auditing a system against known failure modes, researching regulatory trends, or teaching AI ethics. The new incident about KPMG's hallucinated citations is a stark reminder that even professional services firms aren't immune. Where it bites: the database is only as good as its submissions. Some incidents are well-sourced news reports; others are single-sourced or lack technical depth. You'll need to cross-check critical findings. Also, there's no real-time alerting—you visit the site or subscribe to the newsletter; you don't get pushed notifications. Compared to vendor-specific risk databases (e.g., those from Credo AI or Fairnow), the AIID is broader but less structured. It's ideal for pattern recognition across domains, not for compliance audits against a specific regulation. The API and full dataset download make it useful for researchers who want to run their own analyses. In practice, we'd use it alongside active testing tools. It won't catch the next vulnerability, but it will remind you that every failure has happened before.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Common stack mates teams adopt alongside Aiid, with the specific reason each pairing earns its keep.
Used Aiid? Help shape our editorial sentiment research.