54 Evidos incidents · luglio 2024 — official updates, affected components, duration and resolution details.
Stiamo attualmente indagando su questo problema.
Una soluzione è stata implementata e stiamo monitorando i risultati.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Attualmente stiamo vivendo un problema che sta causando ritardi nella consegna delle email inviate dalla nostra piattaforma. Di conseguenza, le e-mail possono richiedere più tempo del previsto per raggiungere i destinatari.
Stiamo indagando ritardi che riguardano le notifiche e-mail inviate da Signhost. La piattaforma Signhost rimane completamente operativa e l'elaborazione dei documenti non è influenzata. Il problema è attualmente limitato alla consegna e-mail, che può portare a notifiche che raggiungono i destinatari più tardi del solito. Stiamo lavorando con il nostro fornitore di servizi e-mail per risolvere il problema il più rapidamente possibile
Abbiamo identificato che i ritardi che riguardano le notifiche e-mail inviate da Signhost sono correlati a un più ampio incidente Microsoft 365 Exchange Online. In questo momento, la piattaforma Signhost rimane pienamente operativa, e l'elaborazione dei documenti, la firma e la gestione delle transazioni non sono interessati. L'impatto è limitato alle notifiche via e-mail che vengono consegnate più tardi del solito. I destinatari possono sperimentare ritardi nella ricezione delle notifiche. Stiamo continuando a monitorare la situazione da vicino insieme al nostro fornitore di servizi e-mail. Forneremo il prossimo aggiornamento il lunedì mattina.
Il problema che riguarda la consegna della notifica e-mail è stato risolto. Le notifiche via e-mail sono ora consegnate come previsto, senza ulteriori ritardi osservati.
### Che è successo? Il 4 settembre 2026, alcune notifiche di posta elettronica Signhost, tra cui la firma di inviti e aggiornamenti di stato, sono stati consegnati più tardi del solito. Durante questo periodo, la piattaforma Signhost rimase completamente operativa. La firma dei documenti, l'elaborazione delle transazioni e la funzionalità API non sono state interessate. ### Che cosa ha causato il problema? La nostra indagine ha confermato che i ritardi sono stati causati da un più ampio incidente Microsoft 365 Exchange Online che riguarda l'elaborazione e la consegna di e-mail. Microsoft ha riferito ritardi e “server occupato“ errori che interessano le infrastrutture Exchange Online. Il problema ha avuto origine al di fuori di Signhost e non era legato all'applicazione Signhost, alle infrastrutture o ai servizi. È importante notare che Signhost non utilizza Microsoft Exchange Online per inviare notifiche e-mail. La nostra e-mail di consegna viene gestita tramite SparkPost, il nostro fornitore di servizi e-mail. Ulteriori informazioni sull'incidente di Microsoft possono essere trovate qui: [Exchange Online outage cause e-mail delays and server busy error](https://www.bleepingcomputer.com/news/microsoft/exchange-online-outage-causes-email-server-busy-errors/) ### Che cosa abbiamo fatto? Abbiamo lavorato a stretto contatto con il nostro fornitore di servizi e-mail per monitorare la situazione e verificare la causa principale. Durante l'incidente, abbiamo monitorato continuamente i servizi Signhost e confermato che le funzionalità della piattaforma core non sono state influenzate. Una volta che Microsoft ha risolto l'incidente Exchange Online, la consegna e-mail ritorna alla normalità. Abbiamo verificato che le notifiche via e-mail vengono ora consegnate come previsto, senza ulteriori ritardi osservati. Vorremmo rassicurare i clienti che nessun documento, transazioni o dati del cliente sono stati influenzati e nessuna azione è richiesta da parte vostra.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Attualmente stiamo vivendo un problema che riguarda il suome Identification (AES) metodo di verifica all'interno di Signhost. Di conseguenza, le transazioni che utilizzano questo metodo di verifica non possono essere completate in questo momento. Stiamo indagando su questo problema.
Il problema è stato identificato e si sta attuando una correzione.
Una soluzione è stata implementata e stiamo monitorando i risultati.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Stiamo vivendo un problema che riguarda i servizi iDIN e iDEAL all'interno di Signhost. Di conseguenza, le transazioni che utilizzano questi metodi non possono essere completate in questo momento. Il nostro team sta attivamente indagando sul problema e lavorando per ripristinare il servizio normale il più rapidamente possibile. Forniremo ulteriori aggiornamenti in quanto ulteriori informazioni diventano disponibili.
Il problema è stato identificato e si sta attuando una correzione.
Una soluzione è stata implementata e stiamo monitorando i risultati.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing problems with ID Proof. We are investigating this issue. ID Proof is unable to be used momentarily.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
A fix has been implemented and we are monitoring the results.
Looks like the fix is holding. We'll keep monitoring the situation.
This incident has been resolved.
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.
We are continuing to investigate this issue.
The issue has been identified. We will proceed to implement a fix for this issue.
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.
A fix has been implemented, we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our provider is experiencing issues. The Signhost QES verification cannot be completed for now.
The issue has been fixed. We are monitoring the situation.
Signhost QES is operational again.
Our provider is experiencing problems. Signhost QES cannot be used. The issue has been identified, the resolution is being handled.
This incident has been resolved.
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.
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.
This incident has been resolved.
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.
A fix has been released to the Google app store and the deeplink problem is solved. Updating the Android app lets users finish identification.
There are currently issues with logging into DigiD. Logius is investigating the issue, we will communicate any updates.
The issues with logging into DigiD have been solved by Logius.
The issues with DigiD have been resolved by Logius.
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.
This incident has been resolved.
We are currently investigating this issue.
Unfortunately, we have not yet been able to identify the problem. We are continuing to investigate this issue.
We have identified a possible cause and are in contact with our provider. We are continuing to investigate the issue with the highest priority.
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.
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.
We are currently not seeing any errors and will continue to monitor the situation.
This incident has been resolved.
### 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.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
itsme has implemented a solution, and the service has been restored. The situation is being closely monitored to ensure stability.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Signers are experiencing issues when signing with a CSC Qualified verification method. We are investigating the issues.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
