DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed7 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

T-MOBILE USA, INC. — July 2021 breach

Clustered 7 filings across 7 jurisdictions · filing window Aug 19, 2021 → Aug 31, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

53,800,000

First → last filing

Aug 19, 2021 → Aug 31, 2021

Merge confidence

100%

incident inc_1938c9b855a64b84 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Jul 19, 2021–Jul 22, 2021, discovered Aug 17, 2021 — the first regulatory filing landed 2 days later. 53,800,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 12-day schedule across 7 filings beginning Aug 19, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
2days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
12days

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 clocksDelaware✓ DE credit monitoring dueWashington✓ WA AG ≤30dCalifornia✓ CA 60-day OK · 2dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Jul 19, 2021breach begins
Aug 17, 2021discovered
notification delay · 2 days
Aug 19, 2021first filing
Aug 31, 2021most recent filing

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

Member cascade — every filing about this breach

  1. AUG 19DE AGDE AG noticefirst filing · states nationwide total 53,800,000day 0
  2. AUG 19NH AGNH AG noticeno count statedday 0
  3. AUG 24WA AGWA AG notice2,079,648 WA residents+5d
  4. AUG 25CA AGCA AG noticeno count stated+6d
  5. AUG 26MA AGMA AG notice1,044,774 MA residents+7d
  6. AUG 27OR AGOR AG noticeno count stated+8d
  7. AUG 31SC AGSC AG noticemost recent · 647,980 SC residents+12d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 12, 2021
DE AG
Discovered
Aug 17, 2021· 5d undetected
DE AG + NH AG + WA AG +3
Data types
Financial account · Financial credentials · Identity (basic) · Government ID
DE AG + NH AG + WA AG +3
Attack vector
Unauthorized Access
NH AG

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)

53,800,000

Sum of filed state slices

3,772,402· 7.0% of stated

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

US53,800,000
WA2,079,648
MA1,044,774
SC647,980

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing7 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
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

12 days

Cadence

~1 / 2d

vs. multi-state median

2.0× 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.