Breach registry
Ticketiq Data Breach
What was exposed, when it happened, and which databases confirm it.
- accounts
- 6,151,185
- Breached
- March 1, 2016
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.
What happened
In May 2018, Ticketfly, a ticket distribution service, experienced a significant data breach when an attacker defaced the website and leaked the data online. The breach exposed over 26 million unique records containing email addresses, names, physical addresses, and phone numbers. Ticketfly later acknowledged that hashed password credentials might have been compromised, despite not being included in the publicly leaked data.
Compromised Info
- name_first
- name_last
- address_street_number_name
- address_street_two
- address_city
- address_state
- address_zip
- phone_number
Attestation
Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.
Sources & Link Methods
- LeakCheck
- Dehashed— linked via AI direct match to LeakCheck (85% confidence)
FAQ
What was leaked in the Ticketiq breach?
The Ticketiq breach exposed: name_first, name_last, email, address_street_number_name, address_street_two, address_city, address_state, address_zip, and phone_number.
When did the Ticketiq breach happen?
The Ticketiq breach was disclosed on March 1, 2016 and affected 6,151,185 records.
Am I affected by the Ticketiq breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the Ticketiq leak.