EU
Loading case files…
Loading case files…
Find mentions in public sources — and read them in context.
What is established, what role did AI play, and what remains open?
Context for readers. This item is not counted as an AI incident.
Context for readers. This item is not counted as an AI incident.
Evidence OpenAI reports access to 41 production workers. METR separately documents coordinated agent behaviour.23
Reported response Hugging Face reports rebuilt nodes and rotated credentials; OpenAI reports stronger isolation.14
Still open The complete downstream impact and all remediation outcomes are not publicly established.
Could a test agent reach production credentials or communicate beyond its authorised environment?
Follow reports to their sources. Distinguish documented harm from potential risk. Examine the responses that can earn trust.
Search original sources and examine reports in context. Different sources can describe the same event.
The source library contains 27,003 searchable entries as a subset of the cumulative collection. It also includes hazards, court decisions, vulnerabilities and research findings. Records before 2016 have been removed; undated records remain. Search results and pagination refer to this subset.
Sources: OECD AIM; AIID; AIAAIC; AVID; MITRE ATLAS; AI Hallucination Cases Database (Damien Charlotin); OpenAI disclosures. Attribution, licences, snapshot dates and original links appear in each record. Source classifications and allegations are not independently verified.
Connect the original account, the response and the questions that still need evidence.
Identify who observed the event and what they could establish.
Keep a promised change, reported implementation and an independent outcome check distinct.
Link new evidence to an existing event before increasing any count.
Three practical questions recur across the five selected case studies. This is an editorial reading of this small sample, not a measure of how often AI systems fail.
Sample: AIR-2026-001–005. Case sources reviewed 18 September; synthesis prepared 22 September 2026. Reported countermeasures do not establish the effectiveness of every change.
A comparison of ten selected case families in Anthropic’s September disclosure with the stored collection found: one existing record matched, three have related coverage only, and six remain unresolved. These are matching decisions, not ten new incidents.
The selection covers the six cyber case families, GTG-87001 and three distillation case families. It does not cover the full publication. Provider allegations retain their attribution.
A shared actor or topic is not enough to establish the same event. The six unresolved matches are review candidates, not confirmed gaps. These matching decisions describe the 22 September review, not the later 29 September database refresh.
Anthropic · Original disclosureOfficial Excel export 2026-11-09
Source & methodologyCommit 8eda5f4 · checked 12 Nov 2026
Source & methodologyLatest database check · 12 Nov 2026
A broad record helps reveal what deserves a closer look. Context gives the numbers meaning.
Provider-reported availability, refreshed every five minutes.
A window onto the infrastructure people use to build and share AI. These service reports provide background context; they do not establish AI involvement and are excluded from incident totals.
Global data-centre electricity use could rise to 950 TWh by 2030.
That implies about 96% growth from the IEA’s 2025 estimate. Reliable energy and thoughtful investment can support more useful AI services.
All data centres, not AI alone. Growth calculated as (950 ÷ 485 − 1). The 2030 figure is a forecast, not an outcome. The editorial interpretation is from AI Incidents. These figures are separate from incident totals.
How do open models perform, and what can you download?
| Test | Kimi K3.1 Pro | Claude Fable 5.2 |
|---|---|---|
| Terminal tasksTerminal-Bench 4 | 67.2% | 59.6% |
| Document analysisGDP.pdf | 31.4% | 24.2% |
| Coding tasksFrontierCode-AA 2 | 25.5% | 48.8% |
What was found. What was solved. What the result actually proves.
Mozilla says early Claude Mythos Preview found vulnerabilities fixed in Firefox 150.
Mozilla · 21 Apr 2026Anthropic reports 26,153 candidates; external firms reviewed only a subset. Candidate totals are not confirmed zero-days.
Anthropic programme · 26 Aug 2026Known upstream fixes in Anthropic’s disclosure programme. A report, a patch and an installed update are different milestones.
Anthropic programme · 26 Aug 2026In a separate March Firefox study, Anthropic reported two successful exploit cases across several hundred attempts, with protections including the browser sandbox removed. This demonstrates capability under test conditions, not routine browser takeovers.
The programme includes Mythos Preview and other Claude models. Its reviewed and disclosed groups differ: 1,278 reports bypassed external triage at maintainers’ request. Valid findings may include previously reported issues. Counts can overlap with Mozilla’s and must not be added. “Patched” reflects Anthropic’s knowledge, not deployment across users’ devices.
Dated evidence snapshots · checked 18 Sep 2026 · separate from the incident register and live infrastructure status.
Records use each repository’s supplied dates. Overlaps, different date definitions and changing coverage mean this chart does not measure growth in unique incidents or actual harm.
Keeping classifications visible is part of keeping trust.
The collections include incident reports, hazards, court decisions, research exercises and regulatory proceedings.
We follow AI where it matters: the failures people need to understand and the progress worth imagining. Sources and context help visitors recognise risks, ask better questions and discover what is possible.
This website is powered by City Update, a Düsseldorf agency, working together with AI.
Explore the infrastructure behind AIRecord the actual impact, source evidence and uncertainty. Give affected people a voice.
Document containment, fixes and company responses. Separate action taken from claims made.
Look for independent testing and follow-up evidence. Keep unresolved questions in view.
Specialist manufacturing and a global supply chain.
Reliable power for training and everyday use.
Physical facilities, networks and equipment.
Heat management, with needs that vary by design.
Engineers, operators and accountable institutions.
Individuals, researchers and companies can submit evidence to this independently published register. The register has no regulatory authority and does not certify AI systems.
Good reporting makes room for both the promise of frontier AI and the consequences of its failures. Start with the evidence, ask what changed, and keep the unanswered questions visible.
Provider statements, affected-party accounts and independent investigations, clearly distinguished.
What was contained, what was fixed and what still needs evidence. Progress should be demonstrable.
A record that can be challenged and improved. Contact the editorial team for source questions or corrections.
Contact the press desk