Aesto, LLC: 9,540,683 individuals, Jul 2026.

OCR classifies the incident as a hacking or IT incident, with the breached information held in a network server. Hacking/IT Incident is the type recorded on 62 of the 100 Alabama filings (62%) and on 86% of all filings submitted in 2026. Network Server is the most common location in the state, appearing on 55% of Alabama filings.

A business associate is recorded as present on the filing, as it is on 29% of Alabama filings. At 9,540,683 individuals the breach is 1,807 times the Alabama median filing of 5,280 and 2,385 times the national median of 4,000 across all 7,927 filings. It is one of 152 filings on the register of one million or more individuals.

As of 10 September 2026 the case is listed by HHS OCR under Cases Currently Under Investigation. OCR has not published a closing summary, so this page is limited to the fields on the filing itself; the archive entry that follows a closed investigation usually adds a short account of what was exposed and what the entity did afterwards.

Alabama's breach notification statute (Ala. Code 8-38-1 et seq.) requires notice to affected residents without unreasonable delay, no later than 45 days after determining a breach occurred. Its attorney general threshold: more than 1,000 Alabama residents. The HIPAA Breach Notification Rule ran alongside it: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery, which is the clock that put this filing on the portal.

Multiplying 9,540,683 individuals by IBM's $160 customer-PII cost per record (Cost of a Data Breach 2025, the figure the site's calculator uses) gives a modelled $1.53B; the 2026 edition's $192 gives $1.83B. Both are modelled estimates with the method shown, not costs disclosed by Aesto, LLC. Because the filing is above the roughly 100,000-record range in which the per-record figure is reliable, the result is an upper bound, not an estimate: fixed costs are spread across far more records at this scale.