IDVerse incident

Incident Name: Important Notice – Chrome 140/141 Update and Liveness Verification

Minor Resolved View vendor source →

IDVerse experienced a minor incident on September 5, 2025 affecting Liveness Engine API and Liveness Engine API and 1 more component, lasting 4h 10m. The incident has been resolved; the full update timeline is below.

Started
Sep 05, 2025, 06:30 AM UTC
Resolved
Sep 05, 2025, 10:41 AM UTC
Duration
4h 10m
Detected by Pingoru
Sep 05, 2025, 06:30 AM UTC

Affected components

Liveness Engine APILiveness Engine APILiveness Engine API

Update timeline

  1. identified Sep 05, 2025, 07:41 AM UTC

    The latest Google Chrome update (versions 140 and 141), which is currently being rolled out across some regions (if a user chooses to update), has introduced an issue impacting our platform’s liveness checks. Users encounter a black screen or 'oh no, something went wrong' during the liveness step, preventing them from completing video capture. Our engineering team has quickly identified the root cause and is actively developing a fix. The solution will need to be applied differently depending on the platform in use. - Engine/SDK : Update NPM Package to version 3.3.0 of the package: https://www.npmjs.com/package/liveness-js/v/3.3.0 - IDKit Enterprise : The product team is patching sites with the updated package. This will be applied to staging first and tested before moving into production - IDKit Saas : The team is currently working on the patch and we will update this page once live. For any liveness issues on Chromium browsers, please use a non-Chromium alternative such as Safari. We will provide an update on this status page once all patches have been deployed.

  2. identified Sep 05, 2025, 08:36 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Sep 05, 2025, 08:37 AM UTC

    We are continuing to work on a fix for this issue. In the meantime if issues are faced, please use another browser such as Safari, Samsung, Firefox etc.. Also please be aware not all users have the option to update their chrome browsers as Google does stagger their rollouts, and users still need to opt-in to update.

  4. identified Sep 05, 2025, 10:40 AM UTC

    This issue was confirmed to only impact desktop users on Chrome version 140 and above. Mobile users were not affected. There may still be issues affecting a minority of users on Microsoft Edge, which is under investigation. However, this appears to impact only a minority of Edge instances, so the broader incident is now considered closed.

  5. resolved Sep 05, 2025, 10:41 AM UTC

    This incident has been resolved.