Breach Census by the numbers
22,879 confirmed incidents across 6 source registers, recomputed on every request.
Every table on this page is a live query against the same confirmed, non-hidden incidents every other page on this site counts — there is no separate "stats" database, so these figures can never drift from what /year, /sector, /country and the organisation pages themselves show.
Most confirmed incidents come from US state attorney general breach-notification registers, which publish how many residents of that one state were notified, not a national or global total. That is the main reason the records-affected coverage figure below is low: a state register entry can confirm an incident happened without ever giving Breach Census a usable overall affected-count to store.
The disclosure-delay table below reuses the exact definition the disclosure_metric materialized view uses on /sector pages (days from occurred_on to disclosed_on, confirmed incidents only), but combines every sector into one site-wide row per jurisdiction and year, and only shows a row once at least 10 incidents support it.
Confirmed incidents by year
Years are assigned by disclosure date, falling back to discovery, then occurrence date.
| Year | Confirmed incidents |
|---|---|
| 2026 | 2,840 |
| 2025 | 2,924 |
| 2024 | 2,640 |
| 2023 | 2,871 |
| 2022 | 2,457 |
| 2021 | 2,816 |
| 2020 | 2,517 |
| 2019 | 1,986 |
| 2018 | 326 |
| 2017 | 411 |
| 2016 | 289 |
| 2015 | 236 |
| 2014 | 214 |
| 2013 | 187 |
| 2012 | 135 |
Organisations and incidents by source register
Counts are of confirmed, non-hidden incidents only — a register row that never resolved to a confirmed incident is not counted here.
| Source register | Organisations | Confirmed incidents |
|---|---|---|
| US state attorney general notices | 14,768 | 22,028 |
| HHS OCR breach portal (US) | 804 | 814 |
| SEC EDGAR filings (US) | 58 | 59 |
| UK ICO enforcement actions | 36 | 36 |
| UK FCA fines | 4 | 4 |
| UK PRA actions | 4 | 4 |
How much is known
Share of the 22,879 confirmed, non-hidden incidents that carry each field.
| Field | Incidents with a value | Coverage |
|---|---|---|
| Records affected | 1,517 | 6.6% |
| Data types | 5,299 | 23.2% |
| Attack type | 2,389 | 10.4% |
Median days from occurrence to disclosure
Every sector combined, by jurisdiction and the year the incident occurred — shown only where at least 10 confirmed incidents support the figure.
| Jurisdiction | Year occurred | Incidents (n) | Median days |
|---|---|---|---|
| US-CA | 2023 | 445 | 153 |
| US-CA | 2024 | 373 | 155 |
| US-CA | 2020 | 363 | 152 |
| US-CA | 2021 | 363 | 136 |
| US-TX | 2025 | 288 | 200 |
| US-WA | 2023 | 280 | 121 |
| US-CA | 2022 | 275 | 147 |
| US-CA | 2025 | 251 | 129 |
| US-CA | 2017 | 237 | 68 |
| US-WA | 2020 | 222 | 200.5 |
| US-CA | 2019 | 220 | 153 |
| US-WA | 2024 | 220 | 160.5 |
| US-CA | 2016 | 217 | 93 |
| US-CA | 2018 | 213 | 131 |
| US-CA | 2014 | 169 | 92 |
| US-CA | 2015 | 153 | 79 |
| US-WA | 2021 | 153 | 137 |
| US-TX | 2026 | 143 | 79 |
| US-WA | 2025 | 140 | 137 |
| US-CA | 2013 | 136 | 70.5 |
| US-WA | 2022 | 121 | 119 |
| US-CA | 2012 | 114 | 56.5 |
| US-CA | 2026 | 114 | 73.5 |
| US-WA | 2016 | 69 | 272 |
| US-WA | 2019 | 62 | 162 |
| US-WA | 2026 | 60 | 80 |
| US-DE | 2023 | 59 | 108 |
| US-WA | 2017 | 54 | 171.5 |
| US-WA | 2018 | 43 | 159 |
| US-DE | 2024 | 39 | 118 |
| US-TX | 2024 | 38 | 439 |
| US-WI | 2017 | 37 | 30 |
| US-DE | 2020 | 35 | 143 |
| US-DE | 2022 | 30 | 100 |
| US-DE | 2021 | 29 | 182 |
| US-CA | 2011 | 25 | 417 |
| US-WA | 2015 | 22 | 230.5 |
| US-WI | 2016 | 19 | 28 |
| US-DE | 2025 | 17 | 131 |
| US-DE | 2019 | 16 | 88.5 |
| US-WI | 2014 | 15 | 53 |
| US-WI | 2013 | 13 | 27 |
| US-WI | 2018 | 13 | 114 |
| US-WI | 2021 | 11 | 52 |
Regulator fines by year and currency
Totals are not summed across currencies.
| Year | Currency | Actions | Total |
|---|---|---|---|
| 2026 | EUR | 5 | 47,026,000 EUR |
| 2026 | GBP | 6 | 16,213,990 GBP |
| 2025 | EUR | 21 | 6,054,000 EUR |
| 2025 | GBP | 8 | 18,732,283 GBP |
| 2024 | EUR | 14 | 1,065,000 EUR |
| 2024 | GBP | 11 | 1,887,500 GBP |
| 2023 | EUR | 13 | 33,416,000 EUR |
| 2023 | GBP | 12 | 24,756,020 GBP |
| 2022 | EUR | 8 | 4,075,000 EUR |
| 2022 | GBP | 2 | 56,750,000 GBP |
| 2021 | EUR | 7 | 1,825,000 EUR |
| 2020 | EUR | 6 | 2,679,000 EUR |
| 2019 | EUR | 3 | 600,000 EUR |
| 2019 | GBP | 2 | 2,665,100 GBP |
| 2018 | GBP | 1 | 16,400,000 GBP |
| 2014 | GBP | 1 | 14,000,000 GBP |
Questions and answers
Why is records-affected coverage so low?
Most confirmed incidents come from US state attorney general registers, which publish how many residents of that one state were notified rather than a national or overall total. That confirms the incident happened without giving Breach Census a single affected-count to store, which is why the coverage figure stays well under half.
Are the regulator fine totals converted to one currency?
No. Fines are shown in their original currency and never summed across currencies, because doing so would require an exchange-rate assumption this site does not otherwise make anywhere.
How is the disclosure delay measured?
As the number of days from an incident’s occurred_on date to its disclosed_on date, for confirmed incidents where both dates are known, grouped by jurisdiction and the year it occurred, and only shown once at least 10 incidents support the figure.