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

Confirmed4 filings · 4 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 4 filings

ZOLL Services LLC — November 2018 breach

Clustered 4 filings across 4 jurisdictions · filing window Mar 18, 2019 → Apr 4, 2019. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

277,319

First → last filing

Mar 18, 2019 → Apr 4, 2019

Merge confidence

100%

incident inc_9f57f25e79a24f19 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe an accidental exposure. Intrusion Nov 8, 2018–Dec 28, 2018, discovered Jan 24, 2019 — the first regulatory filing landed 53 days later. 277,319 individuals reported across the linked filings. Data reported: Government ID, Health (basic), and Identity (basic). Notifications rolled out on a 17-day schedule across 4 filings beginning Mar 18, 2019. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

53days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

17days

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 clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 8, 2018breach begins

Jan 24, 2019discovered

notification delay · 53 days

Mar 18, 2019first filing

Apr 4, 2019most recent filing

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

Member cascade — every filing about this breach

MAR 18HHS OCRHHS OCR noticefirst filing · states nationwide total 277,319auto-linkedday 0
MAR 18MT AGMT AG notice445 MT residentsauto-linkedday 0
MAR 29MA AGMA AG notice1,561 MA residentsauto-linked+11d
APR 4CA AGCA AG noticemost recent · no count statedauto-linked+17d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Nov 8, 2018 – Dec 28, 2018
Discovered: Jan 24, 2019· 77d undetected
Data types: Health (basic) · Identity (basic) · Government ID
Attack vector: Misconfiguration

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)

277,319

Sum of filed state slices

2,006· 0.7% of stated

99% 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 filing4 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

17 days

Cadence

~1 / 5.7d

vs. multi-state median

2.1× slower

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.