Download
Both files hold the same 88 entries, one per layoff announcement, regenerated on every update. The JSON file also carries the field definitions below, the licence and the suggested citation. Both are served with open CORS headers, so they can be read directly from a notebook or a browser.
What is in it
- 88
- Layoff announcements
- 82
- Companies
- 15
- Countries
- 160,295
- Job cuts with exact counts (a floor)
An entry is included only when the company itself or credible reporting cited AI or automation as a driver of the cuts. Cuts made to fund or refocus on AI count; AI used only to choose who was cut does not. Percentages and ranges are kept as reported and never summed, so the exact-count total is a floor, not a census. The full rule, with examples, is on the methodology page.
Fields
One row per announcement. Lists are semicolon-separated in the CSV and arrays in the JSON.
| Field | Meaning |
|---|---|
| id | Stable identifier: company slug plus the entry date. |
| date | Date the cuts were announced or first reported (YYYY-MM-DD). |
| company | Company making the cuts. |
| country | The company's home country, not where the cuts happened. |
| industry | The company's industry. |
| sectors | Business lines affected (semicolon-separated in the CSV). |
| roles | Roles affected as reported; "Various" when the source gives no breakdown (semicolon-separated in the CSV). |
| employees_affected | Headcount exactly as reported: a number, a percentage such as "40%" or a range such as "4000-6000". Empty when no figure was disclosed. |
| employees_affected_exact | The headcount when it was reported as an exact number, otherwise empty. Only these values are summed in the tracker's totals. |
| attribution | "explicit" when the company itself cited AI; "strong" when credible reporting established it. |
| mechanism | How the source links the cuts to AI: "automation" when AI or automation does, or removes the need for, work the cut roles did; "reinvestment" when the cuts fund or refocus resources on AI; "disruption" when AI eroded demand for the company's product. Empty when the source cites AI only in general terms. When a source gives more than one, the one it puts first. |
| reason | Summary of the cuts and of how AI was cited. |
| source | Publisher of the source. |
| source_url | Link to the source. |
Stable ids and deep links
Each entry's idis the company's slug plus the announcement date, for example kroger-2026-10-12. It never changes once published, and it is the anchor of the entry's row in the ledger: https://www.ailayofftracker.com/#kroger-2026-10-12. Cite the id when you rely on a single entry, so the reference survives later additions.
Licence and citation
The data is licensed under CC BY 4.0: quote, chart, republish or build on it, including commercially, with attribution and a link. Each entry's source link points to the original report; cite that report too when you rely on one entry.
Use and cite this data
Free to quote, chart and republish under CC BY 4.0 with attribution and a link. Download the full dataset as CSV or JSON.
- In an article
According to AILayoffTracker.com, which tracks layoffs where AI was cited as a driver, …
- As a reference
- AILayoffTracker.com. AI-Related Layoffs Database [Data set]. Data through October 12, 2026. CC BY 4.0. https://www.ailayofftracker.com/
Referenced in SalesforceBen, SiteProNews, Cybernews, and Lumo Insights. See where →
Updates and corrections
Entries are added as they are verified, and the files rebuild with each update. Every correction, removal or change of method is listed with its date in the public changelog. New entries also appear in the RSS feed. For questions or a custom cut of the data, see press & data reuse.