Artificial Intelligence Policy Tracker

AI Incident Database

Browse AI incidents

Every incident record (metadata only) from the weekly snapshot of 2026-09-07. Filter, then export the selection with its licence attached; each row links to the full record and its reports.

Filter incidents (1 active)

Two-letter code, e.g. US

Reset

179 incidents · page 8 of 8

  1. #452 · 2 reports

    ChatGPT-Written Bug Reports Deemed "Nonsense" by White Hat Platform, Prompted Bans AIID ↗

    ChatGPT-generated responses submitted to smart contract bug bounty platform Immunefi reportedly lacked details to help diagnose technical issues, which reportedly wasted the platform's time, prompting bans to submitters.

    Deployer: Openai, Immunefi Users · Developer: Openai · Harmed: Immunefi

  2. #549 · 1 report

    Fast Food Chains' AI Chatbots Failed to Assist Job Applicants with Scheduling Interviews AIID ↗

    McDonald's, Wendy's, and Hardee's AI chatbots deployed to pre-screen job candidates and schedule interviews reportedly ran into issues such as not giving useful submission instructions, failing to relay information to the manager, and scheduling an interview when the manager was not available.

    Deployer: Wendy'S, Mcdonald'S, Hardee'S · Developer: Wendy'S, Mcdonald'S, Hardee'S · Harmed: Fast Food Job Applicants, Amanda Claypool

  3. #453 · 1 report

    Twitter's AI Moderation Tool Misidentified Rockets as Pornography AIID ↗

    Twitter's automated content moderation misidentified images of rocket launches as pornographic content, prompting incorrect account suspensions.

    Deployer: Twitter · Developer: Twitter · Harmed: X (Twitter) Users

  4. #446 · 5 reports

    ShotSpotter Failed to Alert Authorities of Mass Shooting in North Carolina AIID ↗

    ShotSpotter did not detect gunshots and alert Durham police of a drive-by shooting in Durham, North Carolina which left five people in hospital on New Year's Day.

    Deployer: Law enforcement, Durham Police Department · Developer: ShotSpotter · Harmed: mass shooting victims, Law enforcement, Durham residents, Durham Police Department

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.

Frequently asked questions

What is recorded in each incident?

What happened, when, who was involved as developer or deployer, who was harmed, the sectors and countries affected, and the domain and subdomain the harm falls under. Incidents are mirrored from the AI Incident Database and each links back to its source record.

Does an incident mean wrongdoing was proven?

No. These are reported incidents, not findings of liability. Entities named in a report are named as reported, allegations are marked as alleged, and nothing here is a legal determination.

How current is the incident data?

It syncs directly from the AI Incident Database several times a day, so a new incident usually appears within hours. Each record carries the date it was last synced, and the snapshot date is shown on the page.

Does this page include the full incident reports?

No. The report texts are outside the licence this data is shared under, so only the metadata and the classifications appear here. Every row links to the original incident record, which carries the reports themselves.