APProjects/us-tech-company-layoffs-warn-act-notices-daily

US tech company layoffs — the actual WARN Act filings, rebuilt every day

Last rebuilt: 2026-09-16. 1,735 layoff notices filed by software, IT, internet, semiconductor and electronics companies with US state labor departments — 191,601 workers, 367 employers, 39 states, 1989–2026. Free, CC BY 4.0, no login, no delay.

Every other tech-layoff tracker you know is assembled from news stories and crowd submissions. This one is assembled from the legal filings employers must make before a mass layoff: employer, state, site, workers affected, notice date, effective date, and the notice type in the state's own words. An automated pipeline re-scrapes 48 state portals every day and rebuilds this file with them.

Read this before you quote a number

This is a FLOOR, not a census. No US state WARN portal publishes an industry field — not one. Sector here is assigned from the employer name by an auditable keyword rule table, and 47.4% of all 60,955 notices in the archive carry a name that reveals no sector at all (Rugged Liner, KPR US, Point Designs). A tech company trading under an opaque name is therefore missing from this file. Every row keeps sector_rule — the exact pattern that fired — so any inclusion can be checked or disputed row by row, and the full unfiltered archive is one click away: all 60,955 notices.

WARN also only covers layoffs above a size threshold (broadly 50+ at a site, lower in some states), so small tech layoffs never generate a filing at all.

What counts as "tech" here: software, internet and e-commerce platforms, semiconductors, consumer electronics and IT services — the same boundary the well-known tech-layoff trackers use, which is why Meta, Intel, Cisco and Google sit in the same file as Wayfair, Instacart, Peloton and WeWork. Telecom and cable carriers are deliberately NOT here; they are in the sector dataset under media_telecom. Disagree with a row? The sector_rule column names the pattern that put it there.

Files

file	rows	what it is
data/tech_layoff_notices.csv	1,735	every tech WARN notice, one row each
data/tech_layoffs_by_employer.csv	367	per-company history, biggest first
data/tech_layoffs_by_year.csv	38	notices, workers and employers per year

import pandas as pd
df = pd.read_csv("https://huggingface.co/datasets/APProjects/us-tech-company-layoffs-warn-act-notices-daily"
                 "/resolve/main/data/tech_layoff_notices.csv")
df.groupby(df.notice_date.str[:4]).employees_affected.sum().tail(10)

Tech layoffs by year

year	notices	workers affected	employers
2026	144	17,463	48
2025	138	12,161	49
2024	177	16,674	47
2023	310	31,381	68
2022	107	13,920	34
2021	35	2,703	17
2020	148	14,542	69
2019	96	7,134	33
2018	59	5,850	30
2017	67	5,713	33
2016	83	12,034	37
2015	72	7,718	36
2014	61	7,508	21
2013	22	2,020	11
2012	6	1,334	5

The companies with the most tech layoff workers on file

employer	notices	workers	states	first	last
Meta Platforms	114	14,006	CA, NJ, NY, TX, WA	2022-11-09	2026-05-26
Microsoft	61	13,083	CA, IL, NY, OR, WA	2004-08-23	2026-07-06
Intel	100	8,973	AZ, CA, NJ, NM, OR, PA, TX, WA	2001-05-03	2026-07-27
Cisco Systems	37	7,986	CA	2014-10-01	2026-06-24
Motorola	28	7,248	CA, FL, IL, KY, NJ	1998-09-22	2016-09-28
Qualcomm	69	6,587	CA, CO, NC, NJ	2014-12-19	2026-04-09
Broadcom	26	5,777	CA, CO, MA, NJ, NY, VA, WA	2014-07-01	2025-10-20
Oracle America	27	4,356	AL, CA, MD, NY, WA	2017-01-19	2026-04-02
Zenith Electronics	8	3,670	IL	1993-04-02	2001-02-26
Google	100	3,369	CA, NY, WA	2017-01-13	2026-08-05
Xerox	33	3,331	CA, CO, FL, IL, KY, NC, NY, OH, OK, OR, TN, UT, WA	1994-10-11	2020-06-06
Panasonic	19	2,941	CA, IL, KY, NJ, NY, OR, WA	2004-01-30	2025-11-26
Intuit	30	2,933	AZ, CA, CO, ID, IL, VA	2013-07-10	2026-05-21
Stitch Fix	7	2,830	CA, PA, TX, UT	2020-06-16	2023-10-02
Western Digital	29	2,660	CA, UT	2015-04-20	2026-02-03

Most recent tech filings in this build

date	employer	state	location	workers
2026-09-14	Uber Technologies	CA	Santa Clara County	43
2026-09-14	LeeMAH Electronics	CA	San Mateo County	62
2026-09-14	Uber Technologies	CA	Santa Clara County	94
2026-09-02	Uber Technologies	WA	Seattle	93
2026-09-02	Uber Technologies	IL	Chicago, 433 West Van Buren St.	363
2026-08-17	LeeMAH Electronics	CA	San Mateo County	205
2026-08-14	Netflix	CA	Los Angeles County	59
2026-08-05	Salesforce	WA	Seattle, Bellevue	59
2026-08-05	Google	WA	Various locations in Washington	52
2026-08-05	Salesforce	CA	San Francisco County	74
2026-08-04	Zillow Group	WA	Seattle	91
2026-08-04	Nutanix	CA	Santa Clara County	65

Names are resolved for spelling variants, not corporate parents: a subsidiary filing under its own name stays under its own name.

Where this comes from

• Source: official state WARN listings, scraped daily and normalized to one schema. Full method, per-state coverage and freshness: https://approjects-warn-act-notices.static.hf.space.
• Public commit log of every daily rebuild: https://github.com/APVentureEngine/warn-act-notices.
• Whole archive, all sectors: https://huggingface.co/datasets/APProjects/us-warn-act-layoffs-notices-daily.
• All 20 sectors, not just this one: layoffs by industry sector.
• Verify anything that matters at the state source before you publish it.

If this saved you a scrape

• Like this dataset (the heart, top right) — likes are how the next person searching for tech layoffs finds a file that was rebuilt today instead of one uploaded once in 2023.
• Watch the source repo's releases — one notification each day the snapshot is republished.
• Corrections and questions: open an issue.

Published by APProjects, an automated publisher of US public records. Not affiliated with any state agency.

A layoff record you can audit, not just download

This dataset is one cut of a single daily rebuild: 61,330 US WARN Act layoff notices from 48 state agencies, 1988 to today, one schema, no login, no delay, CC BY 4.0. Snapshot as of 2026-09-16; the files above are rebuilt every day, so the live count is the truth.

Several projects publish a current WARN scrape and two of them carry more rows than we do. None of them publish what the records used to say:

• 617 observed changes to already-published notices, logged daily since 2026-08-31. data/revisions.csv records every field that differed between two consecutive daily builds — employee counts, effective dates, notice types, company names — with the old value, the new value and the date we saw it. We publish the observation and not the cause: a change is equally explained by the agency amending the notice or by our own parser improving, and we do not guess which (see data/revisions.README.txt). A scrape that starts tomorrow cannot backfill any of it; it only exists if someone was watching.
• 6,799 notices whose state agency page no longer lists them. Agencies take notices down. We keep them, flagged as archive-only, so a count you ran last year still reconciles.
• Point-in-time employer identity. The ticker crosswalk resolves a filer to the company as it existed at the time of the notice — Kmart, Sears Holdings, Symantec — not to whatever is on today's ticker file.

If you have to defend a number to an editor, a referee or a compliance reviewer, that provenance layer is the part you cannot rebuild yourself. How to cite this dataset →

Look something up right now — free, no signup, nothing to install. Check any employer or state against the last 180 days → It runs in your browser against these same files.

Building something with it? The same files are a free HTTP API — JSON and CSV, no key, no signup, access-control-allow-origin: * so fetch() works from a browser: endpoints, schema and curl examples →

Need one industry only? The same filings, cut by an auditable employer-name rule (each row keeps the rule that fired): tech companies · hospitals & healthcare · retail store closings · restaurants & hotels · factory & plant closings · banks, insurance & finance · warehouses, trucking & logistics · all 20 sectors.

Or have it watch a list for you. Coming back to look is the part a CSV cannot do. WARN Watch — $49 for a year, one payment, nothing auto-renews, 14-day refund, no login: up to 500 employer names plus whole states, matched on every daily refresh, delivered to a private alert page + calendar (.ics) + RSS + an optional Slack / Discord / Teams webhook. Every alert carries that employer's whole filing history from the archive, which a keyword rule on an RSS feed cannot see. There is no built-in email — we do not claim one.

• See a real alert page before paying · what you get
• Try it free for 30 days, no card · Buy — $49/year

Not deciding today? Join the update list → — one email when a new dataset or tier is published; nothing promotional. A state added or a column renamed ships in the daily release instead, no address needed. The list is shared across APProjects datasets, holds an email address only, is run by Gumroad, and any message unsubscribes you. Rather give no address at all? Watch the repo's releases — GitHub notifies you on every daily republish, and a new state or changed field is in those notes the day it lands.

Reaching a human. WARN Feed is published by APProjects, an automated data publisher — that is stated plainly rather than dressed up. Corrections, coverage gaps, schema questions and refund requests all go here and are read: open an issue. Payments are handled by Gumroad as merchant of record, so an invoice can carry your company name.

Source, scrapers and methodology · the 48-state site

_{Card views are counted anonymously: one 1×1 image on a public CDN, no cookies, no script, no personal data. The count is public: jsDelivr stats.}