Histórico de interrupções do Idnow

1. 16 Eost 2026 da 18:47 UTCinvestigating

   Atualmente estamos experimentando uma degradação de desempenho e estamos investigando ativamente a questão. Nossa equipe está trabalhando para identificar a causa raiz e implementar uma solução. Clientes usando eSign com IDnow QTSP são afetados.

2. 16 Eost 2026 da 19:59 UTCmonitoring

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

3. 16 Eost 2026 da 20:10 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Eost 2026 da 01:16 UTCidentified

   We are currently experiencing a service disruption on our advanced signature service 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. 9 Eost 2026 da 01:57 UTCidentified

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

3. 10 Eost 2026 da 07:59 UTCidentified

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

4. 10 Eost 2026 da 09:08 UTCmonitoring

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

5. 10 Eost 2026 da 10:10 UTCresolved

   This incident has been resolved.

1. 27 Gouere 2026 da 09:17 UTCinvestigating

   *.identity.tm domínios (incluindo página de status dedicada) não são resolvidos pelo DNS, resultando em falta de acesso aos sistemas.

2. 27 Gouere 2026 da 09:34 UTCmonitoring

   A resolução do DNS parece funcionar novamente. Estamos a recolher provas para investigação.

3. 27 Gouere 2026 da 09:46 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gouere 2026 da 09:31 UTCinvestigating

   Estamos a passar por uma perturbação de serviço para o robô de teste. Ao executar o robô de teste com o cenário HAPPYPATH, se houver uma inconsistência de dados entre os dados iniciais e os dados posteriormente enviados para o TestRobot com HAPPYPATH, o resultado da execução será SUCCESS DATA CHANGED (como no cenário CHANGEALL.) Na verdade, isto significa - HAPPYPATH não é atualmente capaz de produzir um resultado SUCESS se o comando robô é escrito para o primeiro ou último nome. Outros cenários robôs funcionam corretamente. Isso só afeta o robô VideoIdent e eSign TEST. Os produtos AutoIdent e InstantSign não são afetados. A produção não é afectada.

2. 5 Eost 2026 da 12:42 UTCmonitoring

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

3. 18 Eost 2026 da 13:55 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Gouere 2026 da 14:25 UTCinvestigating

   Estamos atualmente passando por uma interrupção de serviço. Nossas equipes de engenharia estão ativamente investigando o problema e trabalhando para restaurar toda a funcionalidade o mais rápido possível. Agradecemos sua paciência e forneceremos atualizações oportunas até que o serviço seja totalmente restaurado.

2. 20 Gouere 2026 da 15:12 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Gouere 2026 da 10:06 UTCmonitoring

   Identificamos um problema técnico em nossa interface de agente VideoIdent que causa um impacto no desempenho. A questão levou a uma disponibilidade reduzida de agentes de vídeo para usuários finais em nossos serviços VideoIdent e eSign. Uma solução foi lançada e estamos a monitorizar a situação. AutoIdent, AutoIdent QES, eID e InstantSign não foram afetados.

2. 3 Gouere 2026 da 12:12 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Mezheven 2026 da 07: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 Mezheven 2026 da 07:35 UTCmonitoring

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

3. 10 Mezheven 2026 da 07:42 UTCresolved

   This incident has been resolved.

1. 9 Mezheven 2026 da 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 Mezheven 2026 da 07:38 UTCresolved

   This incident has been resolved.

1. 5 Mae 2026 da 09: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 Mae 2026 da 09:43 UTCmonitoring

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

3. 5 Mae 2026 da 10:00 UTCresolved

   This incident has been resolved.

1. 28 Ebrel 2026 da 07: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 Ebrel 2026 da 08:08 UTCmonitoring

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

3. 28 Ebrel 2026 da 08:08 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28 Ebrel 2026 da 08:40 UTCresolved

   This incident has been resolved.

1. 21 Ebrel 2026 da 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 Ebrel 2026 da 17:48 UTCresolved

   This incident has been resolved.

1. 3 Ebrel 2026 da 07: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 Ebrel 2026 da 07:44 UTCidentified

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

3. 3 Ebrel 2026 da 07:50 UTCmonitoring

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

4. 3 Ebrel 2026 da 07:52 UTCresolved

   This incident has been resolved.

1. 25 Meurzh 2026 da 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 Meurzh 2026 da 15:39 UTCidentified

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

3. 25 Meurzh 2026 da 15:46 UTCmonitoring

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

4. 25 Meurzh 2026 da 15:57 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 Meurzh 2026 da 16:01 UTCresolved

   This incident has been resolved.

1. 18 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 13:41 UTCidentified

   A fix is being implemented.

4. 18 Meurzh 2026 da 13:53 UTCmonitoring

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

5. 18 Meurzh 2026 da 15:44 UTCmonitoring

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

6. 18 Meurzh 2026 da 16:25 UTCresolved

   This incident has been resolved.

1. 13 Meurzh 2026 da 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 Meurzh 2026 da 15:15 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 Meurzh 2026 da 15:35 UTCidentified

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

4. 13 Meurzh 2026 da 16:44 UTCidentified

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

5. 13 Meurzh 2026 da 17:35 UTCidentified

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

6. 13 Meurzh 2026 da 17:47 UTCmonitoring

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

7. 13 Meurzh 2026 da 18:04 UTCresolved

   This incident has been resolved.

1. 2 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 15:40 UTCidentified

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

3. 2 Cʼhwevrer 2026 da 15:42 UTCmonitoring

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

4. 2 Cʼhwevrer 2026 da 16:24 UTCresolved

   This incident has been resolved.

1. 29 Genver 2026 da 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 Genver 2026 da 15:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 Genver 2026 da 15:58 UTCmonitoring

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

4. 29 Genver 2026 da 15:59 UTCresolved

   This incident has been resolved.

1. 29 Genver 2026 da 07: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 Genver 2026 da 07:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 Genver 2026 da 08:12 UTCidentified

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

4. 29 Genver 2026 da 08:29 UTCidentified

   The services are gradually getting back online.

5. 29 Genver 2026 da 08:31 UTCidentified

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

6. 29 Genver 2026 da 09:26 UTCmonitoring

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

7. 29 Genver 2026 da 09:47 UTCresolved

   This incident has been resolved.

1. 11 Genver 2026 da 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 Genver 2026 da 10:39 UTCidentified

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

3. 11 Genver 2026 da 11:11 UTCmonitoring

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

4. 11 Genver 2026 da 18:16 UTCresolved

   This incident has been resolved.

1. 5 Genver 2026 da 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 Genver 2026 da 11:28 UTCidentified

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

3. 5 Genver 2026 da 11:46 UTCmonitoring

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

4. 5 Genver 2026 da 13:06 UTCresolved

   This incident has been resolved.