63 recorded Idnow incidents since March 2025, with official updates, affected components, duration and resolution information.
We are currently experiencing a performance degradation on our TEST system and are actively investigating the issue. Our team is working to identify the root cause and implement a solution. Customers using eSign with IDnow QTSP are affected.
We are currently experiencing a service disruption. Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Dear customers, On 21 October 2026, the PHP project released emergency updates for two critical vulnerabilities in the PHP runtime, together referred to as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Both allow unauthenticated remote code execution and are already being exploited in the wild. As soon as the patches were published, we assessed our assets against the affected versions. IDnow products and services are not affected. No product or service we provide to you runs a vulnerable PHP build, and our public website has been reviewed and is fully patched. No action is required from you currently. If your security team would like the technical basis for this assessment, our ServiceDesk team can arrange a call with the IDnow Security team. In case you have any questions or need further assistance, please contact IDnow Support: https://support.idnow.io
We are currently experiencing a service disruption on IDCheck sandbox environment. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
The services should be restored within the next 2 hours.
It is taking a bit longer than expected. The services should be restored by 18:00 today.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a service disruption. Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a degradation in performance and our team is actively investigating the root cause. We appreciate your patience and will post regular updates until service performance returns to normal.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a degradation in performance on our TEST system and our team is actively investigating the root cause. We appreciate your patience and will post regular updates until service performance returns to normal.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a service disruption. Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're experiencing an performance degradation and are currently looking into the issue. We will provide regular updates on the issue.
We identified a performance downgrade from 16:08 till 17:00.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a performance degradation and are actively investigating the issue. Our team is working to identify the root cause and implement a solution. Customers using eSign with IDnow QTSP are affected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a service disruption on our advanced signature service Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.
We are continuing to work on a fix for this issue.
The team is fixing the issue, the service should be restored within the next hour.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
*.identity.tm domains (including dedicated status page) are not resolved by the DNS, resulting in lack of access to the systems.
DNS resolution seems to be functioning again. We are collecting evidence for investigation.
This incident has been resolved.
We are currently experiencing a service disruption for the test robot. While running the test robot with HAPPYPATH scenario, if there is a data inconsistency between the initial data and the later submitted data to the TestRobot with HAPPYPATH, the result of the run will be SUCCESS_DATA_CHANGED (as in the CHANGEALL scenario.) In effect, this means -HAPPYPATH is currently not able to produce a SUCCESS outcome if the robot command is written to the first or last name. Other robot scenarios work properly. This only affects VideoIdent and eSign TEST robot. The AutoIdent products and InstantSign are not affected. Production is not affected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a service disruption. Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.
This incident has been resolved.
We identified a technical issue in our VideoIdent agent interface which causes a performance impact. The issue led to a reduced availability of video agents for end users on our VideoIdent and eSign services. A fix was deployed and we're monitoring the situation. AutoIdent, AutoIdent QES, eID and InstantSign were not affected.
This incident has been resolved.
We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a performance degradation and are actively investigating the issue. Our team is working to identify the root cause and implement a solution. Customers using eSign with IDnow QTSP are affected.
This incident has been resolved.
We are currently experiencing a service disruption on PVID. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently experiencing a service disruption. Our DevOps team is working to identify the root cause and implement a solution. eSigning users who use the Namirial TSP are affected. We will keep you updated with any new developments.
This incident has been resolved.
