Incidents reported on status page for OpenSanctions https://status.opensanctions.org/ https://d1lppblt9t2x15.cloudfront.net/logos/7c03ce50251a0ea5d6b127aa59a9d306.png https://status.opensanctions.org/ en https://status.opensanctions.org/ Wed, 03 Jun 2026 08:18:30 +0000 https://status.opensanctions.org/#8e14606dc4a9059836e01b21109bf13f74f129687ddaea7a966f3f3852f7a682 Publication of the `default` dataset recovered https://status.opensanctions.org/ Wed, 03 Jun 2026 06:18:11 +0000 https://status.opensanctions.org/#8e14606dc4a9059836e01b21109bf13f74f129687ddaea7a966f3f3852f7a682 Publication of the `default` dataset went down https://status.opensanctions.org/incident/909920 Mon, 01 Jun 2026 10:12:00 -0000 https://status.opensanctions.org/incident/909920#2b345ee85f53446b1aec829a93164681ca370b277e3cdf144ecd6acc8e551157 Deployments of yente 4 failed to update since 12:22 CEST Friday 28 May 2026. Our hosted API was not affected by this. The cause of this was resolved at 10:16 CEST Monday 1 June 2026 shortly after picking up a customer alerting us to the issue. Affected deployments should automatically update the next time they check for index updates. An affected instance would have shown the log entry `Metadata fetch error: Invalid url: None`. The next succeeding update would show the log entry `Refreshing manifest/catalog..` and shortly after `Indexing entities`. The cause of this was a dataset missing the metadata field `publisher.url` which is not currently a required field in more recent versions. We are releasing validation to ensure this field is present for existing yente 4 installations going forward. https://status.opensanctions.org/ Fri, 22 May 2026 06:16:18 +0000 https://status.opensanctions.org/#4268afd2a8fd803bd50f7f9ddf92e765dbe3bcb86ab6106412c86528c042c5aa Statement-based data API recovered https://status.opensanctions.org/ Fri, 22 May 2026 06:15:57 +0000 https://status.opensanctions.org/#e84cc127e91e632da0f2d6bb5e5432865096f9f16a637fcc579388225681e18e Search API recovered https://status.opensanctions.org/ Fri, 22 May 2026 06:15:26 +0000 https://status.opensanctions.org/#4268afd2a8fd803bd50f7f9ddf92e765dbe3bcb86ab6106412c86528c042c5aa Statement-based data API went down https://status.opensanctions.org/ Fri, 22 May 2026 06:15:09 +0000 https://status.opensanctions.org/#e84cc127e91e632da0f2d6bb5e5432865096f9f16a637fcc579388225681e18e Search API went down https://status.opensanctions.org/ Sat, 16 May 2026 23:42:41 +0000 https://status.opensanctions.org/#9cb6ad36bcb0de9e67e7ebd5e7ce1356fc642ba010719d68a086263da90c5616 Re-generate the global metadata index recovered https://status.opensanctions.org/ Sat, 16 May 2026 22:12:03 +0000 https://status.opensanctions.org/#9cb6ad36bcb0de9e67e7ebd5e7ce1356fc642ba010719d68a086263da90c5616 Re-generate the global metadata index went down https://status.opensanctions.org/ Tue, 12 May 2026 19:17:25 +0000 https://status.opensanctions.org/#a43753c1d74b36226826e87b6ec0b684504f20fb168869bbf700eb17b9d47260 Publication of the `default` dataset recovered https://status.opensanctions.org/ Tue, 12 May 2026 18:25:04 +0000 https://status.opensanctions.org/#a43753c1d74b36226826e87b6ec0b684504f20fb168869bbf700eb17b9d47260 Publication of the `default` dataset went down https://status.opensanctions.org/ Thu, 07 May 2026 14:09:08 +0000 https://status.opensanctions.org/#16eb3401a2ad8f492c0a93bfeab0f13330a520b6bc608bf40d358a7349310015 Publication of the `default` dataset recovered https://status.opensanctions.org/ Thu, 07 May 2026 12:23:06 +0000 https://status.opensanctions.org/#16eb3401a2ad8f492c0a93bfeab0f13330a520b6bc608bf40d358a7349310015 Publication of the `default` dataset went down https://status.opensanctions.org/ Thu, 07 May 2026 09:47:26 +0000 https://status.opensanctions.org/#ee596e892dc5ab77f0fdd6b84b0d0426a1a885dfca45bf270c835dad1138cac5 Re-generate the global metadata index recovered https://status.opensanctions.org/ Thu, 07 May 2026 09:12:03 +0000 https://status.opensanctions.org/#ee596e892dc5ab77f0fdd6b84b0d0426a1a885dfca45bf270c835dad1138cac5 Re-generate the global metadata index went down https://status.opensanctions.org/ Tue, 05 May 2026 00:14:25 +0000 https://status.opensanctions.org/#1fdba34e9cab7e1b2e82ae8cc0d20b9ffa8658f12a4acc49f76495577600d297 Statement-based data API recovered https://status.opensanctions.org/ Tue, 05 May 2026 00:13:48 +0000 https://status.opensanctions.org/#1fdba34e9cab7e1b2e82ae8cc0d20b9ffa8658f12a4acc49f76495577600d297 Statement-based data API went down https://status.opensanctions.org/incident/834919 Mon, 02 Mar 2026 09:40:27 -0000 https://status.opensanctions.org/incident/834919#e7c53c1f3b4a52457b9a3426dd882d4c87001cc08b6a3e38992d445caedd6453 tl;dr: On Monday, we’re **deploying a breaking change to our hosted API service** which removes the following fields from the `/match` response format: * `matcher` metadata at the root of the response (use `/algorithms` endpoint instead) * `features` from the individual result objects (use `explanations` instead) The change was announced and documented in August - for more detail, check the relevant changelog item: https://www.opensanctions.org/changelog/29/ https://status.opensanctions.org/incident/796564 Wed, 31 Dec 2025 09:56:00 -0000 https://status.opensanctions.org/incident/796564#82e429628a88a2bdda284edc9b1771b76e92cd63a574b12493059f5ab00945b4 As [announced in September](https://www.opensanctions.org/changelog/31/), we are now shutting down the legacy KYB API hosted at `api.graph.opensanctions.org`. We do not anticipate any impact on our main production API. https://status.opensanctions.org/incident/613006 Wed, 02 Jul 2025 10:46:00 -0000 https://status.opensanctions.org/incident/613006#8abdb1bba9f70011dfe4f28eddb6c514f132cf034adbe22e88439108709106a5 We're currently experiencing an issue affecting the export process for the default dataset. The sanctions dataset is not impacted. [A fix has been released](https://github.com/opensanctions/opensanctions/pull/2456). It is expected to take 4 hours for the export files to be updated. https://status.opensanctions.org/incident/607743 Thu, 26 Jun 2025 05:00:40 -0000 https://status.opensanctions.org/incident/607743#cecbbb9dea7be2d80d7cadd42987bcca42c0336513ccba5b88dbdf8886171e6d We are planning to migrate our main data service, `data.opensanctions.org` to a new hosting provider for CDN distribution. The service should function identically, bit the issuance of a new SSL/TLS certificate for the new hosting provider might lead to a brief outage during the migration. https://status.opensanctions.org/incident/605056 Thu, 19 Jun 2025 07:00:00 -0000 https://status.opensanctions.org/incident/605056#c39b94530baa32f136ef8c85bed7bee0202ca01d2d722b4108da2ffd74800d4f Maintenance on our accounts and statements database is planned for 10 minutes. Higher latency might be seen on matching, search and entity API requests during this time. Statements data might be unavailable during this time. Signing up and account details via the website such as viewing your usage might be unavailable during this time. https://status.opensanctions.org/incident/516727 Fri, 21 Feb 2025 13:16:00 -0000 https://status.opensanctions.org/incident/516727#0a44c14b3c39f7c40f93d59fdded77d41d3193eabed9b73ffe6d1d7c12dcb9f2 The data is now recovered. https://status.opensanctions.org/incident/516727 Fri, 21 Feb 2025 12:15:00 -0000 https://status.opensanctions.org/incident/516727#fc48631331cf82547f7b8ed1cb7075f6381e30f2aa227fdb9c980fba3ee582cb We've deployed a faulty change that limits our API to only "wanted" lists. We're shutting down the API service until the full scope of data has been re-indexed. https://status.opensanctions.org/incident/339884 Thu, 14 Mar 2024 10:00:00 -0000 https://status.opensanctions.org/incident/339884#ed0251d67d3406159843ff7a4d9d8e4f71b62b918350026b106eb5dc9d782115 We're planning to upgrade the accounts database in running in the backend of the API. The procedure should not incur any downtime but is irregular, so we announce it here. https://status.opensanctions.org/incident/291623 Mon, 04 Dec 2023 09:00:00 -0000 https://status.opensanctions.org/incident/291623#b47c99c166e30b5774a935ab4e0fe0f7289d5fefed0acc7240772d0e91b0ecf3 We're planning to switch the default scoring method used by the `/match` API to use the `logic-v1` implementation. The effect will be a change in the scores returned by the system for relevant matches. The current behaviour will remain available by adding the `algorithm=regression-v1` query parameter to requests. You can learn more about `logic-v1` scoring here: https://www.opensanctions.org/articles/2023-09-18-scoring-rules/ https://status.opensanctions.org/incident/273971 Tue, 17 Oct 2023 13:24:00 -0000 https://status.opensanctions.org/incident/273971#dc49238528725c8b035fecebbb4036a6a7d1d2376bf9d95757aa9ea199dd52f4 Within the next 24 hours, we're going to start serving some of the OpenSanctions bulk data files from `mirror.opensanctions.net` by default. Existing links to `data.opensanctions.org` will continue to work and can be used at any time instead. https://status.opensanctions.org/incident/269947 Sun, 08 Oct 2023 19:58:00 -0000 https://status.opensanctions.org/incident/269947#978af4d25e921df6a538095183d8ee0d78eb0974fd916f53267a0f89cee34200 After an indexing failure, we're generating a fresh index. ETA 20mins. https://status.opensanctions.org/incident/268038 Thu, 05 Oct 2023 13:00:00 -0000 https://status.opensanctions.org/incident/268038#30f93b9859120f451590f68d7508bca7367b6bdd9de28fcee272a8ea4a5a22eb We're going to deploy another iteration of the matching system, improving the accuracy and recall of the results. In particular, we're going to revert the scores returned via the `name-based` and `name-qualified` algorithms to the previous form (yente 3.6) and keep them fixed to those results from now on. We will also introduce a new mechanism to supply custom feature weights to the scoring system. https://status.opensanctions.org/incident/263644 Mon, 25 Sep 2023 09:00:00 -0000 https://status.opensanctions.org/incident/263644#c68223226bd8585df797ff9182f721c8656f6400b6cecb6a39dbbe981c649eff We're deploying a small upgrade to the scoring API which fixes an issue in the `regression-v1` algorithm in which a mismatch of dates of birth didn't result in the desired decrease of match score. https://status.opensanctions.org/incident/252764 Fri, 01 Sep 2023 10:00:00 -0000 https://status.opensanctions.org/incident/252764#d1755ea6f71e05528bf84e07e45b28364e90074b273a4d98ea46633ceabcf240 Maintenance completed https://status.opensanctions.org/incident/252764 Fri, 01 Sep 2023 08:00:00 -0000 https://status.opensanctions.org/incident/252764#d610f873a6092502459c6bd76d5639ef3030c0962b388b90b5ec0552a6cbb3d5 We're planning an upgrade to our SaaS billing system which requires database maintenance. This will incur a short window of downtime in the stated time frame. On the upside: we will likely lose an hour of usage metering data. So anyone who can get a request run during the maintenance period gets it for free :)