This appendix sorts every row of the incident log in Appendix C by the industry it touched, and gives each industry a page of its own, split into sub-sectors. Nothing here is new reporting: each row shows the log's own text, with the same stated cause, status label, sources and link.
Rows sit together here because they share an industry. That does not mean they are linked, or that one caused another. Being in the log is not a judgment that an event was an attack: some rows are failures, accidents, warnings or statements, and some rest on reports or claims (see Status). The log is a curated list, not a sample, so the counts show where reporting concentrated as much as where events did.
By industry
Each row is counted once, under its main industry. The numbers in brackets are sub-sectors.
How firm the evidence is, by industry
Each row keeps the log's status label. Confirmed: the organization, the product's maker or an official body confirmed the event itself. Reported: it rests on news reports or one firm's research. Claimed: it rests on attackers' claims or unverified suspicion. A confirmed row can still be a failure or an accident; the stated cause on each industry page says which.
| Industry | Rows | Confirmed | Reported | Claimed | A source says AI was or may have been used |
|---|---|---|---|---|---|
| Government and public sector | 35 | 24 | 11 | 0 | 3 |
| Finance and insurance | 15 | 14 | 1 | 0 | 3 |
| Healthcare and life sciences | 10 | 8 | 2 | 0 | 0 |
| Energy and utilities | 6 | 4 | 2 | 0 | 1 |
| Transport and logistics | 22 | 16 | 5 | 1 | 0 |
| Technology and telecom | 29 | 20 | 9 | 0 | 8 |
| Retail, consumer and hospitality | 14 | 13 | 1 | 0 | 1 |
| Manufacturing and industry | 8 | 6 | 2 | 0 | 0 |
| Education and research | 8 | 7 | 1 | 0 | 1 |
| Media and entertainment | 2 | 2 | 0 | 0 | 1 |
| Professional and IT services | 1 | 1 | 0 | 0 | 0 |
| Across sectors | 16 | 13 | 2 | 1 | 5 |
| All industries | 166 | 128 | 36 | 2 | 23 |
A row counts here when a cited source says an AI tool was used, or may have been used, in that incident, including to find the flaw it exploited. Rows where a source denies any AI role, or mentions AI only in general terms, are not counted. Each count is what a source reported, not our finding, and none of the sources cited ties any of these rows to the US outages of November 12 to 17.
By week
Rows from Table 1 of the log (October 20 to November 18, 2026), by the week they began or became public. Darker cells hold more rows. The first and last columns are part weeks. A busier week means more rows in the log, which can reflect more reporting as much as more events. None of the sources cited in the log links any of these rows to the US outages of November 12 to 17.
| Industry | 20-26 Oct | 27 Oct-2 Nov | 3-9 Nov | 10-16 Nov | 17-18 Nov (2 days) | Total |
|---|---|---|---|---|---|---|
| Government and public sector | 5 | 10 | 7 | 8 | 2 | 32 |
| Finance and insurance | · | 5 | 7 | 2 | · | 14 |
| Healthcare and life sciences | 3 | 2 | 3 | 2 | · | 10 |
| Energy and utilities | 1 | · | 2 | 1 | 1 | 5 |
| Transport and logistics | 2 | 3 | 4 | 7 | 1 | 17 |
| Technology and telecom | 5 | 7 | 7 | 2 | 2 | 23 |
| Retail, consumer and hospitality | 1 | 2 | 4 | 4 | · | 11 |
| Manufacturing and industry | · | 1 | 3 | 3 | · | 7 |
| Education and research | 1 | 3 | 1 | 3 | · | 8 |
| Media and entertainment | · | · | 1 | 1 | · | 2 |
| Professional and IT services | · | · | · | · | · | 0 |
| Across sectors | 3 | 1 | 5 | 4 | · | 13 |
By region
The same Table 1 rows by the region heading they sit under in the log. More rows in a region can reflect more reporting in its languages and outlets as much as more incidents.
| Industry | United States | Latin America | Europe | Asia-Pacific | Middle East and Africa | Worldwide and at sea |
|---|---|---|---|---|---|---|
| Government and public sector | 7 | 7 | 11 | 4 | 1 | 2 |
| Finance and insurance | 2 | 2 | 2 | 6 | · | 2 |
| Healthcare and life sciences | 5 | 2 | 3 | · | · | · |
| Energy and utilities | · | 1 | 4 | · | · | · |
| Transport and logistics | 6 | 1 | 5 | 2 | 1 | 2 |
| Technology and telecom | 3 | · | 7 | 5 | 1 | 7 |
| Retail, consumer and hospitality | 1 | · | 3 | 5 | 2 | · |
| Manufacturing and industry | 1 | · | 4 | 1 | · | 1 |
| Education and research | 2 | 1 | 2 | 2 | · | 1 |
| Media and entertainment | · | · | 2 | · | · | · |
| Professional and IT services | · | · | · | · | · | · |
| Across sectors | 3 | · | 4 | 4 | · | 2 |
Every sub-sector
Each link opens that industry's page at the sub-sector. These counts include rows also listed from other industries, so they can add up to more than the industry's own total.
- Government and public sector: National government (25), State and local government (15), Defense and intelligence (4), Law enforcement and justice (3), Elections (3)
- Finance and insurance: Banking (5), Payments and fintech (2), Crypto and digital assets (4), Insurance (2), Investment and brokerage (2), Regulators and market bodies (2), Across finance (2)
- Healthcare and life sciences: Hospitals and health systems (9), Health services and insurers (2), Blood, labs and diagnostics (2)
- Energy and utilities: Oil and gas (3), Electricity and grid (2), Water and heating (2), Renewables (1)
- Transport and logistics: Aviation and air traffic (7), Maritime and ports (9), Rail (1), Road, logistics and postal (5)
- Technology and telecom: Cloud and SaaS (17), Software supply chain and open source (6), Network and security products (11), Telecom and internet providers (7), Hardware and devices (1)
- Retail, consumer and hospitality: Retail and grocery (12), E-commerce (3), Food and restaurants (2), Travel and hospitality (4), Consumer apps and services (1)
- Manufacturing and industry: Manufacturing (3), Automotive (1), Semiconductors and electronics (1), Chemicals and materials (1), Industrial control systems (9)
- Education and research: Universities (8), Education agencies and exams (3), Research institutes (2)
- Media and entertainment: News media (2)
- Professional and IT services: Legal (1), IT and managed service providers (8)
- Across sectors: Widely exploited vulnerabilities (12), Attack tools and frameworks (8), Official statements, warnings and reports (12)
How we sorted the rows
Each row has one main industry, the one its victim or subject belongs to, and is counted only there. A row that clearly spans another industry, such as a software flaw exploited at hospitals, is also listed on that industry's page, marked "also listed here", and is not counted twice. Rows about a tool, a widely exploited flaw, or an official statement, warning or report that is not about one victim sit under "Across sectors", and are also listed under the industry they concern. The sorting is ours; the facts in each row are the sources'.
Update log: This is a developing story. We'll add new findings here as the FAA forensics, vendor advisories and official root-cause reports come in. 18 Nov 2026: added "Where Anthropic's Claude and Mythos 5 fit", including whether restricting Mythos helped or hurt, the publisher's view and a skeptical reading, a key point, 21 timeline entries (AI models, the June 2026 US order, ARTEX's developer, related attacks, and the November 16 Optimizely and Coles incidents), and an item to "What would settle it". Later on 18 Nov: added the Director of National Intelligence's statements and House testimony, the FBI's clarification on ARTEX, the FAA's router pause and the state of its investigation, the Secretary of State's remarks, an unconfirmed report that fixes for AI-found flaws caused the outages, updates from Equinor and Optimizely, Visa's statement, earlier Amazon, Google and StepSecurity reports on ARTEX, a GAO report on AI chatbots, and 14 timeline entries. Last updated 18 Nov 2026.