IDVerse incident

High rate of DFA-flagged applications since approximately 5:43AM AEDT

IDVerse experienced a major incident on October 17, 2025 affecting OCR & DFA Engine API and OCR & DFA Engine API and 1 more component, lasting 1h 2m. The incident has been resolved; the full update timeline is below.

Started: Oct 17, 2025, 11:56 PM UTC
Resolved: Oct 18, 2025, 12:59 AM UTC
Duration: 1h 2m
Detected by Pingoru: Oct 17, 2025, 11:56 PM UTC

Affected components

OCR & DFA Engine APIOCR & DFA Engine APIOCR & DFA Engine API3rd Party Component Services

Update timeline

investigating Oct 17, 2025, 11:56 PM UTC

We are currently investigating an issue involving certain clients where every transaction completed since approximately 5:43AM AEDT is returning HIGH RISK results for DFA without obvious cause Initial consultation with IDVerse Operations personnel has identified this as potentially originating from service disruptions with a 3rd party data vendor, however investigations remain ongoing. Please reach out to IDVerse Support for further assistance
identified Oct 18, 2025, 12:20 AM UTC

This has been confirmed as a 3rd party provider outage 'IPQS' https://www.ipqualityscore.com/. This is used for GeoFlagging https://ocrlabs.atlassian.net/servicedesk/customer/portal/1/article/1870462988. Previously the action was to wait for IPQS to come back online and then look at impacted transactions and have them re-processed. This is remaining to be the best course of action , however we will update once we know further. Please reach out if you require an immediate update in the meantime.
resolved Oct 18, 2025, 12:59 AM UTC

IDVerse Operations escalation to the 3rd party data vendor have resulted in a return to normal service as of approximately 11:23AM AEDT 18/10/25. Transaction results should now process as normal. IDVerse Support and Operations teams are continuing to manage and monitor the situation, however please reach out to IDVerse Support for any further queries or concerns