Veriff 장애 기록

1. 2026년 9월 3일 PM 10:18 UTCinvestigating

   우리는 현재 Verification Decisions와 잠재적인 degraded 성과를 투자하고 있습니다. 우리의 팀은 지연 된 결정에 기여하는 문제의 뿌리 원인을 식별하고 곧 업데이트 제공 할 것입니다.

2. 2026년 9월 3일 PM 10:30 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 9월 3일 PM 10:34 UTCidentified

   문제는 우리의 제 3 자 제공 업체 중 하나로 확인되었습니다. 자동 검증 결정 시간에 우리의 미국 지구.

4. 2026년 9월 3일 PM 10:36 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

5. 2026년 9월 3일 PM 11:02 UTCmonitoring

   우리는 더 많은 문제를 모니터링하고 있습니다.

6. 2026년 9월 4일 AM 6:20 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 31일 PM 8:46 UTCidentified

   우리는 현재 Verification Decisions와 잠재적인 degraded 성과를 투자하고 있습니다. 우리의 팀은 지연 된 결정에 기여하는 문제의 뿌리 원인을 식별하고 곧 업데이트 제공 할 것입니다.

2. 2026년 8월 31일 PM 9:18 UTCidentified

   Verification Decisions에 영향을 미치는 성능은 미국 지역의 검증의 작은 하위 집합에 투자하고 있습니다. 우리의 팀은 기여 문제를 확인하고 건강한 환경에 새로운 트래픽을 리디렉션했습니다. 미국 지역의 인-발견 검증의 제한 수는 지연 된 결정을 경험할 수 있습니다. 우리는 곧 업데이트를 제공 할 것입니다.

3. 2026년 8월 31일 PM 9:55 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 8월 31일 PM 10:08 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 26일 PM 4:46 UTCresolved

   약 16 : 18 및 16 : 40 UTC에서 26 8 월 2026, 최종 사용자의 하위 세트는 검증 흐름을 완료하면서 간헐적 오류 또는 느리게 발생할 수 있습니다. 우리의 팀은 문제점을 확인하고, 서비스 회복 후에 고침을 적용했습니다. 검증 흐름은 현재 작동 중입니다. 우리는 모니터를 계속하고 반복을 방지하기 위해 조사합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 6일 PM 6:00 UTCinvestigating

   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.

2. 2026년 8월 6일 PM 6:09 UTCidentified

   We have identified an issue affecting one of our third-party providers and are working closely with them to resolve it as quickly as possible. Because the issue is intermittent, some sessions may experience higher-than-normal decision latency, while others may not be affected. We will continue to provide updates as more information becomes available.

3. 2026년 8월 6일 PM 7:24 UTCmonitoring

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

4. 2026년 8월 6일 PM 7:33 UTCresolved

   This incident has been resolved.

1. 2026년 7월 28일 PM 2:00 UTCinvestigating

   자동화된 세션을 발생시키는 문제들을 적극적으로 모니터링하고 있습니다. 이 문제는 모든 세션에 영향을 미치지 않습니다, 그래서 당신은 또는 영향을받지 않을 수 있습니다. 우리의 팀은 현재 뿌리 원인을 조사하고 있습니다. 우리는 영향을받는 구성 요소를 확인하고 공유하는 더 많은 정보가 있습니다.

2. 2026년 7월 28일 PM 2:25 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 7월 28일 PM 2:25 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

4. 2026년 7월 28일 PM 2:27 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

5. 2026년 7월 28일 PM 2:38 UTCresolved

   우리는 높은 결정 시간을 초래하는 데 실패 구성 요소 배포를 압연했습니다. 모니터링 기간에 따라 모든 시스템은 정상 작동으로 돌아 왔습니다. 우리는이 발생 할 수있는 불편에 대해 사과합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 24일 PM 12:15 UTCinvestigating

   우리는 현재 Verification Decisions와 잠재적인 degraded 성과를 투자하고 있습니다. 우리의 팀은 지연 된 결정에 기여하는 문제의 뿌리 원인을 식별하고 곧 업데이트 제공 할 것입니다.

2. 2026년 7월 24일 PM 4:46 UTCidentified

   우리는 우리의 제 3 자 제공 업체 중 하나에 영향을 미치는 문제를 확인하고 가능한 한 빨리 해결하기 위해 그들과 긴밀히 협력하고있다. 문제는 간헐적이기 때문에, 일부 세션은 더 높은 정상적인 결정 지연을 경험할 수 있습니다, 다른 사람들이 영향을 미치지 않을 수 있습니다. 더 많은 정보로 업데이트를 계속 제공 할 것입니다.

3. 2026년 7월 24일 PM 8:34 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 7월 25일 AM 11:59 UTCresolved

   성공적인 감시의 기간 후에, 우리는 문제점이 완전히 해결된다는 것을 확인했습니다. 체계 미터는 정상적인에 돌려보내지고 모든 서비스는 조작상입니다. 감사합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 21일 AM 11:37 UTCresolved

   2026-07-20 14:50 UTC 및 2026-07-20 16:30 UTC 사이, 시계 목록 검열 (PEP 및 Sanctions) webhooks의 배달에 대한 제 3 자 제공 업체의 사건. 이 기간 동안 Watchlist Screening 결과를 생성 할 수 없으며 해당 웹훅 알림은 영향을받는 세션의 작은 하위 세트에 전달되지 않았습니다. 이 사건은 제 3 자 제공자에게 독점적으로 고립되었습니다. Veriff의 핵심 정체성 검증 및 결정적인 기능은 영향을 미치지 않았습니다. 제3자 서비스는 정상적인 가동에 돌려보내고 시계 목록 검열 webhook 납품은 재시작했습니다. 활동은 Watchlist Screening (PEP & Sanctions) 검사를 위해 재처리될 수 있습니다, 그 결과가 webhook, Public API 및 Veriff Hub/ Station을 통해 사용할 수 있습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 7일 PM 9:06 UTCinvestigating

   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.

2. 2026년 7월 7일 PM 9:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 7월 7일 PM 9:32 UTCmonitoring

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

4. 2026년 7월 7일 PM 11:43 UTCresolved

   This incident has been resolved.

1. 2026년 7월 6일 PM 8:39 UTCidentified

   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.

2. 2026년 7월 9일 AM 9:29 UTCidentified

   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.

3. 2026년 7월 9일 PM 1:09 UTCidentified

   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.

4. 2026년 7월 10일 PM 12:43 UTCresolved

   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.

1. 2026년 7월 6일 PM 3:15 UTCidentified

   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.

2. 2026년 7월 6일 PM 7:31 UTCresolved

   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.

1. 2026년 6월 30일 PM 4:32 UTCinvestigating

   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.

2. 2026년 6월 30일 PM 4:57 UTCmonitoring

   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.

3. 2026년 6월 30일 PM 5:21 UTCresolved

   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.

1. 2026년 6월 30일 PM 3:22 UTCinvestigating

   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.

2. 2026년 6월 30일 PM 3:33 UTCidentified

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

3. 2026년 6월 30일 PM 3:40 UTCresolved

   This incident has been resolved.

1. 2026년 6월 18일 PM 2:39 UTCinvestigating

   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.

2. 2026년 6월 18일 PM 3:03 UTCidentified

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

3. 2026년 6월 18일 PM 3:56 UTCmonitoring

   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.

4. 2026년 6월 18일 PM 6:59 UTCresolved

   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.

1. 2026년 6월 17일 PM 3:26 UTCmonitoring

   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.

2. 2026년 6월 17일 PM 4:15 UTCresolved

   This incident has been resolved.

1. 2026년 6월 12일 AM 2:06 UTCinvestigating

   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.

2. 2026년 6월 12일 AM 2:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 6월 12일 AM 2:43 UTCidentified

   The issue has been identified.

4. 2026년 6월 12일 AM 3:11 UTCmonitoring

   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.

5. 2026년 6월 12일 AM 5:45 UTCmonitoring

   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.

6. 2026년 6월 12일 AM 10:19 UTCresolved

   This incident has been resolved.

1. 2026년 6월 11일 PM 5:38 UTCresolved

   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.

1. 2026년 6월 8일 PM 5:23 UTCresolved

   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.

1. 2026년 5월 27일 PM 2:51 UTCresolved

   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.

1. 2026년 5월 19일 AM 7:45 UTCmonitoring

   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

2. 2026년 5월 20일 AM 6:34 UTCresolved

   This incident has been resolved.

1. 2026년 4월 24일 PM 2:18 UTCinvestigating

   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.

2. 2026년 4월 24일 PM 2:32 UTCidentified

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

3. 2026년 4월 24일 PM 3:30 UTCmonitoring

   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.

4. 2026년 4월 24일 PM 3:34 UTCresolved

   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.