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

3 incidents

  1. #290 · 3 reports

    False Negatives for Water Quality-Associated Beach Closures AIID ↗

    Toronto’s use of AI predictive modeling (AIPM) which had replaced existing methodology as the only determiner of beach water quality raised concerns about its accuracy, after allegedly conflicting results were found by a local water advocacy group using traditional means.

    Deployer: Toronto City Government · Developer: Toronto Public Health · Harmed: Sunnyside Beachgoers, Marie Curtis Beachgoers, Toronto Citizens

  2. #140 · 1 report

    University of Toronto's ProctorU Deployment Reportedly Disadvantaged BIPOC Students During Exam Check-Ins AIID ↗

    University of Toronto students reported that ProctorU and other online exam-monitoring services created discriminatory and stressful check-in experiences for BIPOC students during remote exams. One U of T student said ProctorU's identity-verification process often failed to recognize her passport, forcing manual checks and consuming exam check-in time. ProctorU said human proctors made final identity and integrity decisions.

    Deployer: University Of Toronto · Developer: Proctoru · Harmed: University Students, University Of Toronto Students, Students, Educational Communities, Students Of Color

  3. #63 · 1 report

    Google Photo Merge Decapitates Subject AIID ↗

    Google Photos' AI Assistant created a strange hybrid photograph when merging three different pictures from a ski trip.

    Deployer: Google · Developer: Google · Harmed: Alex Harker

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.