Jumio Outage History

We would like to inform you that we experienced an unexpected service interruption affecting our Rules service execution across our DC regions (US, EU, SGP). The issue has now been resolved, and the service is fully restored. We apologize for the inconvenience this may have caused. Our engineering teams have taken the necessary corrective actions to ensure this issue does not reoccur. We appreciate your patience and understanding during this time. For more details regarding the service disruption, please see below: Affected DC Regions: US, EU, SGP Started: 05:20 UTC We identified that the Rules service triggers were failing to execute across our DC regional environments, which may have impacted the final transaction decisioning process. Resolved: 12:05 UTC The Rules service logic was corrected, and all related service dependencies were successfully restored. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

We experienced a processing delay affecting some IDV transactions in all data centers. During the incident window, customers may have seen some delays in receiving callback response for transactions and in result retrieval. Incident Timeline (UTC) EU PROD Started time: 06:16:00 UTC Recovered time: 06:30:00 UTC SGP PROD Started time: 06:38:00 UTC Recovered time: 06:57:00 UTC US PROD Started time: 06:49:20 UTC Recovered time: 07:10:00 UTC All backlogged transactions have been processed. All incoming transactions continue to be processed at normal rates. We apologize for any inconvenience this may have caused. If you have further questions, please contact Jumio Support at https://support.jumio.com or [email protected].

We are pleased to inform you that the recent instability has been resolved, and our Identity Verification and Authentication services fully restored. We genuinely apologize for the inconvenience we caused. Our engineering staff has taken great care to make sure that the cause of this issue does not occur again. We appreciate your patience. For details of the service instability, please read below: At 15:40 UTC on 2026-05-09, we discovered unexpected issues. We have isolated the root cause and worked toward a full resolution. As of 19:47 UTC on 2026-05-09, the Identity Verification and Authentication have been restored to proper functionality, and is fully available. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

We experienced a delay affecting some identity verification transactions between 02:58UTC to 11:19 UTC. During the impacted window, transactions routed to manual review may have seen minor delays in receiving callback responses and in result retrieval. All backlogged transactions have been processed. All incoming transactions continue to be processed at normal rates. We apologize for any inconvenience this may have caused. If you have further questions, please contact Jumio Support at https://support.jumio.com or [email protected].

The issue affecting our US data center has been resolved. During the incident, customers may have experienced increased latency and delays when calling the Retrieval API service. Our engineering team identified and addressed the underlying cause, and services have now returned to normal operating levels. We apologize for any inconvenience this may have caused and appreciate your patience.

Between 06:56 UTC and 07:20 UTC, we experienced a processing delay in EU data center affecting Identity Verification transactions. During this period: Customers using Jumio Enterprise may have experienced delayed transaction processing. JumioGo customers may have observed a slightly higher rejection rate due to missing mandatory data points caused by auto-extraction failures. All services are now fully operational, and transaction processing has returned to normal. We appreciate your patience while we worked to resolve this issue.

We identified an issue affecting the Cross Transaction Risk capability across all data centers. During the impacted period, this feature did not execute as expected, which meant that any dependent rules either failed or did not execute. Issue Start: 08:18 AM UTC Issue Resolved: 11:00 AM UTC The feature is now fully restored and operating as intended. Please reach out to Support if you have any further questions or concerns.

We experienced a brief degradation in our EU data center at 19:33 UTC, which resulted in some delays in our transaction processing. Customers may have also experienced an increase in errors when calling our Retrieval API. NOTE: All services remain functional at this time. Apologies for the inconvenience.

All backlogged transactions have been processed. All incoming transactions continue to be processed at normal rates since 09:00 UTC on July 17th. We apologize for any inconvenience this may have caused and appreciate your patience.

All backlogged transactions have been processed. All incoming transactions continue to be processed at normal rates since 16:30 UTC on July 8th. We apologize for any inconvenience this may have caused and appreciate your patience.

We experienced a temporary service instability in our US, EU & SGP Data Center from 22.30 June 2nd UTC to 1:19 June 3rd UTC, which may have impacted the availability of the Retrieval API service and cause delay on Callback responses . The issue has been fully resolved, and we are taking proactive steps to prevent future occurrences. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

We experienced a temporary service instability in our US Data Center from 1:12 to 1:17 UTC, which may have impacted the availability of the Retrieval API service and cause delay on Callback responses . The issue has been fully resolved, and we are taking proactive steps to prevent future occurrences. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

All backlogged transactions have been processed. All incoming transactions continue to be processed at normal rates. We apologize for any inconvenience this may have caused.

All backlogged transactions have been processed. All incoming transactions continue to be processed at normal rates. We apologize for any inconvenience this may have caused.

We are pleased to inform you that the recent instability has been resolved, and our services are fully restored.

We experienced a temporary service interruption in the US Data Center from 12:01 PM to 12:11 PM UTC. During this time, some of our services may have returned a 5xx error. The issue has been resolved, and we are actively implementing measures to prevent similar occurrences in the future. We sincerely apologize for any inconvenience this may have caused and thank you for your patience and understanding.

We are pleased to inform you that the 504 timeout error has been resolved, and our services in the U.S. DC are fully restored. We genuinely apologize for the inconvenience we caused. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

We experienced a disruption in CPF Validation services across all data centers (US, EU, and SGP) from Friday, December 20, 9:40 PM UTC to Saturday, December 21, 4:20 AM UTC. As a result, workflows utilizing the CPF Validation check capability encountered failures, returning a NOT_EXECUTED/TECHNICAL_ERROR decision. The issue has been addressed, and services have been fully restored. We sincerely apologize for any inconvenience this may have caused and thank you for your understanding and patience. If you have any questions or concerns, please do not hesitate to reach out.

All incoming transactions are now being processed at normal rates. We apologize for any inconvenience this may have caused.

After careful monitoring, we are pleased to inform you that the recent instability on our US datacenter has been resolved, and all our services are now fully restored. We sincerely apologize for any inconvenience caused. At 09:25 am UTC on 2024-08-19, we identified intermittent issues with our Verification services on the US datacenter affecting SDK customers, potentially causing errors during the user journey. At 10:00 am UTC on 2024-08-19, we confirmed that all services were fully restored and are functioning as expected. If you have any questions, please contact Jumio Support at https://support.jumio.com

After careful monitoring, we are pleased to inform you that the recent instability on our US datacenter has been resolved, and all our services are now fully restored. We sincerely apologize for any inconvenience caused. At 10:13 pm UTC on 2024-07-30, we discovered unexpected issues with our Verification services on US datacenter. At 10:54 pm UTC on 2024-07-30, the issue related to global AWS issue with multiple services in US region. At 5:05 am UTC on 2020-07-31 AWS fully recovered their services in US region. Jumio's services have been restored to proper functionality and are fully available, but we have them under monitoring and continue to work on reprocessing the pending scans. At 6:46 am UTC on 2024-07-31, we confirmed that all the services has been restored to proper functionality and are working as expected. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

We are pleased to inform you that the recent instability has been resolved, and our Identity Verification and Authentication services are fully restored. We genuinely apologize for the inconvenience caused. For details of the service instability, please read below: Incident Started: 16:00 UTC on 2024-07-25 Incident Resolved: 16:24 UTC on 2024-07-25 If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

After careful monitoring, we are pleased to inform you that the recent instability on our EU datacenter has been resolved, and all our services are now fully restored. We sincerely apologize for any inconvenience caused. Our engineering team has diligently addressed the matter to prevent a recurrence. At 4:17 am UTC on 2024-07-09, we discovered unexpected issues with all of our Verification services on EU datacenter. At 4:42 am UTC on 2024-07-09, the services have been restored to proper functionality and are fully available, but we have them under monitoring. At 5:05 am UTC on 2024-07-09, we confirmed that all the services has been restored to proper functionality and are working as expected. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].