Veriff の障害履歴

We are currently investigating potential degraded performance with Verification Decisions. Our team is working on identifying root cause of the issue that is contributing to delayed decisions and will provide an update shortly.

We are continuing to investigate this issue.

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

This incident has been resolved.

We have identified an issue affecting one of our internal components, which is impacting verification decision times. As a result, some verification requests may take longer than usual to receive a decision. Our team is actively working to resolve the issue as quickly as possible and minimize the impact. We apologize for the inconvenience and appreciate your patience.

We are experiencing an issue with a component of our OCR (text extraction) service that supports Verification Decisions. This can delay how quickly a decision is returned and, in a small number of cases, affect the outcome. WHO IS AFFECTED - Customers processing verifications in our US region only. Other regions are unaffected. - Impact is intermittent (occurring in waves over the past ~2 days), not a continuous outage. WHAT YOU MAY SEE - Slower decisions (most common): verifications take longer than usual to return, but the decision itself is correct. - Incorrect resubmissions: a small proportion of legitimate verifications may be incorrectly returned for resubmission. An unusual spike in resubmissions may be caused by this. - Lower-confidence decisions: some decisions may be reached with incomplete text-extraction data. WHAT WE ARE DOING - The affected component is partially dependent on a third-party service that is currently experiencing an outage. We are working with the provider on a fix. - We have deployed changes to make the service more resilient and reduce the impact in the meantime. NEXT UPDATE - We will post our next update by 11:00 UTC Thursday, July 9th.

We are experiencing an issue with a component of our OCR (text extraction) service that supports Verification Decisions. This can delay how quickly a decision is returned and, in a small number of cases, affect the outcome. WHO IS AFFECTED - Customers processing verifications in our US region only. Other regions are unaffected. - Impact is intermittent (occurring in waves over the past ~2 days), not a continuous outage. WHAT YOU MAY SEE - Slower decisions (most common): verifications take longer than usual to return, but the decision itself is correct. - Incorrect resubmissions: a small proportion of legitimate verifications may be incorrectly returned for resubmission. An unusual spike in resubmissions may be caused by this. - Lower-confidence decisions: some decisions may be reached with incomplete text-extraction data. WHAT WE ARE DOING - We have deployed changes to make the service more resilient and reduce the impact in the meantime. - The affected component is partially dependent on a third-party service that is currently experiencing an outage. They stated that the fix would be deployed by Friday 10th of July. NEXT UPDATE - We will post our next update by 11:00 UTC Friday, July 10th.

Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

We have identified an issue affecting one of our internal components, which is impacting verification decision times. As a result, some verification requests may take longer than usual to receive a decision. Our team is actively working to resolve the issue as quickly as possible and minimize the impact. We apologize for the inconvenience and appreciate your patience.

Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

We have identified an issue that is preventing new Veriff accounts from being created. This issue does not affect existing customers or their ability to use the service; it only impacts the creation of new accounts. Our team is actively investigating the root cause and working to implement a fix. We will provide updates as more information becomes available.

The fix has been successfully deployed. While services have returned to operational, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

We have identified an issue affecting manual verifications that may cause delays in verification decisions. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We will provide updates as more information becomes available.

The root cause of the issue has been identified. Our team is prioritized on deploying a fix.

This incident has been resolved.

Thank you for your patience. We have identified the components with the issue. Our team is actively investigating the root cause, and we will share a status update shortly.

The issue has been identified and a fix is being implemented.

We identified an issue affecting the search service in Veriff Station that caused some search requests to fail and return errors. The issue has been resolved, and a fix has been deployed. We are actively monitoring the service to ensure continued stability and performance.

Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

We have identified an issue affecting one of our services, resulting in longer-than-expected decision times for verifications. A fix has already been deployed; however, some related effects are still being mitigated as the changes continue to propagate through the system. Our team is actively monitoring the situation and will provide further updates as they become available.

This incident has been resolved.

We are currently investigating potential degraded performance with Verification Decisions. Our team is working on identifying root cause of the issue that is contributing to delayed decisions and will provide an update shortly.

We are continuing to investigate this issue.

The issue has been identified.

The issue has been traced back to an upstream infrastructure outage affecting our platform. We are working closely with the provider to monitor the resolution and restore full functionality.

The fix has been successfully deployed. While services are returning to operational level, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

This incident has been resolved.

Between 2026-06-11 11:10 and 2026-06-11 14:50, Auto Decision Time experienced degraded performance. The issue was identified and resolved by our team before this notification was published. System metrics have returned to normal and all services are operational.

Between 2026-06-08 16:15 and 2026-06-08 17:00 UTC, our API and Webhook services experienced degraded performance. The issue was identified and resolved by our team before this notification was published. System metrics have returned to normal and all services are operational.

Between 14:01:00 UTC and 14:15:00 UTC, the decision times experienced degraded performance. The issue was identified and resolved by our team before this notification was published. System metrics have returned to normal and all services are operational.

Hello! We wanted to to inform you that our session expiry is currently experiencing issues, which prevents sessions from getting expired/abandoned once the sessions is past it's validity date. Please also note that decision webhooks notifying about expired/abandoned sessions are also not being sent because of this issue at hand The root cause of the issue was already identified, further impact mitigated and we are waiting for the session backlog to clear out. We will keep you posted on new updates

This incident has been resolved.

We are currently investigating potential degraded performance with INE/ CURP 2.0 validation check. Our team is working on identifying root cause of the issue that is contributing to delayed decisions and will provide an update shortly.

The root cause of the issue has been identified. Our team is prioritized on deploying a fix.

The fix has been successfully deployed. While services have returned to operational, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

Thank you for your patience. We have identified the components with the issue. Our team is actively investigating the root cause, and we will share a status update shortly.

The root cause of the issue has been identified. Our team is prioritized on deploying a fix.

The fix has been successfully deployed. While services have returned to operational, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

We are currently investigating potential degraded performance with API. Our team is working on identifying root cause of the issue that is contributing to increased latency/ errors on requests to public API and will provide an update shortly.

The fix has been successfully deployed. While services have returned to operational, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

We have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

We are currently investigating a potential issue with our services. Our team is investigating to determine if everything is working as expected. We will provide an update on our findings as soon as possible.

Thank you for your patience. We have identified the components with the issue. Our team is actively investigating the root cause, and we will share a status update shortly.

We are continuing to investigate this issue.

The root cause of the issue has been identified. Our team is prioritized on deploying a fix.

The fix has been successfully deployed. While services have returned to operational, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

We are continuing to monitor for any further issues.

Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

We are currently investigating a potential issue with our services. Our team is investigating to determine if everything is working as expected. We will provide an update on our findings as soon as possible.

The issue has been identified and a fix is being implemented.

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

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

This incident has been resolved.

During 2026-04-16T17:04:34Z UTC - 2026-04-16T22:04:00Z UTC, POA service experienced degraded performance. The issue was identified and resolved by our team before this notification was published. System metrics have returned to normal and all services are operational.

Thank you for your patience. We have identified the components with the issue. Our team is actively investigating the root cause, and we will share a status update shortly.

We are continuing to investigate this issue.

The fix has been successfully deployed. While services have returned to operational, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

We are continuing to monitor for any further issues.

Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

Hello! We have identified ongoing issues with our AML Screening webhooks, for which updated screening results do not contain any information on the found matches; Our teams are investigating the root cause of the issue and will start working on a fix as soon as possible. Sorry for the inconvenience and we will keep you updated!

The issue has been identified and a fix is being implemented.

The fix is out! We’ve deployed a fix, but to be safe we’re keeping an eye on everything.

This incident has been resolved.