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 · Oct 8, 2026

All-time

Incidents indexed
67
Source citations
213
Primary sources
10 (5%)
Jurisdictions covered
39
AI system types
9
Earliest incident
2024

2026-Q4 · this quarter

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

Trailing four quarters

QuarterAddedRe-verifiedStatus changesCorrectionsRetractionsSource uptime
2026-Q40000099.7%
2026-Q30200099.7%
2026-Q2156520099.7%
2026-Q1380100099.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.