OVH data breach

916,620 records Breach date: May 2015

Exposed data

Email addressesUsernamesPasswordsIP addresses

In May 2015, OVH suffered a data breach. The dataset indexed by LeakCheck contains 916,620 records.

The leaked records include email addresses, usernames, passwords and IP addresses.

If your data appears in this dataset, any account that shares the same password is at risk. Run a free check below, and if you find yourself in a leak — change the affected passwords and enable two-factor authentication.

Check if your account is affected

Enter your email, username or phone number — the check is free and confidential, and the result will tell you whether this breach mentions you.

Exposed in this breach? Do this now

Change the password

On the breached site and everywhere else you reused it. Make every password unique.

Enable 2FA

A second factor keeps a leaked password from becoming a hijacked account.

Set up monitoring

and get notified the moment your data appears in a new leak.

OVH breach: questions and answers

When did the OVH data breach happen?

The OVH breach dates to May 2015.

How many records were leaked in the OVH breach?

LeakCheck has indexed 916,620 records from the OVH breach.

What data was exposed in the OVH breach?

The leaked records include email addresses, usernames, passwords and IP addresses.

Were passwords exposed in the OVH breach?

Yes. The indexed OVH records include passwords, in plain text or hashed. If you had an account, change that password and every other password you reused.

How do I check if my data was in the OVH breach?

Enter your email address, username or phone number in the search form on this page. The free check shows whether your data appears in the OVH breach — and in any of the other 1,468 sources LeakCheck indexes.

What should I do if my data was in the OVH breach?

Change the password you used on OVH and everywhere you reused it, turn on two-factor authentication, and watch for phishing that quotes details from the leak. To hear about the next breach first, set up breach monitoring.