Confirmed breach. Intrusion Mar 18, 2024, discovered Mar 18, 2024 — the first regulatory filing landed 392 days later (flagged late). 118,418 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✗ ME AG >90d · 392dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
118,418
Data types
—
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 18, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Mar 18, 2024
Reported by MAINE AG filing
392 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Medical Express Ambulance Service reported a data breach to the Indiana Attorney General. The breach occurred on 2024-03-18 and was reported on 2025-04-14. 2,151 Indiana residents were affected. 118,418 individuals affected in total.
Medical Express Ambulance Service, a healthcare organization, reported a data breach to the Maine Attorney General, affecting 49 state residents. The breach, which occurred and was discovered on March 18, 2024, was categorized as an external system breach or hacking incident. The company began notifying affected individuals on April 14, 2025, and offered 12 months of identity theft protection services. The total number of individuals affected across all states is 118,418.
Affected (this filing): 49
ME AG >90d · 392d
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.