Historial de interrupciones de Idnow

1. 16 de agosto de 2026 a las 18:47 UTCinvestigating

   Actualmente estamos experimentando una degradación del rendimiento y estamos investigando activamente la cuestión. Nuestro equipo está trabajando para identificar la causa raíz e implementar una solución. Los clientes que usan eSign con IDnow QTSP se ven afectados.

2. 16 de agosto de 2026 a las 19:59 UTCmonitoring

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

3. 16 de agosto de 2026 a las 20:10 UTCresolved

   Este incidente ha sido resuelto.

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

1. 9 de agosto de 2026 a las 1:16 UTCidentified

   Actualmente estamos experimentando una interrupción del servicio en nuestro servicio avanzado de firmas Nuestros equipos de ingeniería están investigando activamente la cuestión y trabajando para restaurar la plena funcionalidad lo antes posible. Apreciamos su paciencia y proporcionaremos actualizaciones oportunas hasta que el servicio esté completamente restaurado.

2. 9 de agosto de 2026 a las 1:57 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

3. 10 de agosto de 2026 a las 7:59 UTCidentified

   The team is fixing the issue, the service should be restored within the next hour.

4. 10 de agosto de 2026 a las 9:08 UTCmonitoring

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

5. 10 de agosto de 2026 a las 10:10 UTCresolved

   This incident has been resolved.

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

1. 27 de julio de 2026 a las 9:17 UTCinvestigating

   *.identity.tm domains (including dedicated status page) are not resolved by the DNS, resulting in lack of access to the systems.

2. 27 de julio de 2026 a las 9:34 UTCmonitoring

   La resolución del DNS parece estar funcionando de nuevo. Estamos reuniendo pruebas para la investigación.

3. 27 de julio de 2026 a las 9:46 UTCresolved

   Este incidente ha sido resuelto.

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

1. 21 de julio de 2026 a las 9:31 UTCinvestigating

   Actualmente estamos experimentando una interrupción del servicio para el robot de prueba. Mientras se ejecuta el robot de prueba con el escenario HAPPYPATH, si hay una inconsistencia de datos entre los datos iniciales y los datos presentados posteriormente al TestRobot con HAPPYPATH, el resultado de la carrera será SUCCESS DATA CHANGED (como en el escenario CHANGEALL). En efecto, esto significa que -HAPPYPATH no es capaz de producir un resultado SUCCESS si el comando robot está escrito al primer o último nombre. Otros escenarios de robot funcionan correctamente. Esto sólo afecta al robot de VideoIdent y ESign TEST. Los productos AutoIdent y InstantSign no están afectados. La producción no se ve afectada.

2. 5 de agosto de 2026 a las 12:42 UTCmonitoring

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

3. 18 de agosto de 2026 a las 13:55 UTCresolved

   Este incidente ha sido resuelto.

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

1. 20 de julio de 2026 a las 14:25 UTCinvestigating

   Actualmente estamos experimentando una interrupción del servicio. Nuestros equipos de ingeniería están investigando activamente la cuestión y trabajando para restaurar la plena funcionalidad lo antes posible. Apreciamos su paciencia y proporcionaremos actualizaciones oportunas hasta que el servicio esté completamente restaurado.

2. 20 de julio de 2026 a las 15:12 UTCresolved

   Este incidente ha sido resuelto.

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

1. 2 de julio de 2026 a las 10:06 UTCmonitoring

   Identificamos un problema técnico en nuestra interfaz de agente de VideoIdent que causa un impacto de rendimiento. El problema llevó a una menor disponibilidad de agentes de vídeo para usuarios finales en nuestros servicios de VideoIdent y eSign. Se desplegó una solución y estamos monitoreando la situación. AutoIdent, AutoIdent QES, eID y InstantSign no fueron afectados.

2. 3 de julio de 2026 a las 12:12 UTCresolved

   Este incidente ha sido resuelto.

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

1. 10 de junio de 2026 a las 7:24 UTCinvestigating

   We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.

2. 10 de junio de 2026 a las 7:35 UTCmonitoring

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

3. 10 de junio de 2026 a las 7:42 UTCresolved

   This incident has been resolved.

1. 9 de junio de 2026 a las 14:07 UTCinvestigating

   We are currently experiencing a performance degradation and are actively investigating the issue. Our team is working to identify the root cause and implement a solution. Customers using eSign with IDnow QTSP are affected.

2. 10 de junio de 2026 a las 7:38 UTCresolved

   This incident has been resolved.

1. 5 de mayo de 2026 a las 9:32 UTCinvestigating

   We are currently experiencing a service disruption on PVID. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.

2. 5 de mayo de 2026 a las 9:43 UTCmonitoring

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

3. 5 de mayo de 2026 a las 10:00 UTCresolved

   This incident has been resolved.

1. 28 de abril de 2026 a las 7:44 UTCinvestigating

   We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.

2. 28 de abril de 2026 a las 8:08 UTCmonitoring

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

3. 28 de abril de 2026 a las 8:08 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28 de abril de 2026 a las 8:40 UTCresolved

   This incident has been resolved.

1. 21 de abril de 2026 a las 15:59 UTCinvestigating

   We are currently experiencing a service disruption. Our DevOps team is working to identify the root cause and implement a solution. eSigning users who use the Namirial TSP are affected. We will keep you updated with any new developments.

2. 21 de abril de 2026 a las 17:48 UTCresolved

   This incident has been resolved.

1. 3 de abril de 2026 a las 7:29 UTCinvestigating

   We are currently experiencing a service disruption on Check'n'Sign service. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.

2. 3 de abril de 2026 a las 7:44 UTCidentified

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

3. 3 de abril de 2026 a las 7:50 UTCmonitoring

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

4. 3 de abril de 2026 a las 7:52 UTCresolved

   This incident has been resolved.

1. 25 de marzo de 2026 a las 15:27 UTCinvestigating

   We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.

2. 25 de marzo de 2026 a las 15:39 UTCidentified

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

3. 25 de marzo de 2026 a las 15:46 UTCmonitoring

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

4. 25 de marzo de 2026 a las 15:57 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 de marzo de 2026 a las 16:01 UTCresolved

   This incident has been resolved.

1. 18 de marzo de 2026 a las 12:52 UTCinvestigating

   For the last couple of hours, we're experiencing a performance degradation and are currently looking into the issue We will provide regular updates on the issue.

2. 18 de marzo de 2026 a las 12:58 UTCidentified

   A 3rd party provider API is experiencing an outage, impacting the performance of Check'n'Sign. We are considering options to workaround the issue.

3. 18 de marzo de 2026 a las 13:41 UTCidentified

   A fix is being implemented.

4. 18 de marzo de 2026 a las 13:53 UTCmonitoring

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

5. 18 de marzo de 2026 a las 15:44 UTCmonitoring

   The 3rd party provider API is up and running again so we are removing the workaround.

6. 18 de marzo de 2026 a las 16:25 UTCresolved

   This incident has been resolved.

1. 13 de marzo de 2026 a las 14:47 UTCinvestigating

   We're experiencing an performance degradation and are currently looking into the issue. We will provide regular updates on the issue.

2. 13 de marzo de 2026 a las 15:15 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 de marzo de 2026 a las 15:35 UTCidentified

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

4. 13 de marzo de 2026 a las 16:44 UTCidentified

   The team identified the root cause. We are investigating it further to restore the services as soon as possible.

5. 13 de marzo de 2026 a las 17:35 UTCidentified

   We are still working on restoring the service. It may take another couple of hours.

6. 13 de marzo de 2026 a las 17:47 UTCmonitoring

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

7. 13 de marzo de 2026 a las 18:04 UTCresolved

   This incident has been resolved.

1. 2 de febrero de 2026 a las 15:08 UTCinvestigating

   We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.

2. 2 de febrero de 2026 a las 15:40 UTCidentified

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

3. 2 de febrero de 2026 a las 15:42 UTCmonitoring

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

4. 2 de febrero de 2026 a las 16:24 UTCresolved

   This incident has been resolved.

1. 29 de enero de 2026 a las 15:13 UTCinvestigating

   We are currently experiencing a service disruption. Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.

2. 29 de enero de 2026 a las 15:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 de enero de 2026 a las 15:58 UTCmonitoring

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

4. 29 de enero de 2026 a las 15:59 UTCresolved

   This incident has been resolved.

1. 29 de enero de 2026 a las 7:26 UTCinvestigating

   We are currently experiencing a service disruption. Our DevOps team is working to identify the root cause and implement a solution. We will send an additional update in 60 minutes.

2. 29 de enero de 2026 a las 7:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 de enero de 2026 a las 8:12 UTCidentified

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

4. 29 de enero de 2026 a las 8:29 UTCidentified

   The services are gradually getting back online.

5. 29 de enero de 2026 a las 8:31 UTCidentified

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

6. 29 de enero de 2026 a las 9:26 UTCmonitoring

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

7. 29 de enero de 2026 a las 9:47 UTCresolved

   This incident has been resolved.

1. 11 de enero de 2026 a las 10:04 UTCinvestigating

   We are currently experiencing a service disruption. Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.

2. 11 de enero de 2026 a las 10:39 UTCidentified

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

3. 11 de enero de 2026 a las 11:11 UTCmonitoring

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

4. 11 de enero de 2026 a las 18:16 UTCresolved

   This incident has been resolved.

1. 5 de enero de 2026 a las 11:15 UTCinvestigating

   We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.

2. 5 de enero de 2026 a las 11:28 UTCidentified

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

3. 5 de enero de 2026 a las 11:46 UTCmonitoring

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

4. 5 de enero de 2026 a las 13:06 UTCresolved

   This incident has been resolved.