Jumio Outage History

Started Oct 20, 2026, 04:31 PM UTC· resolved Oct 20, 2026, 06:42 PM UTC

1. identified Oct 20, 2026, 04:31 PM UTC

   We are currently experiencing processing delays affecting a subset of Identity Verification transactions across our US, EU, and SGP data centers, starting at approximately 15:00 UTC. Transactions routed to manual review during this window may experience delayed Callback and Retrieval responses. All other services remain fully operational. We apologize for any disruption this may cause and appreciate your patience, and will provide another update as soon as service is fully restored.

2. monitoring Oct 20, 2026, 06:12 PM UTC

   Processing delays for Identity Verification transactions have been mitigated, and queue levels are recovering. We are currently monitoring system health and response times to ensure continued stability. Further updates will be provided once fully resolved.

3. resolved Oct 20, 2026, 06:42 PM UTC

   Monitoring is complete, all backlogged transactions have been processed and all incoming transactions continue to be processed at normal rates. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Oct 01, 2026, 08:43 PM UTC· resolved Oct 02, 2026, 10:21 AM UTC

1. identified Oct 01, 2026, 08:43 PM UTC

   We are currently experiencing a service degradation affecting our backend processing services across Identity Verification and DocProof services. Overall transaction processing is experiencing processing delays, and fully automated transactions may encounter intermittent failures with the reject reason MISSING_MANDATORY_DATAPOINTS. Root cause: Our engineering team identified an underlying OCR model issue causing failures in data extraction for ID documents and DocProof transactions, leading to processing delays and unexpected rejections. Next steps: Our engineering team is actively working to mitigate the issue and restore full system performance. We sincerely apologize for the inconvenience and appreciate your patience. We will provide further updates as more information becomes available. If you have any immediate questions, please contact Jumio Support at https://support.jumio.com or [email protected].

2. identified Oct 01, 2026, 11:37 PM UTC

   While automated errors have cleared for the US region, our backend processing services across Identity Verification and DocProof continue to experience transaction backlogs globally. Regional impact breakdown: - US Data Center: Errors have fully cleared. Customers should no longer be experiencing MISSING_MANDATORY_DATAPOINTS rejections, though overall transactions may still experience processing delays due to backlogs. - EU & SGP Data Centers: Remain affected by both processing delays and errors. Fully automated transactions in these regions may still encounter intermittent failures returning the rejection reason MISSING_MANDATORY_DATAPOINTS. Next steps: Our team is actively working to clear the processing backlogs, restore full system performance globally, and monitor regional recovery. We sincerely apologize for the inconvenience and appreciate your patience. We will provide further updates as more information becomes available. For assistance, please contact Jumio Support at [email protected] or visit https://support.jumio.com.

3. monitoring Oct 02, 2026, 12:31 AM UTC

   System performance across all data centers (US, EU, and SGP) has stabilized. Current status & Regional impact: - Errors cleared globally: The elevated error rates and intermittent MISSING_MANDATORY_DATAPOINTS rejections affecting fully automated transactions have now stopped across all data centers, and error rates have returned to normal levels. - Ongoing backlog processing: While real-time transaction processing and error rates have normalized, our backend services continue to process the transaction backlog. As a result, customers may still experience temporary processing delays. Next steps: Our engineering team is actively monitoring system performance and backlog recovery across all regions. We sincerely apologize for the disruption caused by this incident and appreciate your continued patience. We will provide a final update once all backlogs have fully cleared. For assistance, please contact Jumio Support at [email protected] or visit https://support.jumio.com.

4. resolved Oct 02, 2026, 10:21 AM UTC

   We are pleased to inform you that the recent instability affecting our Identity Verification and DocProof services has been fully resolved. All incoming requests, including manual reviews, are processing as expected. Additionally, all backlogged transactions have been cleared, and processing latency has returned to normal levels. We apologize for the inconvenience and appreciate your patience while we worked to resolve the issue.

Read the full incident report →

Started Oct 01, 2026, 02:28 PM UTC· resolved Oct 01, 2026, 03:06 PM UTC

1. resolved Oct 01, 2026, 05:24 PM UTC

   At approximately 2026-10-01 02:28 PM UTC, we experienced a performance degradation affecting our IDV services across all data centers. Affected customers may have experienced intermittent MISSING_MANDATORY_DATAPOINTS rejections. At 03:06 PM UTC on October 01, 2026, our Engineering team identified an underlying OCR model issue causing extraction failures for ID documents without Machine Readable Zones (MRZ). This issue also resulted in increased processing times for IDV transactions requiring human review, as well as unexpected rejections with the MISSING_MANDATORY_DATAPOINTS error code. The issue has been fully resolved, and all system operations have returned to normal performance. No further impact is expected. We appreciate your patience and understanding throughout this incident. If you have any questions or require further assistance, please contact Jumio Support at https://support.jumio.com.

Read the full incident report →

Started Sep 02, 2026, 11:01 AM UTC· resolved Sep 02, 2026, 11:33 AM UTC

1. investigating Sep 02, 2026, 11:01 AM UTC

   Since 10:15 UTC, Identity Verification and Authentication services in the SGP data center have been experiencing an outage. Our team is actively investigating to restore service as quickly as possible. All other services remain fully operational. We apologize for any inconvenience and will provide an update once resolved. For assistance, please contact Jumio Support at [email protected] or visit https://support.jumio.com.

2. investigating Sep 02, 2026, 11:03 AM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 02, 2026, 11:08 AM UTC

   Identity Verification and Authentication services in the SGP data center were fully restored as of 10:50 UTC. All systems are now operating normally, and our team continues to actively monitor performance to ensure ongoing stability. We sincerely apologize for any disruption or inconvenience this issue may have caused. If you continue to experience issues or have any questions, please contact Jumio Support at [email protected] or visit https://support.jumio.com.

4. resolved Sep 02, 2026, 11:33 AM UTC

   The service disruption affecting Identity Verification and Authentication in the SGP data center has been fully resolved. Impacted Services: Identity Verification & Authentication (WEB and Mobile) Start Time: 10:15 UTC Resolved Time: 10:50 UTC Current Status: Resolved Following a period of active monitoring, all services are confirmed to be operating normally. We sincerely apologize for any inconvenience this issue may have caused. If you continue to experience any issues or have questions, please reach out to Jumio Support at [email protected] or visit https://support.jumio.com.

Read the full incident report →

Started Jul 03, 2026, 08:26 AM UTC· resolved Jul 03, 2026, 03:57 PM UTC

1. identified Jul 03, 2026, 08:26 AM UTC

   Incident Notice: Document Verification (DocProof) Processing Delay We are currently experiencing a processing delay across all data centers for Document Verification (DocProof) transactions that involve manual processing. The issue began at 05:35 UTC on July 3, 2026. Current Status: All services remain operational, and our team is actively working to process the accumulated backlog and restore normal processing times. We will provide further update once normal processing times have been fully restored. We sincerely apologize for any inconvenience this may cause and appreciate your patience and understanding.

2. resolved Jul 03, 2026, 03:57 PM UTC

   Processing times have returned to normal, and the backlog has been successfully cleared. All DocProof transactions, including those requiring manual review, are now being processed as expected. We apologize for any inconvenience this incident may have caused and appreciate your patience and understanding while we worked to resolve the issue.

Read the full incident report →

Started Jun 17, 2026, 03:28 PM UTC· resolved Jun 18, 2026, 09:30 AM UTC

1. resolved Jun 18, 2026, 05:10 PM UTC

   An inadvertent behaviour was identified in an internal Web Client deployment that prevented some users from completing their verification journey during the Selfie/Liveness capture step. The Engineering team identified the root cause and deployed a fix to resolve the issue affecting the liveness acquisition flow. Issue Start Time: June 17, 2026, 3:28 PM UTC Issue Mitigation Time: June 18, 2026, 9:30 AM UTC Current Status: All services are fully operational at this time. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

Read the full incident report →

Started May 25, 2026, 07:10 AM UTC· resolved May 26, 2026, 07:10 AM UTC

1. resolved May 26, 2026, 08:13 AM UTC

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

Read the full incident report →

Started May 25, 2026, 05:20 AM UTC· resolved May 25, 2026, 12:05 PM UTC

1. resolved May 25, 2026, 05:19 PM UTC

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

Read the full incident report →

Started May 09, 2026, 06:07 PM UTC· resolved May 09, 2026, 07:53 PM UTC

1. identified May 09, 2026, 06:07 PM UTC

   We’re really sorry to be holding you up today! Please know our engineering and operations teams are working hard to get everything up and running. All other services are fully operational. We'll provide an update as soon as the issue is resolved. We apologize for any inconvenience and appreciate your patience. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

2. identified May 09, 2026, 06:19 PM UTC

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

3. identified May 09, 2026, 06:20 PM UTC

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

4. identified May 09, 2026, 06:23 PM UTC

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

5. monitoring May 09, 2026, 07:37 PM UTC

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

6. resolved May 09, 2026, 07:53 PM UTC

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

Read the full incident report →

Started Apr 23, 2026, 03:05 AM UTC· resolved Apr 23, 2026, 11:31 AM UTC

1. identified Apr 23, 2026, 03:05 AM UTC

   We are currently experiencing a delay in processing on all data centers for Identity Verification transactions. Transactions routed to manual review may have seen minor delays in receiving callback responses and in result retrieval. Please note that All services remain functional at this time, and we will update here when the service is fully restored. We apologize for any disruption this may have caused and appreciate your patience as our team worked to restore full service

2. resolved Apr 23, 2026, 11:31 AM UTC

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

Read the full incident report →

Started Apr 06, 2026, 05:30 PM UTC· resolved Apr 06, 2026, 06:47 PM UTC

1. identified Apr 06, 2026, 05:30 PM UTC

   We are currently experiencing a brief degradation in our US DC data center. During this time, customers may experience delays when calling the Retrieval API endpoint service. Our team is actively investigating the issue and will provide further updates as more information becomes available.

2. resolved Apr 06, 2026, 06:47 PM UTC

   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.

Read the full incident report →

Started Jan 05, 2026, 08:20 AM UTC· resolved Jan 05, 2026, 08:23 AM UTC

1. investigating Jan 05, 2026, 08:20 AM UTC

   We are currently experiencing a delay in processing on EU data centers for Identity Verification transactions. For Jumio Enterprise Customers: These transactions were successfully processed but experienced increased latency. For JumioGo Customers: Some transactions may have encountered higher rejection rates. This was due to auto-extraction failures resulting in missing mandatory data points. NOTE: All services remain functional at this time, and we will send you another notification when the service is fully restored. Apologies for the inconvenience.

2. resolved Jan 05, 2026, 08:23 AM UTC

   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.

Read the full incident report →

Started Oct 20, 2025, 08:11 AM UTC· resolved Oct 21, 2025, 02:00 AM UTC

1. identified Oct 20, 2025, 08:11 AM UTC

   We are currently experiencing a service outage in our US data center due to an AWS server outage. The incident began around 07:11 UTC on 2025-10-20. At 07:23 UTC, we identified the instability and are now working closely with AWS to urgently mitigate the issue. In the meantime, please refrain from creating or updating any workflow rules on all data centers until the issue is fully resolved. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

2. monitoring Oct 20, 2025, 10:17 AM UTC

   We are pleased to inform you that AWS has gradually restored its services. Though it is not completely resolved yet, we are seeing more transactions successfully processed in our US data center. We are actively monitoring the situation and continuing to reprocess the pending scans, which is expected to take a few more hours. Additionally, we observed some slow processing cases for IDV in our EU and SGP data centers between 07:50 and 08:00 UTC. However, services in both data centers have been fully restored since then. We apologize for any inconvenience and appreciate your patience. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected]

3. monitoring Oct 20, 2025, 04:24 PM UTC

   We are continuing to observe partial recovery in AWS services affecting Jumio’s US data center. At this time some IDV transactions continue to be incorrectly rejected and delays in transaction processing are being observed across all data centers. Our engineering team is actively monitoring the situation and working closely with AWS to ensure full recovery as soon as possible. We will continue to provide updates as AWS restores full service availability. We apologize for any inconvenience and appreciate your patience. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

4. monitoring Oct 20, 2025, 07:30 PM UTC

   Our systems are currently partially processing transactions, and services have not yet fully returned to normal in the US data center. The disruption continues to be caused by an ongoing AWS incident in the US region. There are no further mitigation steps available from our side at this time, and we are awaiting AWS to restore full functionality. Our engineering team is actively monitoring the situation and will act quickly to bring all services back to normal as soon as AWS resolves the issue. We will continue to provide updates as more information becomes available. We apologize for any inconvenience and appreciate your patience. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

5. monitoring Oct 20, 2025, 11:45 PM UTC

   AWS has confirmed that their services are now fully operational, and our internal testing indicates that Jumio services are functioning normally. As with any large-scale recovery, some intermittent issues may still occur as traffic levels return to normal. We’re continuing to monitor closely system's performance and will take immediate action should any anomalies arise. We appreciate your patience throughout this incident. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

6. resolved Oct 21, 2025, 02:00 AM UTC

   All Jumio services remain stable following continued monitoring after AWS’s full recovery. No further impact is expected. Transactions that failed during the outage will need to be resubmitted for processing. We appreciate your patience throughout this incident. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

Read the full incident report →

Started Sep 11, 2025, 08:00 AM UTC· resolved Sep 11, 2025, 11:00 AM UTC

1. resolved Sep 11, 2025, 11:09 AM UTC

   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.

Read the full incident report →

Started Aug 07, 2025, 09:45 PM UTC· resolved Aug 07, 2025, 09:45 PM UTC

1. resolved Aug 07, 2025, 09:56 PM UTC

   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.

Read the full incident report →

Started Jul 16, 2025, 01:01 PM UTC· resolved Jul 17, 2025, 09:12 AM UTC

1. identified Jul 16, 2025, 01:01 PM UTC

   We're currently experiencing delays in processing Identity Verification and Doc Proof transactions across all our data centers. This issue began around 10:00 UTC. All other services are fully operational. We'll provide an update as soon as the issue is resolved. We apologize for any inconvenience and appreciate your patience.

2. monitoring Jul 16, 2025, 07:01 PM UTC

   We’re currently experiencing degraded performance issues which impacted across our US,EU,SGP data centers . Our team is currently working to restore normal performance levels in a timely manner . We apologize for any inconvenience, will share a new update once our internal services are fully operational. We appreciate your patience as our team works to resolve the issue.If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

3. resolved Jul 17, 2025, 09:12 AM UTC

   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.

Read the full incident report →

Started Jul 08, 2025, 02:32 AM UTC· resolved Jul 08, 2025, 07:12 PM UTC

1. investigating Jul 08, 2025, 02:32 AM UTC

   We are currently experiencing a delay in processing ID and IV verification transactions in our U.S. data centers. This issue began at 00:50 UTC on July 8th and is affecting the availability of Usability checks, resulting in delays in transaction processing. Our team is actively investigating and working to resolve the issue as quickly as possible. We apologize for any inconvenience and appreciate your patience. NOTE: All services remain functional at this time, and we will send you another notification when the service is fully restored. Apologies for the inconvenience.

2. monitoring Jul 08, 2025, 04:35 AM UTC

   Our top priority is to fully restore your services and ensure a smooth, reliable identity verification experience for your end users. We sincerely apologize for the disruption and inconvenience this has caused. We have identified the root cause of the issue and have implemented a fix at 03:14am UTC. In addition, we are taking proactive steps to prevent it from happening again. While the primary issue has been addressed, we are still working through the remaining backlog. We will continue to keep you informed as more updates become available.

3. resolved Jul 08, 2025, 07:12 PM UTC

   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.

Read the full incident report →

Started Jun 17, 2025, 02:38 PM UTC· resolved Jun 20, 2025, 05:09 PM UTC

1. identified Jun 17, 2025, 02:38 PM UTC

   Conversion Degradation on Android Chrome Since June 16th, we have observed a decline in conversion rates across all our data centers (US, EU, and SGP). This issue has affected our Identity Verification and Authentication services, causing some transactions to fail and return a "NOT_EXECUTED" status. After thorough analysis, we identified that this problem is isolated to Android devices running Chrome version 137 and above, following a recent update pushed by Google. Users on affected devices may experience performance issues, including lag or transaction timeouts, particularly when capturing Selfie/liveness images. Our engineering team has pinpointed the root cause and is actively working on a resolution. The services degradation would have started with the deployment of the new version of Chrome, which we noticed started from: 2025-06-16 07:30 UTC. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding as we work to restore full service functionality. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

2. monitoring Jun 17, 2025, 06:47 PM UTC

   We have implemented the fix and we are monitoring the results.

3. monitoring Jun 17, 2025, 09:34 PM UTC

   We wanted to inform that we have validate with our Engineering support team the successful fix deployment, which included an enhancement within the camera capture logic. This have shown positive results within the conversion rate of Identity | Authentication user traffic. We will continue to actively monitor the current incident and will share a new update once the incident is fully resolved.

4. monitoring Jun 20, 2025, 11:34 AM UTC

   Status Update – June 20 We’re pleased to share a positive update regarding the recent drop in conversion rates. Background: Following the release of the latest Chrome update on June 16, we observed a 30% drop in overall conversion rates. After releasing an initial fix on June 17, we were able to recover half of that lost conversion, improving performance by approximately 15%. Current Status: On June 19, a final fix was deployed for Web Client implementations, which has fully restored conversion rates to expected levels. Next Steps for WebSDK Users: Please note that the issue remains for customers using our WebSDK. A new version of the WebSDK containing the fix is being finalized and is scheduled for release later today. Once available, integration of the updated SDK will be required to resolve the issue. We will update this status page once the new WebSDK version is published. Helpful Link: NPM Package: https://www.npmjs.com/package/@jumio/websdk?activeTab=readme Thank you for your patience and continued partnership.

5. resolved Jun 20, 2025, 05:09 PM UTC

   We are pleased to inform you that the recent drop in conversion rates has been successfully resolved. Update for WebSDK Users: A new version of the WebSDK has been released. Please update to the latest version to benefit of the recent enhancements. package @jumio/websdk (0.3.0): https://www.npmjs.com/package/@jumio/websdk?activeTab=readme We appreciate your patience and cooperation as the teams worked to identify and resolve the issue. If you continue to experience any problems, please reach out to Jumio Support at https://support.jumio.com.

Read the full incident report →

Started Jun 03, 2025, 01:31 AM UTC· resolved Jun 03, 2025, 02:05 AM UTC

1. monitoring Jun 03, 2025, 01:31 AM UTC

   We are currently experiencing a delay in processing on US, EU and SGP data centers for ID Verification transactions. NOTE: All services remain functional at this time, and we will send you another notification when the service is fully restored.

2. investigating Jun 03, 2025, 02:05 AM UTC

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

3. resolved Jun 03, 2025, 02:05 AM UTC

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

Read the full incident report →

Started May 13, 2025, 03:42 PM UTC· resolved May 13, 2025, 07:00 PM UTC

1. resolved May 13, 2025, 03:42 PM UTC

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

Read the full incident report →

Started Mar 24, 2025, 11:11 AM UTC· resolved Mar 24, 2025, 05:22 PM UTC

1. monitoring Mar 24, 2025, 11:11 AM UTC

   We are currently experiencing a delay in processing Identity Verification transactions on our EU data centers, which began approximately at 09:46 UTC. Please note: All other services are fully functional at this time. We will notify you as soon as the issue is fully resolved. We apologize for any inconvenience this may cause and appreciate your understanding.

2. resolved Mar 24, 2025, 05:22 PM 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.

Read the full incident report →

Started Jan 15, 2025, 04:01 AM UTC· resolved Jan 15, 2025, 07:43 AM UTC

1. investigating Jan 15, 2025, 04:01 AM UTC

   We are currently experiencing a delay in processing on EU data centers for Identity Verification transactions. At 2:25 UTC on 2025-01-15, we discovered an instability in our EU DC which leads -Increased processing delay for transactions on all data centers -Increased error rate and potential degradation in quality If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected]. Please know our engineering and operations teams are working hard to get everything up and running. NOTE: All services remain functional at this time, and we will send you another notification when the service is fully restored. Apologies for the inconvenience.

2. investigating Jan 15, 2025, 04:02 AM UTC

   We are continuing to investigate this issue.

3. monitoring Jan 15, 2025, 04:25 AM UTC

   Our first priority is to restore your services to full capacity and ensure that your end users have a better identity verification experience. We apologize for the disruption and the inconvenience we are causing. We have identified the root cause of the problem and have taken steps to resolve the issue and taking measures to prevent a recurrence. All new incoming transactions are being processed at a normal rate, but we are still working through the remaining backlog which might still have some delay and will provide more information as it becomes available. At 2:25 UTC on 2025-01-15, we discovered an instability in our EU DC which leads -Increased processing delay for transactions on all data centers -Increased error rate and potential degradation in quality At 3:32 UTC on 2025-01-15, solution has been implemented and we are monitoring the status If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

4. resolved Jan 15, 2025, 07:43 AM 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.

Read the full incident report →

Started Jan 08, 2025, 12:45 PM UTC· resolved Jan 08, 2025, 04:02 PM UTC

1. identified Jan 08, 2025, 01:54 PM UTC

   We’re really sorry to be holding you up today! Please know our engineering and operations teams are working hard to get everything up and running. We have identified an instability with all our services in the E.U. We know this is customer impacting so we are working on it urgently. The EU services were unavailable from: 2025-01-08 12:45 UTC Description: At 12:45 UTC on 2025-01-08, we discovered an instability in our EU DC. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

2. identified Jan 08, 2025, 02:02 PM UTC

   We’re really sorry to be holding you up today! Please know our engineering and operations teams are working hard to get everything up and running. We have identified an instability with all our services in the E.U. We know this is customer impacting so we are working on it urgently. The EU services were unavailable from: 2025-01-08 12:45 UTC Description: At 12:45 UTC on 2025-01-08, we discovered an instability in our EU DC. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

3. monitoring Jan 08, 2025, 02:24 PM UTC

   We are pleased to inform you that our services are now restored. We are actively monitoring the service status to make sure everything is working as expected. We appreciate your patience. For details of the service instability, please read below: At 12:45 UTC on 2025-01-08, we discovered unexpected issues with all of our Identity Verification Web and SDK services in the EU datacenter. As of 14:08 UTC on 2025-01-08, the service has been restored to proper functionality and is fully available. If you have any questions, please contact Jumio Support at https://support.jumio.com.

4. resolved Jan 08, 2025, 04:02 PM UTC

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

Read the full incident report →

Started Jan 04, 2025, 12:01 PM UTC· resolved Jan 04, 2025, 12:11 PM UTC

1. resolved Jan 04, 2025, 05:25 PM UTC

   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.

Read the full incident report →

Started Jan 01, 2025, 01:24 PM UTC· resolved Jan 01, 2025, 08:31 PM UTC

1. identified Jan 01, 2025, 01:24 PM UTC

   We’re really sorry to be holding you up today! Please know our engineering and operations teams are working hard to get everything up and running. We have identified an instability with all our services in the U.S. We know this is customer impacting so we are working on it urgently. The US services were unavailable from: 2025-01-01 12:40 UTC Description: At 12:40 UTC on 2025-01-01, we discovered an instability in our US DC. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

2. monitoring Jan 01, 2025, 01:51 PM UTC

   After careful monitoring, we are pleased to inform you that the recent instability in our US 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 12:40 UTC on 2025-01-01, we discovered an issue with all of our services services on the US datacenter. At 13:35 UTC on 2025-01-01, the services have been restored to proper functionality and should be available, but we have them all under monitoring. If you have any questions, please contact Jumio Support at https://support.jumio.com or [email protected].

3. monitoring Jan 01, 2025, 06:15 PM UTC

   We have observed a small number of transactions displaying 504 timeout errors starting approximately 5:55pm UTC. We sincerely apologize for any inconvenience caused. Our engineering team is diligently working to resolve the matter.

4. resolved Jan 01, 2025, 08:31 PM UTC

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

Read the full incident report →