Clustered 2 filings across 2 jurisdictions · filing window Nov 11, 2022 → Nov 14, 2022. View entity profile → Other incidents for this victim →
incident inc_c0260944ae4543c2 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Financial account · Financial credentials
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.
ME NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 8, 2022 → Oct 11, 2022
When the intrusion reportedly occurred, per the linked filings
Oct 11, 2022
Reported by MAINE AG, NEW HAMPSHIRE AG filings
American Metering Services (AMS) experienced an external system breach between March 8, 2022, and October 11, 2022. The incident was discovered on October 11, 2022. The breach compromised names combined with financial account numbers or credit/debit card numbers and their associated security codes, affecting 3 Maine residents. Written notifications were sent to affected individuals on November 11, 2022.
Affected (this filing): 3
American Metering Services (AMS) notified the NH Attorney General that an unauthorized person may have captured payment information (name and bank account number) of 2 NH residents via its payment portal (ams-ubs.com) between March 8 and October 11, 2022. AMS fixed the vulnerability, notified law enforcement, and mailed notifications to affected individuals on November 11, 2022.
Affected (this filing): 2
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.