Allied Telesis Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-30 and was reported on 2025-04-21. 10 Indiana residents were affected. 43,413 individuals affected in total.
Affected (this filing): 43,413
Clustered 2 filings across 2 jurisdictions · filed Apr 21, 2025. View entity profile → Other incidents for this victim →
incident inc_32b6a620973843e1 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 30, 2024
When the intrusion reportedly occurred, per the linked filings
May 20, 2024
Reported by NEW HAMPSHIRE AG filing
Allied Telesis Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-30 and was reported on 2025-04-21. 10 Indiana residents were affected. 43,413 individuals affected in total.
Affected (this filing): 43,413
Allied Telesis, Inc. notified the New Hampshire Attorney General of a data event affecting 77 NH residents. Unauthorized access occurred between April 30 and May 20, 2024, with discovery on May 20, 2024. Files were removed. The company notified federal law enforcement, offered 24 months of Experian credit monitoring, and implemented additional cybersecurity safeguards and employee training.
Affected (this filing): 77
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.