Anchorage Neighborhood Health Center: 70,555 individuals, Nov 2025.

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 21 of the 32 Alaska filings (66%) and on 81% of all filings submitted in 2025. Network Server appears on 44% of Alaska filings.

No business associate is recorded on the filing; 38% of Alaska filings do involve one. At 70,555 individuals the breach is 35 times the Alaska median filing of 2,008 and 18 times the national median of 4,000 across all 7,884 filings. It sits in the 10,000 to 99,999 band, which holds 1,938 filings.

As of 28 August 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.

Alaska's breach notification statute (Alaska Stat. 45.48.010 et seq.) requires notice to affected residents in the most expedient time possible and without unreasonable delay. Its attorney general threshold: only when invoking the no-likelihood-of-harm exception (written notice to the AG). 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 70,555 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 $11.3M; the 2026 edition's $192 gives $13.5M. Both are modelled estimates with the method shown, not costs disclosed by Anchorage Neighborhood Health Center. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 2.0 times the sector average.