All Systems Operational

Uptime over the past 90 days. View historical uptime.
Australia Operational
90 days ago
99.97 % uptime
Today
IDKit Enterprise Platform Operational
90 days ago
100.0 % uptime
Today
OCR & DFA Engine API ? Operational
90 days ago
100.0 % uptime
Today
Liveness Engine API ? Operational
90 days ago
99.98 % uptime
Today
Face Match Engine API ? Operational
90 days ago
100.0 % uptime
Today
DataConnect DVS API ? Operational
90 days ago
100.0 % uptime
Today
FraudHub Operational
90 days ago
100.0 % uptime
Today
IDKit Platform ? Operational
90 days ago
99.66 % uptime
Today
United Kingdom Operational
90 days ago
99.97 % uptime
Today
OCR & DFA Engine API ? Operational
90 days ago
100.0 % uptime
Today
Liveness Engine API ? Operational
90 days ago
100.0 % uptime
Today
Face Match Engine API ? Operational
90 days ago
100.0 % uptime
Today
IDKit Enterprise Platform ? Operational
90 days ago
100.0 % uptime
Today
FraudHub Operational
90 days ago
100.0 % uptime
Today
IDKit Platform ? Operational
90 days ago
99.66 % uptime
Today
USA ? Operational
90 days ago
99.97 % uptime
Today
OCR & DFA Engine API ? Operational
90 days ago
100.0 % uptime
Today
Liveness Engine API ? Operational
90 days ago
100.0 % uptime
Today
Face Match Engine API ? Operational
90 days ago
100.0 % uptime
Today
IDKit Enterprise Platform ? Operational
90 days ago
100.0 % uptime
Today
FraudHub Operational
90 days ago
100.0 % uptime
Today
IDKit Platform ? Operational
90 days ago
99.66 % uptime
Today
Canada Operational
90 days ago
100.0 % uptime
Today
Core Technologies ? Operational
90 days ago
100.0 % uptime
Today
IDKit Enterprise ? Operational
90 days ago
100.0 % uptime
Today
3rd Party Component Services ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Sep 6, 2025

No incidents reported today.

Sep 5, 2025
Incident Name: Important Notice – Chrome 140/141 Update and Liveness Verification
Resolved - This incident has been resolved.
Sep 5, 20:41 AEST
Update - This issue was confirmed to only impact desktop users on Chrome version 140 and above. Mobile users were not affected.

There may still be issues affecting a minority of users on Microsoft Edge, which is under investigation. However, this appears to impact only a minority of Edge instances, so the broader incident is now considered closed.
Sep 5, 20:40 AEST
Update - We are continuing to work on a fix for this issue. In the meantime if issues are faced, please use another browser such as Safari, Samsung, Firefox etc..

Also please be aware not all users have the option to update their chrome browsers as Google does stagger their rollouts, and users still need to opt-in to update.
Sep 5, 19:37 AEST
Update - We are continuing to work on a fix for this issue.
Sep 5, 17:36 AEST
Identified - The latest Google Chrome update (versions 140 and 141), which is currently being rolled out across some regions (if a user chooses to update), has introduced an issue impacting our platform’s liveness checks. Users encounter a black screen or 'oh no, something went wrong' during the liveness step, preventing them from completing video capture.

Our engineering team has quickly identified the root cause and is actively developing a fix. The solution will need to be applied differently depending on the platform in use.

- Engine/SDK : Update NPM Package to version 3.3.0 of the package: https://www.npmjs.com/package/liveness-js/v/3.3.0
- IDKit Enterprise : The product team is patching sites with the updated package. This will be applied to staging first and tested before moving into production
- IDKit Saas : The team is currently working on the patch and we will update this page once live.

For any liveness issues on Chromium browsers, please use a non-Chromium alternative such as Safari. We will provide an update on this status page once all patches have been deployed.
Sep 5, 16:30 AEST
Sep 4, 2025

No incidents reported.

Sep 3, 2025
IDKit - API Authorization errors post 1.56 release
Resolved - 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.
Sep 3, 11:00 AEST
Sep 2, 2025

No incidents reported.

Sep 1, 2025

No incidents reported.

Aug 31, 2025

No incidents reported.

Aug 30, 2025

No incidents reported.

Aug 29, 2025

No incidents reported.

Aug 28, 2025
Burst SMS - Degraded Messaging
Resolved - 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.
Aug 28, 11:08 AEST
Identified - 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
Aug 28, 10:19 AEST
Aug 27, 2025

No incidents reported.

Aug 26, 2025

No incidents reported.

Aug 25, 2025

No incidents reported.

Aug 24, 2025

No incidents reported.

Aug 23, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage