IDVerse incident
IDKit - Users unable to capture document, instead receive 'Couldn’t recognise your ID'
Resolved after 3 days 21 hours, affecting IDKit Platform, on August 1, 2025.
We have monitored the system post-resolution over the weekend and can confirm that it is now functioning as intended.
Affected components
Update timeline
- identified Aug 01, 2025, 03:26 AM UTC
We have heard reports of some user being unable to capture documents as part of the user flow. This is currently being investigated by the team.
- identified Aug 01, 2025, 03:26 AM UTC
This is currently under investigation.
- identified Aug 01, 2025, 04:18 AM UTC
We are continuing to work on a fix for this issue.
- identified Aug 01, 2025, 06:14 AM UTC
This has been confirmed to impact all IDKit saas regions. The fix is currently in progress and will provide further updates once deployed.
- monitoring Aug 01, 2025, 07:21 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 05, 2025, 12:12 AM UTC
We have monitored the system post-resolution over the weekend and can confirm that it is now functioning as intended.
Your product runs on more than IDVerse
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services