Histórico de interrupções do Veriff

1. 3 Gwengolo 2026 da 22:18 UTCinvestigating

   Estamos atualmente investigando o desempenho potencial degradado com decisões de verificação. Nossa equipe está trabalhando na identificação da causa básica do problema que está contribuindo para decisões atrasadas e irá fornecer uma atualização em breve.

2. 3 Gwengolo 2026 da 22:30 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 3 Gwengolo 2026 da 22:34 UTCidentified

   Um problema foi identificado com um de nossos provedores de terceiros causando um aumento nos tempos de auto verificação de decisão em nossas regiões dos EUA.

4. 3 Gwengolo 2026 da 22:36 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

5. 3 Gwengolo 2026 da 23:02 UTCmonitoring

   Continuamos monitorando quaisquer outros problemas.

6. 4 Gwengolo 2026 da 06:20 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 31 Eost 2026 da 20:46 UTCidentified

   Estamos atualmente investigando o desempenho potencial degradado com decisões de verificação. Nossa equipe está trabalhando na identificação da causa básica do problema que está contribuindo para decisões atrasadas e irá fornecer uma atualização em breve.

2. 31 Eost 2026 da 21:18 UTCidentified

   Estamos investigando desempenho degradado afetando decisões de verificação para um pequeno subconjunto de verificações na região dos EUA. Nossa equipe identificou o problema contribuinte e redirecionou o novo tráfego para um ambiente saudável. Um número limitado de verificações em curso na região dos EUA pode sofrer decisões tardias. Vamos fornecer uma atualização em breve.

3. 31 Eost 2026 da 21:55 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 31 Eost 2026 da 22:08 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Eost 2026 da 16:46 UTCresolved

   Entre aproximadamente 16:18 e 16:40 UTC em 26 de agosto de 2026, um subconjunto de usuários finais pode ter encontrado erros intermitentes ou lentidão ao completar o fluxo de verificação. Nossa equipe identificou o problema e aplicou uma correção, após a qual o serviço recuperou. O fluxo de verificação está agora funcionando normalmente. Continuamos a monitorizar e vamos investigar para prevenir a recorrência.

Traduzido automaticamente da atualização oficial do incidente.

1. 6 Eost 2026 da 18: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. 6 Eost 2026 da 18: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. 6 Eost 2026 da 19:24 UTCmonitoring

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

4. 6 Eost 2026 da 19:33 UTCresolved

   This incident has been resolved.

1. 28 Gouere 2026 da 14:00 UTCinvestigating

   Estamos monitorando ativamente um problema que está fazendo com que algumas sessões automatizadas experimentem tempos de decisão mais altos do que o habitual. Esta questão não está afetando todas as sessões, então você pode ou não ser impactado. A nossa equipa está a investigar a causa principal. Forneceremos outra atualização assim que identificarmos o componente afetado e tivermos mais informações para compartilhar.

2. 28 Gouere 2026 da 14:25 UTCinvestigating

   Continuamos a investigar esta questão.

3. 28 Gouere 2026 da 14:25 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

4. 28 Gouere 2026 da 14:27 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

5. 28 Gouere 2026 da 14:38 UTCresolved

   Rebocámos uma implantação de componentes que estava a causar tempos de decisão elevados. Após um período de monitorização, todos os sistemas voltaram à operação normal. Pedimos desculpa por qualquer inconveniente que isto possa ter causado.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gouere 2026 da 12:15 UTCinvestigating

   Estamos atualmente investigando o desempenho potencial degradado com decisões de verificação. Nossa equipe está trabalhando na identificação da causa básica do problema que está contribuindo para decisões atrasadas e irá fornecer uma atualização em breve.

2. 24 Gouere 2026 da 16:46 UTCidentified

   Identificámos um problema que afecta um dos nossos fornecedores de terceiros e estamos a trabalhar em estreita colaboração com eles para o resolver o mais rapidamente possível. Como a questão é intermitente, algumas sessões podem apresentar latência de decisão superior ao normal, enquanto outras podem não ser afetadas. Continuaremos a fornecer atualizações à medida que mais informações estiverem disponíveis.

3. 24 Gouere 2026 da 20:34 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 25 Gouere 2026 da 11:59 UTCresolved

   Após um período de acompanhamento bem sucedido, confirmámos que a questão está totalmente resolvida. As métricas do sistema voltaram ao normal e todos os serviços estão operacionais. Obrigado pela vossa paciência connosco.

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gouere 2026 da 11:37 UTCresolved

   Entre 2026-07-20 14:50 UTC e 2026-07-20 16:30 UTC, um incidente em um provedor de terceiros causou desempenho degradado para a entrega de webhooks Watchlist Screening (PEP e Sanções). Durante esse período, os resultados da Watchlist Screening não puderam ser gerados, e as notificações de webhook correspondentes não foram entregues para um pequeno subconjunto de sessões afetadas. Este incidente foi isolado exclusivamente para o fornecedor de terceiros; a verificação de identidade central da Veriff e as capacidades de tomada de decisão não foram impactadas. O serviço de terceiros voltou desde então à operação normal e Watchlist Screening entrega webhook retomou. Sessões afetadas podem ser reprocessadas para a verificação da Watchlist Screening (PEP & Sanctions), após o qual os resultados estarão disponíveis via webhook, a API Pública e Veriff Hub/ Station.

Traduzido automaticamente da atualização oficial do incidente.

1. 7 Gouere 2026 da 21: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. 7 Gouere 2026 da 21:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 Gouere 2026 da 21:32 UTCmonitoring

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

4. 7 Gouere 2026 da 23:43 UTCresolved

   This incident has been resolved.

1. 6 Gouere 2026 da 20: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. 9 Gouere 2026 da 09: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. 9 Gouere 2026 da 13: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. 10 Gouere 2026 da 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. 6 Gouere 2026 da 15: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. 6 Gouere 2026 da 19: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. 30 Mezheven 2026 da 16: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. 30 Mezheven 2026 da 16: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. 30 Mezheven 2026 da 17: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. 30 Mezheven 2026 da 15: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. 30 Mezheven 2026 da 15:33 UTCidentified

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

3. 30 Mezheven 2026 da 15:40 UTCresolved

   This incident has been resolved.

1. 18 Mezheven 2026 da 14: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. 18 Mezheven 2026 da 15:03 UTCidentified

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

3. 18 Mezheven 2026 da 15: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. 18 Mezheven 2026 da 18: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. 17 Mezheven 2026 da 15: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. 17 Mezheven 2026 da 16:15 UTCresolved

   This incident has been resolved.

1. 12 Mezheven 2026 da 02: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. 12 Mezheven 2026 da 02:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 12 Mezheven 2026 da 02:43 UTCidentified

   The issue has been identified.

4. 12 Mezheven 2026 da 03: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. 12 Mezheven 2026 da 05: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. 12 Mezheven 2026 da 10:19 UTCresolved

   This incident has been resolved.

1. 11 Mezheven 2026 da 17: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. 8 Mezheven 2026 da 17: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. 27 Mae 2026 da 14: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. 19 Mae 2026 da 07: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. 20 Mae 2026 da 06:34 UTCresolved

   This incident has been resolved.

1. 24 Ebrel 2026 da 14: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. 24 Ebrel 2026 da 14:32 UTCidentified

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

3. 24 Ebrel 2026 da 15: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. 24 Ebrel 2026 da 15: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.