IDVerse Outage History

IDVerse is up right now

IDVerse had 13 outages in the last 2 years totaling 1355h 11m of downtime — averaging 0.5 incidents per month.

There were 13 IDVerse outages since July 28, 2025 totaling 1355h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ocrlabs.com

Notice June 12, 2026

DVS PRODUCTION Intermittent Outage - All Document Types

Detected by Pingoru
Jun 12, 2026, 12:00 AM UTC
Resolved
Jun 12, 2026, 12:00 AM UTC
Duration
Timeline · 1 update
  1. 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.

Read the full incident report →

Minor April 7, 2026

DVS PRODUCTION - Intermittent Outage - Medicare

Detected by Pingoru
Apr 07, 2026, 04:07 AM UTC
Resolved
Apr 07, 2026, 09:37 AM UTC
Duration
5h 29m
Affected: IDKit Enterprise PlatformIDKit Platform
Timeline · 2 updates
  1. 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

  2. resolved Apr 08, 2026, 06:18 AM UTC

    Services were restored as of 7:37PM 07 April 2026 AEST

Read the full incident report →

Major December 19, 2025

DVS Production Intermittent Outage - All Documents

Detected by Pingoru
Dec 19, 2025, 04:54 AM UTC
Resolved
Dec 19, 2025, 05:12 AM UTC
Duration
17m
Affected: 3rd Party Component Services
Timeline · 2 updates
  1. 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

  2. resolved Dec 19, 2025, 06:42 AM UTC

    DVS advise that as of 19/12/2025 16:12 PM all services have been restored

Read the full incident report →

Major November 18, 2025

High rate of DFA-flagged applications between approximately 12AM - 3:20AM AEDT

Detected by Pingoru
Nov 18, 2025, 05:00 PM UTC
Resolved
Nov 19, 2025, 03:49 AM UTC
Duration
10h 48m
Affected: 3rd Party Component Services
Timeline · 5 updates
  1. 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.

  2. investigating Nov 18, 2025, 10:31 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 18, 2025, 10:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Nov 18, 2025, 10:34 PM UTC

    We are continuing to monitor for any further issues.

  5. 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.

Read the full incident report →

Minor October 29, 2025

DVS - Production Intermittent Outage (Passports)

Detected by Pingoru
Oct 29, 2025, 04:00 PM UTC
Resolved
Dec 19, 2025, 06:54 AM UTC
Duration
50d 14h
Affected: 3rd Party Component Services
Timeline · 2 updates
  1. 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.

  2. 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

Read the full incident report →

Major October 17, 2025

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

Detected by Pingoru
Oct 17, 2025, 11:56 PM UTC
Resolved
Oct 18, 2025, 12:59 AM UTC
Duration
1h 2m
Affected: OCR & DFA Engine APIOCR & DFA Engine APIOCR & DFA Engine API3rd Party Component Services
Timeline · 3 updates
  1. 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

  2. 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.

  3. 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

Read the full incident report →

Notice September 3, 2025

IDKit - API Authorization errors post 1.56 release

Detected by Pingoru
Sep 03, 2025, 01:00 AM UTC
Resolved
Sep 03, 2025, 01:00 AM UTC
Duration
Timeline · 1 update
  1. 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.

Read the full incident report →

Minor August 28, 2025

Burst SMS - Degraded Messaging

Detected by Pingoru
Aug 28, 2025, 12:19 AM UTC
Resolved
Aug 28, 2025, 01:08 AM UTC
Duration
48m
Affected: 3rd Party Component Services
Timeline · 2 updates
  1. 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

  2. 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.

Read the full incident report →

Critical August 1, 2025

IDKit - Users unable to capture document, instead receive 'Couldn’t recognise your ID'

Detected by Pingoru
Aug 01, 2025, 02:26 AM UTC
Resolved
Aug 05, 2025, 12:12 AM UTC
Duration
3d 21h
Affected: IDKit Platform
Timeline · 6 updates
  1. 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.

  2. identified Aug 01, 2025, 03:26 AM UTC

    This is currently under investigation.

  3. identified Aug 01, 2025, 04:18 AM UTC

    We are continuing to work on a fix for this issue.

  4. 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.

  5. monitoring Aug 01, 2025, 07:21 AM UTC

    A fix has been implemented and we are monitoring the results.

  6. 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.

Read the full incident report →

Critical July 28, 2025

AU Region - IDVerse Liveness API Outage

Detected by Pingoru
Jul 28, 2025, 06:46 AM UTC
Resolved
Jul 28, 2025, 11:08 PM UTC
Duration
16h 21m
Affected: Liveness Engine API
Timeline · 2 updates
  1. monitoring Jul 28, 2025, 06:46 AM UTC

    IDVerse Operations have advised of a 13 minute outage of the Liveness API endpoint in the AU region between 06:14 to 06:27 UTC (16:14 to 16:27 AEST) today 28/07/25 This issue would have presented as a nondescript error at the Liveness stage of an Identity Verification, potentially impacting the completion of Liveness capture until the issue was resolved. Whilst we expect any current applications impacted can be retried with success, please reach out to to IDVerse Support for further assistance

  2. resolved Jul 28, 2025, 11:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 28, 2025

Liveness Outage - AU server (4:14pm AEST - 4:27 AEST)

Detected by Pingoru
Jul 28, 2025, 06:30 AM UTC
Resolved
Jul 28, 2025, 06:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Jul 28, 2025, 06:45 AM UTC

    AU Liveness Engine outage from 4:14pm AEST - 4:27 AEST (06:14 to 06:27 UTC). The error encountered during liveness capture has been resolved. Customers are now able to return and complete previously impacted transactions

Read the full incident report →