Historial de interrupciones de Evidos

1. September 4, 2026 at 10:12 AM UTCinvestigating

   Actualmente estamos experimentando un problema que está causando retrasos en la entrega de correos electrónicos enviados desde nuestra plataforma. Como resultado, los correos electrónicos pueden tardar más de lo esperado para llegar a los destinatarios.

2. September 4, 2026 at 12:49 PM UTCinvestigating

   Estamos investigando retrasos que afectan las notificaciones de correo electrónico enviadas por Signhost. La plataforma Signhost sigue siendo plenamente operacional y el procesamiento de documentos no está afectado. La cuestión se limita actualmente a la entrega por correo electrónico, lo que puede dar lugar a notificaciones que lleguen a los destinatarios más adelante de lo habitual. Estamos trabajando con nuestro proveedor de servicios de correo electrónico para resolver el problema lo antes posible

3. September 4, 2026 at 2:28 PM UTCidentified

   Hemos identificado que los retrasos que afectan las notificaciones de correo electrónico enviadas por Signhost están relacionados con un incidente más amplio de Microsoft 365 Exchange Online. En este momento, la plataforma Signhost sigue siendo plenamente operacional, y el procesamiento, la firma y el manejo de transacciones no están afectados. El impacto se limita a las notificaciones de correo electrónico que se envían más tarde de lo habitual. Los beneficiarios pueden experimentar retrasos en la recepción de notificaciones. Continuamos monitoreando la situación de cerca junto con nuestro proveedor de servicios de correo electrónico. Vamos a proporcionar la siguiente actualización el lunes por la mañana.

4. September 7, 2026 at 6:18 AM UTCresolved

   Se ha resuelto la cuestión que afecta a la notificación por correo electrónico. Las notificaciones por correo electrónico se están entregando como se espera, sin más demoras observadas.

5. September 7, 2026 at 8:29 AM UTCpostmortem

   ### ¿Qué pasó? El 4 de septiembre de 2026, algunas notificaciones de email Signhost, incluyendo invitaciones de firma y actualizaciones de estado, fueron entregadas más tarde de lo habitual. Durante este período, la plataforma Signhost siguió siendo plenamente operacional. La firma de documentos, el procesamiento de transacciones y la funcionalidad de API no se vieron afectados. ### ¿Qué causó el problema? Nuestra investigación confirmó que los retrasos fueron causados por un incidente más amplio de Microsoft 365 Exchange Online que afectó el procesamiento y la entrega del correo electrónico. Microsoft reportó retrasos y errores “servidor ocupado” que afectan la infraestructura de Exchange Online. La cuestión se originó fuera de Signhost y no estaba relacionada con la aplicación Signhost, la infraestructura o los servicios. Es importante señalar que Signhost no utiliza Microsoft Exchange Online para enviar notificaciones de correo electrónico. Nuestra entrega de correo electrónico se maneja a través de SparkPost, nuestro proveedor de servicios de correo electrónico. Más información sobre el incidente de Microsoft se puede encontrar aquí: [Exchange Online outage causes email delays and server Hungarian errors](https://www.bleepingcomputer.com/news/microsoft/exchange-online-outage-Causes-email-delays-servidor-busy-errors/) ### ¿Qué hicimos? Trabajamos estrechamente con nuestro proveedor de servicios de correo electrónico para supervisar la situación y verificar la causa raíz. A lo largo del incidente, monitoreamos continuamente los servicios de Signhost y confirmamos que la funcionalidad de la plataforma central no se vio afectada. Una vez que Microsoft resolvió el incidente de Exchange Online, la entrega de correo electrónico volvió a la normalidad. Hemos verificado que las notificaciones de correo electrónico se están entregando como se espera, sin más demoras observadas. Quisiéramos asegurar a los clientes que no se impactaron documentos, transacciones o datos del cliente y que no se requiere ninguna acción por su parte.

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

1. July 23, 2026 at 12:49 PM UTCinvestigating

   Actualmente estamos experimentando un problema que afecta al método de verificación de sume Identificación (AES) dentro de Signhost. En consecuencia, las transacciones que utilizan este método de verificación no pueden completarse en este momento. Estamos investigando este tema.

2. July 23, 2026 at 1:41 PM UTCidentified

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

3. July 23, 2026 at 1:57 PM UTCmonitoring

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

4. July 23, 2026 at 2:18 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 17, 2026 at 2:25 PM UTCinvestigating

   Actualmente estamos experimentando un problema que afecta a los servicios iDIN e iDEAL dentro de Signhost. Como resultado, las transacciones que utilizan estos métodos no pueden completarse en este momento. Nuestro equipo está investigando activamente la cuestión y trabajando para restaurar el servicio normal lo antes posible. Proporcionaremos más actualizaciones a medida que se disponga de más información.

2. July 17, 2026 at 2:44 PM UTCidentified

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

3. July 17, 2026 at 2:47 PM UTCmonitoring

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

4. July 17, 2026 at 3:19 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 18, 2026 at 7:16 AM 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. June 18, 2026 at 9:02 AM UTCmonitoring

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

3. June 18, 2026 at 9:16 AM UTCresolved

   This incident has been resolved.

1. June 16, 2026 at 1:27 PM UTCinvestigating

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

2. June 16, 2026 at 1:55 PM UTCmonitoring

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

3. June 16, 2026 at 2:09 PM UTCresolved

   This incident has been resolved.

1. June 3, 2026 at 4:55 AM 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. June 3, 2026 at 5:22 AM 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. June 3, 2026 at 5:33 AM UTCmonitoring

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

4. June 3, 2026 at 5:49 AM UTCmonitoring

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

5. June 3, 2026 at 6:55 AM UTCresolved

   This incident has been resolved.

1. May 28, 2026 at 7:06 AM 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. May 28, 2026 at 8:30 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 28, 2026 at 10:19 AM UTCidentified

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

4. May 28, 2026 at 1:31 PM 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. May 28, 2026 at 2:13 PM UTCmonitoring

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

6. May 28, 2026 at 2:24 PM UTCresolved

   This incident has been resolved.

1. May 21, 2026 at 11:05 PM 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. May 21, 2026 at 11:25 PM UTCidentified

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

3. May 21, 2026 at 11:28 PM UTCmonitoring

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

4. May 21, 2026 at 11:38 PM UTCresolved

   This incident has been resolved.

1. May 5, 2026 at 7:07 AM UTCidentified

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

2. May 5, 2026 at 8:11 AM UTCmonitoring

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

3. May 5, 2026 at 8:42 AM UTCresolved

   Signhost QES is operational again.

1. April 21, 2026 at 3:35 PM UTCidentified

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

2. April 22, 2026 at 5:48 AM UTCresolved

   This incident has been resolved.

1. April 20, 2026 at 7:52 AM 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. April 20, 2026 at 7:57 AM 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. April 20, 2026 at 8:00 AM UTCresolved

   This incident has been resolved.

1. April 10, 2026 at 1:29 PM 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. April 13, 2026 at 10:35 AM 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. March 23, 2026 at 12:29 PM UTCinvestigating

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

2. March 23, 2026 at 1:38 PM UTCmonitoring

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

3. March 23, 2026 at 2:01 PM UTCresolved

   The issues with DigiD have been resolved by Logius.

1. March 17, 2026 at 9:34 AM 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. March 17, 2026 at 9:59 AM UTCresolved

   This incident has been resolved.

1. February 12, 2026 at 10:07 AM UTCinvestigating

   We are currently investigating this issue.

2. February 12, 2026 at 10:44 AM UTCinvestigating

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

3. February 12, 2026 at 11:58 AM 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. February 12, 2026 at 1:00 PM 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. February 12, 2026 at 2:05 PM 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. February 12, 2026 at 3:08 PM UTCmonitoring

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

7. February 12, 2026 at 3:21 PM UTCresolved

   This incident has been resolved.

8. February 18, 2026 at 9:45 AM 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. January 23, 2026 at 9:21 AM 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. January 23, 2026 at 9:38 AM UTCmonitoring

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

3. January 23, 2026 at 10:09 AM UTCresolved

   This incident has been resolved.

1. December 10, 2025 at 9:10 AM 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. December 10, 2025 at 9:33 AM 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. December 10, 2025 at 9:37 AM UTCmonitoring

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

4. December 10, 2025 at 9:50 AM UTCresolved

   This incident has been resolved.

1. November 25, 2025 at 10:33 AM UTCinvestigating

   We are currently investigating this issue.

2. November 25, 2025 at 12:07 PM UTCidentified

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

3. November 25, 2025 at 12:10 PM UTCmonitoring

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

4. November 25, 2025 at 12:12 PM UTCresolved

   This incident has been resolved.

1. November 18, 2025 at 12:08 PM UTCinvestigating

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

2. November 18, 2025 at 12:31 PM UTCidentified

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

3. November 18, 2025 at 12:33 PM UTCmonitoring

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

4. November 18, 2025 at 12:37 PM UTCresolved

   This incident has been resolved.

1. November 11, 2025 at 2:40 PM UTCidentified

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

2. November 11, 2025 at 2:51 PM UTCidentified

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

3. November 11, 2025 at 3:12 PM UTCresolved

   This incident has been resolved.