Home › Companies › Regence

Regence data breach

Regence appears in 4 breach notices filed with HHS OCR and Washington AG, most recently reported on May 21, 2026.

Also listed as: Regence (Regence BS, Regence BSI and Regence BCBSO); Regence (Regence BlueShield and Regence BCBS of OR)

Breach notices filed with regulators

ReportedFiled withBreach date(s)People affectedData involvedSource
May 21, 2026HHS OCRNot listed 2,856 people (total reported to HHS) Not listedHHS OCR list ↗
May 6, 2025Washington AGNov 5, 2024 – Nov 21, 2024 706 Washington residents NameSocial Security NumberDriver's License or Washington ID Card NumberFinancial & Banking InformationFull Date of BirthHealth Insurance Policy or ID NumberMedical InformationWashington AG list ↗
Jan 31, 2025Washington AGDec 5, 2024 – Dec 19, 2024 714 Washington residents Medical InformationNameWashington AG list ↗
Aug 16, 2019Washington AGJul 25, 2019 642 Washington residents NameSocial Security NumberWashington AG list ↗

Each row is a notice as published by the agency. For state lists, the number affected counts only that state's residents; HHS lists the total reported. SEC rows are Form 8-K Item 1.05 filings, which usually don't give a count. A notice does not mean a settlement exists, and a settlement may cover a different incident than a given notice.

Is there a settlement?

We don't track an open class-action settlement for Regence right now. Settlements usually come months or years after a breach. Follow Regence and we'll email you if one opens.

What you can do now

Follow Regence

Get an email when Regence has an open settlement: when one is announced, a weekly reminder with the deadline and days left, and a heads-up if the deadline moves. Nothing about other companies unless you ask for it.

Free. At most one email a week, and only when there is something to act on. One-click unsubscribe in every email. Privacy