Resolved -
This incident has been resolved.
If you have any questions, please do not hesitate to contact us via https://customer.idnow.io/.
Jul 16, 17:12 CEST
Monitoring -
With the fix implemented yesterday on our TEST systems, our browser version of all products are working.
A solution for IDnow app and SDK solutions will be delivered in the upcoming days.
If you have any questions, please do not hesitate to contact us via https://customer.idnow.io/.
Jul 11, 10:22 CEST
Update -
We have implemented a fix for the ongoing problem of out TEST system. The fix works on the browser version of all products.
As a result of the fix, new IdentIDs will have the prefix TS2- . Existing IdentIDs with TST- will continue to work.
For IDnow app and SDK solutions, a fix will be delivered in the upcoming days.
If you have any questions, please do not hesitate to contact us via https://customer.idnow.io/.
Jul 10, 13:33 CEST
Update -
We are actively working on a fix for the ongoing problem with our TEST system.
We will provide an update once the fix has been successfully verified and implemented.
Thank you for your continued patience and understanding.
Jul 10, 10:02 CEST
Identified -
We have identified the cause behind the ongoing issue and are working on a fix. We will provide an update once the fix has been successfully verified and implemented.
Thank you for your continued patience and understanding.
Jul 9, 17:20 CEST
Update -
We are still actively investigating the ongoing issue and working to determine the root cause.
We will keep you updated with any new developments.
We apologize for the inconvenience caused.
Jul 9, 12:12 CEST
Update -
We are still actively investigating the ongoing issue. Unfortunately,we have not yet determined the root cause.
Our teams are working around the clock to resolve the issue. We will keep you updated with any new developments.
We apologize for the inconvenience caused.
Jul 8, 18:13 CEST
Update -
We are currently continuing our investigating into the ongoing issue with the TEST systems. At this moment, we have not yet identified the root cause.
Rest assured, our dedicated teams are working diligently to resolve the issue as quickly as possible.
We appreciate your patience and will provide further updates as soon as more information becomes available.
Jul 8, 12:57 CEST
Update -
We are continuing to investigate this issue to understand and remediate the root cause of the problem.
Jul 8, 09:28 CEST
Update -
Our investigation regarding the service disruption of our TEST systems is still ongoing. We will update the status page again as soon as we have a solution.
Jul 5, 13:03 CEST
Investigating -
We are currently experiencing a service disruption on our TEST system.
Our dedicated teams are working to identify the root cause and implement a solution. Users may not be able to finish identification.
We will send an additional update in 60 minutes.
Jul 5, 11:06 CEST