AIIncidentTracker
Transparency

How we operate, in numbers

We publish quarterly statistics so anyone using our data — compliance teams, plaintiffs' lawyers, journalists, researchers — can evaluate our editorial process the same way they'd evaluate a news desk. These numbers are auto-generated from our internal audit log. Nothing is hand-edited.

Updated daily · May 25, 2026

All-time

Incidents indexed
30
Source citations
66
Primary sources
10 (15%)
Jurisdictions covered
22
AI system types
9
Earliest incident
2024

2026-Q2 · this quarter

Incidents added
13
Re-verifications
28
Status changes
2
Corrections issued
0
Retraction rate
0.00%
Avg time-to-verify
609h
Source uptime
99.7%
Takedowns honored
0 / 0

Trailing four quarters

QuarterAddedRe-verifiedStatus changesCorrectionsRetractionsSource uptime
2026-Q2132820099.7%
2026-Q112230099.7%
2025-Q41000099.7%
2025-Q32020099.7%
Sourced & verified

Every incident requires at least one primary or secondary source. We HEAD-check every source URL every 6 hours and fall back to an archived copy when an upstream goes dark.

Methodology
Open audit trail

Every status change, severity update, and re-verification writes a row to an append-only audit table — including who made the change and why.

Editorial standards
Visible corrections

When we get something wrong, the correction appears on the incident page, dated, alongside the original text. We never silently edit.

Corrections policy
Takedown handling

We honor narrow legal-removal requests (defamation, court-ordered redaction, GDPR Article 17). Quarterly totals are published in this report.

Removal-request form

Numbers update hourly via our editorial audit cron. See system status for ingestion cadence and live source health.