IDVerse Enterprise site Returns "504 Gateway Timeout ERROR"
Affected: IDKit Enterprise PlatformOCR & DFA Engine APIIDKit Enterprise PlatformIDKit EnterpriseIDKit Enterprise Platform
IDVerse Outage History
IDVerse is up right nowIDVerse had 14 outages in the last 2 years totaling 2967h 4m of downtime — averaging 0.6 incidents per month.
There were 14 IDVerse outages since August 1, 2025 totaling 2967h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.
DVS PRODUCTION Intermittent Outage - All Document Types
Timeline · 1 update
- resolved Jun 12, 2026, 04:24 AM UTC
Document/s Affected: All Document Types Start Date and Time: 12 June 2026 — 10:00AM AEST End Date and Time: 12 June 2026 — 12:15PM AEST Issue is now resolved. Last failed transaction was at 10:53 AM.
IDVerse Enterprise staging site Returns "503 Service Temporarily Unavailable"
Affected: IDKit Enterprise PlatformIDKit Enterprise PlatformIDKit EnterpriseIDKit Enterprise PlatformIDKit Enterprise Platform
Timeline · 2 updates
- monitoring Jun 04, 2026, 02:34 AM UTC
As part of ongoing platform lifecycle and security management activities, certain IDVerse Enterprise staging environments have transitioned to a controlled access model in alignment with current LexisNexis Risk Solutions security standards. The staging environments themselves remain operational and available for active delivery, testing, and migration activities where required. Access is now managed through a coordinated enablement process based on active business or project requirements. If staging access is currently returning error '503', the IDVerse team can assist with enabling access for agreed periods through the standard support and coordination process. For questions or to re‑activate access, please reach out to IDVerse Support via the appropriate support channel: - Support portal: https://lnrs.my.site.com/IDVerseSupportDesk - Email: [email protected]
- resolved Jun 30, 2026, 10:29 PM UTC
This incident has been resolved.
Sender ID Registrations in Australia - Regulation change July 1st 2026
Affected: 3rd Party Component Services
Timeline · 2 updates
- identified May 29, 2026, 06:18 AM UTC
The Australian Communications and Media Authority (ACMA) has issued an urgent call-to-action for organisations that use branded SMS messages sending to Australian Phone Numbers. A new mandatory SMS Sender ID Register will apply from 1 July 2026. To find out more please read: https://enterprise.docs.idverse.com/docs/required-information-for-sender-id-registrations
- resolved Jul 09, 2026, 03:09 AM UTC
This incident has been resolved.
DVS PRODUCTION - Intermittent Outage - Medicare
Affected: IDKit Enterprise PlatformIDKit Platform
Timeline · 2 updates
- investigating Apr 07, 2026, 04:07 AM UTC
DVS have advised as of 7 April 2026 — 1:31PM AEST of an intermittent outage impacting Medicare cards You may receive system errors 'S' responses until the issue is resolved
- resolved Apr 08, 2026, 06:18 AM UTC
Services were restored as of 7:37PM 07 April 2026 AEST
High rate of DFA-flagged applications since approximately Feb 8th - 4PM AEDT
Affected: 3rd Party Component Services
Timeline · 5 updates
DVS Production Intermittent Outage - All Documents
Affected: 3rd Party Component Services
Timeline · 2 updates
- investigating Dec 19, 2025, 04:54 AM UTC
We are advised of a DVS intermittent outage impacting all documents as of 19/12/2025 15:15PM AEDT You may receive system errors 'S' responses until the issue is resolved
- resolved Dec 19, 2025, 06:42 AM UTC
DVS advise that as of 19/12/2025 16:12 PM all services have been restored
High rate of DFA-flagged applications between approximately 12AM - 3:20AM AEDT
Affected: 3rd Party Component Services
Timeline · 5 updates
- investigating Nov 18, 2025, 10:31 PM UTC
We are investigating an issue for some clients where many transactions completed between roughly 12:00 AM and 3:20 AM AEDT are returning HIGH RISK DFA results unexpectedly. Our initial review with IDVerse Operations suggests the issue may be linked to service disruptions from our GeoData provider, IPQS (https://www.ipqualityscore.com). Investigations are continuing and will provide updates as they become available. If you need any potentially impacted transactions reprocessed, please submit a ticket to the support team for review.
- investigating Nov 18, 2025, 10:31 PM UTC
We are continuing to investigate this issue.
- monitoring Nov 18, 2025, 10:33 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Nov 18, 2025, 10:34 PM UTC
We are continuing to monitor for any further issues.
- resolved Nov 19, 2025, 03:49 AM UTC
This was resolved approximately 3:20 AM AEDT, and was confirmed to be related to the cloudflare incident (https://www.cloudflarestatus.com/) that also impacted IPQS. If you need any potentially impacted transactions reprocessed, please submit a ticket to the support team for review.
DVS - Production Intermittent Outage (Passports)
Affected: 3rd Party Component Services
Timeline · 2 updates
- identified Oct 30, 2025, 05:02 AM UTC
DVS advised as of October 30th 2025 - 03:00 AEST there is an intermittent outage affecting passport and Electoral Commission documents. Outage being resolved by Microsoft Azure and services are now recovering. You may receive system errors 'S' responses until the issue is resolved.
- resolved Dec 19, 2025, 06:54 AM UTC
This issue is understood to have been impacting periodically between 30/10/25 - noting the following chain of events: > 30/10 outage first indicated as resolved on 08/12 > Issue reoccurred 11/12 and resolved on 12/12 > Issue reoccured 16/12 and resolved on 17/12 Due to the ongoing nature of this intermittent outage, continuation of this outage advice has remained. This incident is now marked as resolved as no further indication from DVS has established continuity of this original incident from September '25. Any issues or concerns, please feel free to reach out to IDVerse Support
High rate of DFA-flagged applications since approximately 5:43AM AEDT
Affected: OCR & DFA Engine APIOCR & DFA Engine APIOCR & DFA Engine API3rd Party Component Services
Timeline · 3 updates
- 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
Incident Name: Important Notice – Chrome 140/141 Update and Liveness Verification
Affected: Liveness Engine APILiveness Engine APILiveness Engine API
Timeline · 5 updates
IDKit - API Authorization errors post 1.56 release
Timeline · 1 update
- resolved Sep 03, 2025, 10:52 PM UTC
Version 1.56 was released on September 3rd at 10:50 AM Sydney time (AEST). This release inadvertently removed the authentication header from webhook notification calls. As a result, webhook requests failed with a 401 Unauthorized error. While this issue did not impact end-user flows or engine decisioning, it prevented customer platforms from receiving webhook notifications for completed transactions. The issue was resolved at 5:44 PM Sydney time (AEST) on the same day.
Burst SMS - Degraded Messaging
Affected: 3rd Party Component Services
Timeline · 2 updates
- identified Aug 28, 2025, 12:54 AM UTC
Customer Degraded Messaging Burst SMS (used by many customers in the APAC regioN) have identified a potential issue in their systems and are currently investigating remediation options. Users may also additionally see intermittent issues logging into their account via the UI. Note: Messages should be added to queues and not lost. Live incident updates with Burst can be tracked here: https://status.transmitsms.com/incidents/2qtyfkq6hkmc
- resolved Aug 28, 2025, 01:56 AM UTC
A fix was implemented at 11:08 AEST with ongoing monitoring can confirm the issue has been fixed. Transactions/SMS's do not need to be re-sent as SMS's were queued and should have since been delivered.
IDKit - Users unable to capture document, instead receive 'Couldn’t recognise your ID'
Affected: IDKit Platform
Timeline · 6 updates
- 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.