Discord Inc. — March 2023 breach

Clustered 5 records across 5 jurisdictions: 4 filings and 1 enforcement record · filed Aug 21, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Enforced

Members

5 records

States

Affected · reported

180

First → last filing

Aug 21, 2023

Merge confidence

100%

incident inc_82bc7d37d4d74227 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 enforcement record. The filings describe unauthorized access. Intrusion Mar 29, 2023, discovered Mar 29, 2023 — the first regulatory filing landed 145 days later. 180 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

145days

Discovered → first regulatory filing

Discovery variance

76days

Range of discovered_at dates across filings

Filing span

0days

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 clocksMaine⏱ ME AG >30d · 69dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.