# Notice: do not use the \`all\` dataset

**URL:** https://discuss.opensanctions.org/t/notice-do-not-use-the-all-dataset/60
**Category:** Announcements
**Tags:** changelog, announcements
**Created:** [February 25, 2025, 10:22am UTC](https://discuss.opensanctions.org/t/notice-do-not-use-the-all-dataset/60 "2025-02-25T10:22:07Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Brenna](https://dub1.discourse-cdn.com/flex014/user_avatar/discuss.opensanctions.org/brenna/32/84_2.png) [@Brenna](https://discuss.opensanctions.org/u/Brenna)
#### Post date: [February 25, 2025, 10:22am UTC](https://discuss.opensanctions.org/t/notice-do-not-use-the-all-dataset/60/1 "2025-02-25T10:22:07Z")

</div>

We’d like to strongly advise all customers that are using the [`all`](https://www.opensanctions.org/datasets/all/) dataset to use [`default`](https://www.opensanctions.org/datasets/default/) instead.

The `all` dataset is an internal artifact of our data infrastructure. Other than having a pleasing name, it is a strictly inferior data product. As of February 2025, we’ve reduced the update frequency of `all` to monthly updates - meaning that **users of the `all` scope will use outdated data in their systems**.

`all` also includes data meant for internal verification/testing purposes which should not be included in production systems (unless you have a regulatory requirement to screen for 1990 “Die Hard” movie villain, John Gruber).
