All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed5 filings · 5 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 5 filings

ACADIAN AMBULANCE SERVICE, INC. — June 2024 breach

Clustered 5 filings across 5 jurisdictions · filing window Nov 1, 2024 → Nov 8, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

2,783,676

First → last filing

Nov 1, 2024 → Nov 8, 2024

Merge confidence

100%

incident inc_69bb36f0105c480e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filing describes unauthorized access. Intrusion Jun 19, 2024–Jun 21, 2024, discovered Jun 19, 2024 — the first regulatory filing landed 135 days later (flagged late). 2,783,676 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 1 more. Notifications rolled out on a 7-day schedule across 5 filings beginning Nov 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

135days

Discovered → first regulatory filing

Discovery variance

2days

Range of discovered_at dates across filings

Filing span

7days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksOregon✗ OR AG >45dVermont✗ VT AG >45 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 19, 2024breach begins

Jun 19, 2024discovered · members disagree

notification delay · 135 days

Nov 1, 2024first filing

Nov 8, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

NOV 1IL AGIL AG noticefirst filing · no count statedauto-linkedday 0
NOV 7OR AGOR AG noticestates nationwide total 2,783,676+6d
NOV 7CA AGCA AG noticeno count statedauto-linked+6d
NOV 8VT AGVT AG noticeno count statedauto-linked+7d
NOV 8MA AGMA AG noticemost recent · 476 MA residentsauto-linked+7d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jun 19, 2024 – Jun 21, 2024
Discovered: Jun 19, 2024IL AGJun 21, 2024OR AG + CA AG + VT AGfilings disagree on discovery
Data types: Health (basic) · Identity (basic) · Government ID · PHI
Attack vector: Unauthorized Access

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

2,783,676

Sum of filed state slices

476· 0.0% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method: deterministic
Confidence: 1.00 · above the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

7 days

Cadence

~1 / 1.8d

vs. multi-state median

1.1× faster

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.