Historial de interrupciones de Veriff

1. September 3, 2026 at 10:18 PM UTCinvestigating

   Actualmente estamos investigando posibles resultados degradados con Decisiones de Verificación. Nuestro equipo está trabajando en la identificación de la causa raíz de la cuestión que contribuye a las decisiones demoradas y proporcionará una actualización en breve.

2. September 3, 2026 at 10:30 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. September 3, 2026 at 10:34 PM UTCidentified

   Se ha identificado un problema con uno de nuestros proveedores de terceros causando un aumento de los tiempos de decisión de verificación automática en nuestras regiones estadounidenses.

4. September 3, 2026 at 10:36 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

5. September 3, 2026 at 11:02 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

6. September 4, 2026 at 6:20 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 31, 2026 at 8:46 PM UTCidentified

   Actualmente estamos investigando posibles resultados degradados con Decisiones de Verificación. Nuestro equipo está trabajando en la identificación de la causa raíz de la cuestión que contribuye a las decisiones demoradas y proporcionará una actualización en breve.

2. August 31, 2026 at 9:18 PM UTCidentified

   Estamos investigando el desempeño degradado que afecta las decisiones de verificación para un pequeño subconjunto de verificaciones en la región de Estados Unidos. Nuestro equipo ha identificado el problema que contribuye y redirigido el nuevo tráfico a un ambiente saludable. Un número limitado de verificaciones en el proceso en la región de Estados Unidos puede experimentar decisiones demoradas. Vamos a proporcionar una actualización en breve.

3. August 31, 2026 at 9:55 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. August 31, 2026 at 10:08 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 26, 2026 at 4:46 PM UTCresolved

   Entre aproximadamente 16:18 y 16:40 UTC el 26 de agosto de 2026, un subconjunto de usuarios finales puede haber encontrado errores intermitentes o lentitud al completar el flujo de verificación. Nuestro equipo identificó el problema y aplicó una solución, después de la cual el servicio se recuperó. El flujo de verificación está funcionando normalmente. Seguimos monitoreando e investigando para evitar la recurrencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 6, 2026 at 6:00 PM 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. August 6, 2026 at 6:09 PM 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. August 6, 2026 at 7:24 PM UTCmonitoring

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

4. August 6, 2026 at 7:33 PM UTCresolved

   This incident has been resolved.

1. July 28, 2026 at 2:00 PM UTCinvestigating

   Estamos monitoreando activamente una cuestión que está provocando que algunas sesiones automatizadas experimenten mayores tiempos de decisión de lo habitual. Este tema no está afectando todas las sesiones, por lo que puede o no ser impactado. Nuestro equipo está investigando la causa raíz. Proporcionaremos otra actualización tan pronto como identifiquemos el componente afectado y tengamos más información que compartir.

2. July 28, 2026 at 2:25 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 28, 2026 at 2:25 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

4. July 28, 2026 at 2:27 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

5. July 28, 2026 at 2:38 PM UTCresolved

   Hemos retrocedido un despliegue de componentes que estaba causando tiempos elevados de decisión. Tras un período de vigilancia, todos los sistemas han regresado a una operación normal. Nos disculpamos por cualquier inconveniente que esto pueda haber causado.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 12:15 PM UTCinvestigating

   Actualmente estamos investigando posibles resultados degradados con Decisiones de Verificación. Nuestro equipo está trabajando en la identificación de la causa raíz de la cuestión que contribuye a las decisiones demoradas y proporcionará una actualización en breve.

2. July 24, 2026 at 4:46 PM UTCidentified

   Hemos identificado un problema que afecta a uno de nuestros proveedores de terceros y estamos trabajando estrechamente con ellos para resolverlo lo antes posible. Debido a que el tema es intermitente, algunas sesiones pueden experimentar un retraso de decisión más alto que normal, mientras que otras pueden no verse afectadas. Seguiremos proporcionando actualizaciones a medida que se disponga de más información.

3. July 24, 2026 at 8:34 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. July 25, 2026 at 11:59 AM UTCresolved

   Tras un período de seguimiento exitoso, hemos confirmado que la cuestión está plenamente resuelta. Las métricas del sistema han regresado a la normalidad y todos los servicios están operativos. Gracias por su paciencia con nosotros.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 21, 2026 at 11:37 AM UTCresolved

   Entre 2026-07-20 14:50 UTC y 2026-07-20 16:30 UTC, un incidente en un proveedor de terceros causó un rendimiento degradado para la entrega de Screening Watchlist (PEP y Sanciones) webhooks. Durante este período, no se pudieron generar resultados de Screening Watchlist, y las correspondientes notificaciones de Webhook no se entregaron para un pequeño subconjunto de sesiones afectadas. Este incidente fue aislado exclusivamente al proveedor de terceros; las capacidades básicas de verificación de identidad y toma de decisiones de Veriff no fueron impactadas. El servicio de terceros ha regresado a la operación normal y la entrega de Webhook Screening Watchlist se ha reanudado. Se pueden reprocesar las sesiones afectadas para el control de la lista de vigilancia (PEP " Sanciones) después de los resultados estarán disponibles a través de webhook, la API pública y el Hub/ Station de Veriff.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 7, 2026 at 9:06 PM 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. July 7, 2026 at 9:07 PM UTCinvestigating

   We are continuing to investigate this issue.

3. July 7, 2026 at 9:32 PM UTCmonitoring

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

4. July 7, 2026 at 11:43 PM UTCresolved

   This incident has been resolved.

1. July 6, 2026 at 8:39 PM 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. July 9, 2026 at 9:29 AM 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. July 9, 2026 at 1:09 PM 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. July 10, 2026 at 12:43 PM 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. July 6, 2026 at 3:15 PM 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. July 6, 2026 at 7:31 PM 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. June 30, 2026 at 4:32 PM 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. June 30, 2026 at 4:57 PM 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. June 30, 2026 at 5:21 PM 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. June 30, 2026 at 3:22 PM 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. June 30, 2026 at 3:33 PM UTCidentified

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

3. June 30, 2026 at 3:40 PM UTCresolved

   This incident has been resolved.

1. June 18, 2026 at 2:39 PM 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. June 18, 2026 at 3:03 PM UTCidentified

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

3. June 18, 2026 at 3:56 PM 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. June 18, 2026 at 6:59 PM 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. June 17, 2026 at 3:26 PM 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. June 17, 2026 at 4:15 PM UTCresolved

   This incident has been resolved.

1. June 12, 2026 at 2:06 AM 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. June 12, 2026 at 2:25 AM UTCinvestigating

   We are continuing to investigate this issue.

3. June 12, 2026 at 2:43 AM UTCidentified

   The issue has been identified.

4. June 12, 2026 at 3:11 AM 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. June 12, 2026 at 5:45 AM 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. June 12, 2026 at 10:19 AM UTCresolved

   This incident has been resolved.

1. June 11, 2026 at 5:38 PM 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. June 8, 2026 at 5:23 PM 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. May 27, 2026 at 2:51 PM 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. May 19, 2026 at 7:45 AM 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. May 20, 2026 at 6:34 AM UTCresolved

   This incident has been resolved.

1. April 24, 2026 at 2:18 PM 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. April 24, 2026 at 2:32 PM UTCidentified

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

3. April 24, 2026 at 3:30 PM 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. April 24, 2026 at 3:34 PM 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.