Histórico de interrupções do Evidos

1. 4 Gwengolo 2026 da 10:12 UTCinvestigating

   Atualmente estamos experimentando um problema que está causando atrasos na entrega de e-mails enviados da nossa plataforma. Como resultado, os e-mails podem levar mais tempo do que o esperado para chegar aos destinatários.

2. 4 Gwengolo 2026 da 12:49 UTCinvestigating

   Estamos investigando atrasos que afetam notificações de e-mail enviadas pelo Signhost. A plataforma Signhost permanece totalmente operacional e o processamento de documentos não é impactado. O problema está atualmente limitado à entrega por e-mail, o que pode resultar em notificações que chegam aos destinatários mais tarde do que o habitual. Estamos trabalhando com nosso provedor de serviço de email para resolver o problema o mais rápido possível

3. 4 Gwengolo 2026 da 14:28 UTCidentified

   Identificamos que os atrasos que afetam as notificações de e-mail enviadas pelo Signhost estão relacionados a um incidente mais amplo do Microsoft 365 Exchange Online. Neste momento, a plataforma Signhost continua totalmente operacional, e o processamento, assinatura e processamento de documentos não são afetados. O impacto é limitado a notificações por e-mail sendo entregues mais tarde do que o habitual. Os beneficiários podem registar atrasos na recepção das notificações. Continuamos a monitorar a situação de perto com o nosso provedor de serviços de e-mail. Apresentaremos a próxima actualização na segunda-feira de manhã.

4. 7 Gwengolo 2026 da 06:18 UTCresolved

   O problema que afeta a entrega de notificação por email foi resolvido. As notificações de e-mail estão sendo entregues como esperado, sem mais atrasos observados.

5. 7 Gwengolo 2026 da 08:29 UTCpostmortem

   O que aconteceu? Em 4 de setembro de 2026, algumas notificações por e-mail Signhost, incluindo convites de assinatura e atualizações de status, foram entregues mais tarde do que o normal. Durante este período, a plataforma Signhost permaneceu totalmente operacional. A assinatura de documentos, o processamento de transações e a funcionalidade da API não foram afetadas. O que causou o problema? Nossa investigação confirmou que os atrasos foram causados por um incidente mais amplo do Microsoft 365 Exchange Online afetando o processamento e entrega de email. A Microsoft relatou atrasos e erros “servidor ocupado” que afetam a infraestrutura Exchange Online. A questão originou-se fora da Signhost e não estava relacionada com o aplicativo Signhost, infraestrutura ou serviços. É importante notar que Signhost não usa o Microsoft Exchange Online para enviar notificações por e-mail. Nossa entrega de e-mail é tratada através da SparkPost, nosso provedor de serviços de e-mail. Mais informações sobre o incidente da Microsoft podem ser encontradas aqui: [Exchange Online outage causa atrasos no e-mail e erros de ocupado do servidor](https://www.beelingcomputer.com/news/microsoft/exchange-online-outage-causes-email-delays-server-busy-errors/) O que fizemos? Trabalhamos em estreita colaboração com nosso provedor de serviços de email para monitorar a situação e verificar a causa raiz. Durante todo o incidente, monitoramos continuamente os serviços Signhost e confirmamos que a funcionalidade da plataforma principal não foi afetada. Uma vez que a Microsoft resolveu o incidente Exchange Online, a entrega de e-mail retornou ao normal. Verificamos que as notificações por e-mail estão sendo entregues como esperado, sem mais atrasos observados. Gostaríamos de garantir aos clientes que nenhum documento, transações ou dados do cliente foram impactados e nenhuma ação é necessária de sua parte.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Gouere 2026 da 12:49 UTCinvestigating

   Atualmente estamos experimentando um problema que afeta o método de verificação itsme Identificação (AES) dentro do Signhost. Como resultado, as transações que utilizam este método de verificação não podem ser concluídas neste momento. Estamos a investigar esta questão.

2. 23 Gouere 2026 da 13:41 UTCidentified

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

3. 23 Gouere 2026 da 13:57 UTCmonitoring

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

4. 23 Gouere 2026 da 14:18 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Gouere 2026 da 14:25 UTCinvestigating

   Atualmente estamos experimentando um problema que afeta serviços iDIN e iDEAL no Signhost. Como resultado, as transações que utilizam esses métodos não podem ser concluídas neste momento. Nossa equipe está ativamente investigando o problema e trabalhando para restaurar o serviço normal o mais rápido possível. Forneceremos atualizações adicionais à medida que mais informações estiverem disponíveis.

2. 17 Gouere 2026 da 14:44 UTCidentified

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

3. 17 Gouere 2026 da 14:47 UTCmonitoring

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

4. 17 Gouere 2026 da 15:19 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 18 Mezheven 2026 da 07:16 UTCinvestigating

   We are currently experiencing issues with the verification method itsme Identification (AES). As a result, signers may be unable to complete the signing process. The itsme Sign (QES) method via CSC Qualified verification is not affected. Our team is actively investigating the issue.

2. 18 Mezheven 2026 da 09:02 UTCmonitoring

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

3. 18 Mezheven 2026 da 09:16 UTCresolved

   This incident has been resolved.

1. 16 Mezheven 2026 da 13:27 UTCinvestigating

   We are currently experiencing problems with ID Proof. We are investigating this issue. ID Proof is unable to be used momentarily.

2. 16 Mezheven 2026 da 13:55 UTCmonitoring

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

3. 16 Mezheven 2026 da 14:09 UTCresolved

   This incident has been resolved.

1. 3 Mezheven 2026 da 04:55 UTCinvestigating

   Currently investigating an outage of the API and signing service. Transaction creation is not possible. Sorry for the inconvenience. This has our highest attention and we'll keep you updated.

2. 3 Mezheven 2026 da 05:22 UTCidentified

   The incident has been identified at our hosting provider, TransIP, causing a temporary outage in service. Recovery work is in progress. For live updates on the incident, please visit https://transnoc.nl.

3. 3 Mezheven 2026 da 05:33 UTCmonitoring

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

4. 3 Mezheven 2026 da 05:49 UTCmonitoring

   Looks like the fix is holding. We'll keep monitoring the situation.

5. 3 Mezheven 2026 da 06:55 UTCresolved

   This incident has been resolved.

1. 28 Mae 2026 da 07:06 UTCinvestigating

   We are currently experiencing issues with the verification method itsme Identification (AES). As a result, signers may be unable to complete the signing process. The itsme Sign (QES) method via CSC Qualified verification is not affected. Our team is actively investigating the issue.

2. 28 Mae 2026 da 08:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 Mae 2026 da 10:19 UTCidentified

   The issue has been identified. We will proceed to implement a fix for this issue.

4. 28 Mae 2026 da 13:31 UTCinvestigating

   We are continuing to investigate the issue with the verification method itsme Identification (AES). Signers may still experience issues completing the signing process. The itsme Sign (QES) method via CSC Qualified verification remains unaffected. We will share further updates as soon as more information becomes available.

5. 28 Mae 2026 da 14:13 UTCmonitoring

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

6. 28 Mae 2026 da 14:24 UTCresolved

   This incident has been resolved.

1. 21 Mae 2026 da 23:05 UTCinvestigating

   Currently we're investigating an issue causing delays in transaction processing. A subset of requests may take longer than expected to complete, and in some cases may time out before processing finishes. We are actively working to reduce the delay and restore normal performance. We will provide another update as soon as we have more information.

2. 21 Mae 2026 da 23:25 UTCidentified

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

3. 21 Mae 2026 da 23:28 UTCmonitoring

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

4. 21 Mae 2026 da 23:38 UTCresolved

   This incident has been resolved.

1. 5 Mae 2026 da 07:07 UTCidentified

   Our provider is experiencing issues. The Signhost QES verification cannot be completed for now.

2. 5 Mae 2026 da 08:11 UTCmonitoring

   The issue has been fixed. We are monitoring the situation.

3. 5 Mae 2026 da 08:42 UTCresolved

   Signhost QES is operational again.

1. 21 Ebrel 2026 da 15:35 UTCidentified

   Our provider is experiencing problems. Signhost QES cannot be used. The issue has been identified, the resolution is being handled.

2. 22 Ebrel 2026 da 05:48 UTCresolved

   This incident has been resolved.

1. 20 Ebrel 2026 da 07:52 UTCinvestigating

   Itsme is currently experiencing a technical issue affecting 25% or more of their transactions since 9:25 AM CET. Their technical teams are actively investigating the problem and working to resolve it as quickly as possible. We understand the inconvenience this may cause and will continue to monitor the situation closely. Updates will be provided as soon as more information becomes available.

2. 20 Ebrel 2026 da 07:57 UTCmonitoring

   Itsme has identified the root cause of the issue. Their systems are currently recovering, and their technical teams are closely monitoring stability to ensure a full and safe resolution. We will continue to monitor the situation and share further updates as soon as they become available.

3. 20 Ebrel 2026 da 08:00 UTCresolved

   This incident has been resolved.

1. 10 Ebrel 2026 da 13:29 UTCidentified

   Some customers may experience issues starting ID validation in the Signhost app on Android devices. Instead of launching the ID validation flow, users are prompted to log in. Our team is working on a fix and we will provide further updates as progress is made. Our signing services are not affected.

2. 13 Ebrel 2026 da 10:35 UTCresolved

   A fix has been released to the Google app store and the deeplink problem is solved. Updating the Android app lets users finish identification.

1. 23 Meurzh 2026 da 12:29 UTCinvestigating

   There are currently issues with logging into DigiD. Logius is investigating the issue, we will communicate any updates.

2. 23 Meurzh 2026 da 13:38 UTCmonitoring

   The issues with logging into DigiD have been solved by Logius.

3. 23 Meurzh 2026 da 14:01 UTCresolved

   The issues with DigiD have been resolved by Logius.

1. 17 Meurzh 2026 da 09:34 UTCmonitoring

   We see degraded performance with the CSC Qualified verification method. Some signers may encounter issues completing the signing process. A fix has been implemented, and we are now monitoring the system to ensure full recovery. We will update this status once we confirm that the issue has been fully resolved.

2. 17 Meurzh 2026 da 09:59 UTCresolved

   This incident has been resolved.

1. 12 Cʼhwevrer 2026 da 10:07 UTCinvestigating

   We are currently investigating this issue.

2. 12 Cʼhwevrer 2026 da 10:44 UTCinvestigating

   Unfortunately, we have not yet been able to identify the problem. We are continuing to investigate this issue.

3. 12 Cʼhwevrer 2026 da 11:58 UTCinvestigating

   We have identified a possible cause and are in contact with our provider. We are continuing to investigate the issue with the highest priority.

4. 12 Cʼhwevrer 2026 da 13:00 UTCinvestigating

   Unfortunately, we have not yet been able to identify the exact cause of the issue. We are continuing our investigation in collaboration with our hosting provider.

5. 12 Cʼhwevrer 2026 da 14:05 UTCinvestigating

   We are still investigating the issue and have not yet identified a root cause. Downloading documents may fail initially but generally succeeds after several retries. At this time, approximately 3–5% of transactions are impacted. For signing transaction, we are observing an increase in queue length. These queued transactions will be retried once the issue is fully resolved. This incident remains our highest priority, and we continue to work on identifying and resolving the underlying cause.

6. 12 Cʼhwevrer 2026 da 15:08 UTCmonitoring

   We are currently not seeing any errors and will continue to monitor the situation.

7. 12 Cʼhwevrer 2026 da 15:21 UTCresolved

   This incident has been resolved.

8. 18 Cʼhwevrer 2026 da 09:45 UTCpostmortem

   ### What happened? On Thursday, February 12th, around 10:30 CEST, we observed an increase in errors affecting the file download and file preview functionalities. As a result, customers experienced issues downloading documents or receipts and viewing documents during signing. In many cases, the action succeeded after retrying. After resolving the incident, we retried open transactions on our end resulting in under 1% of transactions ending in an error state. In some cases, this may have been caused by transactions that were deleted in the meantime. ### What we did Once the increase in errors was detected, our team immediately started investigating the issue. Initial analysis focused on our application and infrastructure, but after ruling out internal causes, we escalated the issue to our hosting provider. ### What caused the issue? The incident was caused by a misconfiguration at our hosting provider during a migration. Because of this incorrect setting: * Larger data packets within the data center were dropped. * This led to failures on our side when retrieving or previewing files. ### What are we doing next? To resolve the incident, the hosting provider corrected the configuration on the affected switches, fully mitigating the issue. To reduce the likelihood of recurrence and improve detection going forward, the following improvements are being implemented: * Improved monitoring: Thresholds in the monitoring system of our hosting provider that tracks specific error rates will be adjusted so similar issues can be detected earlier. * Faster escalation: We are reviewing escalation procedures with our hosting provider to shorten investigation time for infrastructure related incidents. * Hosting migration: We are migrating our file services to another hosting provider this quarter to have more control over configuration.

1. 23 Genver 2026 da 09:21 UTCinvestigating

   Customers are experiencing issues with logging in to the Signhost web portal. After filling in log in credentials an error message is received: "Invalid credentials" We are investigating the issue.

2. 23 Genver 2026 da 09:38 UTCmonitoring

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

3. 23 Genver 2026 da 10:09 UTCresolved

   This incident has been resolved.

1. 10 Kerzu 2025 da 09:10 UTCinvestigating

   Itsme is currently experiencing a technical issue affecting 25% or more of their transactions since 9:40 AM CET. Their technical teams are actively investigating the problem and working to resolve it as quickly as possible. We understand the inconvenience this may cause and will continue to monitor the situation closely. Updates will be provided as soon as more information becomes available.

2. 10 Kerzu 2025 da 09:33 UTCinvestigating

   itsme is still investigating the issue, and systems are beginning to recover. Full service has not yet been restored. We will share updates as soon as more information is available. Thank you for your patience.

3. 10 Kerzu 2025 da 09:37 UTCmonitoring

   itsme has implemented a solution, and the service has been restored. The situation is being closely monitored to ensure stability.

4. 10 Kerzu 2025 da 09:50 UTCresolved

   This incident has been resolved.

1. 25 Du 2025 da 10:33 UTCinvestigating

   We are currently investigating this issue.

2. 25 Du 2025 da 12:07 UTCidentified

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

3. 25 Du 2025 da 12:10 UTCmonitoring

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

4. 25 Du 2025 da 12:12 UTCresolved

   This incident has been resolved.

1. 18 Du 2025 da 12:08 UTCinvestigating

   Signers are experiencing issues when signing with a CSC Qualified verification method. We are investigating the issues.

2. 18 Du 2025 da 12:31 UTCidentified

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

3. 18 Du 2025 da 12:33 UTCmonitoring

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

4. 18 Du 2025 da 12:37 UTCresolved

   This incident has been resolved.

1. 11 Du 2025 da 14:40 UTCidentified

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

2. 11 Du 2025 da 14:51 UTCidentified

   We see a very high peak load and have put our systems in maintenance until this subsides.

3. 11 Du 2025 da 15:12 UTCresolved

   This incident has been resolved.