54 Evidos incidents · juillet 2024 — official updates, affected components, duration and resolution details.
Nous enquêtons actuellement sur cette question.
Un correctif a été mis en place et nous suivons les résultats.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous sommes actuellement confrontés à un problème qui cause des retards dans la livraison des courriels envoyés depuis notre plateforme. Par conséquent, les courriels peuvent prendre plus de temps que prévu pour atteindre les destinataires.
Nous enquêtons sur les retards affectant les notifications électroniques envoyées par Signhost. La plateforme Signhost reste pleinement opérationnelle et le traitement des documents n'est pas affecté. À l'heure actuelle, la question se limite à la transmission des courriels, ce qui peut amener les destinataires à recevoir des notifications plus tard que d'habitude. Nous travaillons avec notre fournisseur de services d'email pour résoudre le problème le plus rapidement possible
Nous avons identifié que les retards affectant les notifications par courriel envoyées par Signhost sont liés à un incident Microsoft 365 Exchange Online plus large. À l'heure actuelle, la plateforme Signhost demeure pleinement opérationnelle et le traitement, la signature et le traitement des documents ne sont pas affectés. L'impact est limité aux notifications par courriel envoyées plus tard que d'habitude. Les bénéficiaires peuvent avoir des retards dans la réception des notifications. Nous continuons de suivre la situation de près avec notre fournisseur de services de messagerie. Nous présenterons la prochaine mise à jour lundi matin.
La question touchant la livraison des avis par courriel a été résolue. Les notifications par courriel sont maintenant envoyées comme prévu, sans que d'autres retards soient observés.
Que s'est-il passé ? Le 4 septembre 2026, certaines notifications par courriel de Signhost, y compris les invitations à signer et les mises à jour du statut, ont été envoyées plus tard que d'habitude. Pendant cette période, la plateforme Signhost est restée pleinement opérationnelle. La signature des documents, le traitement des transactions et la fonctionnalité de l'API n'ont pas été touchés. Qu'est-ce qui a causé le problème ? Notre enquête a confirmé que les retards ont été causés par un incident plus large de Microsoft 365 Exchange Online affectant le traitement et la livraison des courriels. Microsoft a signalé des retards et des erreurs du serveur occupé concernant l'infrastructure Exchange Online. La question a été soulevée à l'extérieur de Signhost et n'était pas liée à l'application, à l'infrastructure ou aux services de Signhost. Il est important de noter que Signhost n'utilise pas Microsoft Exchange Online pour envoyer des notifications par courriel. Notre livraison d'email est gérée par SparkPost, notre fournisseur de services d'email. Plus d'informations sur l'incident de Microsoft peuvent être trouvées ici: [Échanges La panne en ligne provoque des retards dans les courriels et des erreurs de serveur occupé](https://www.bleepingcomputer.com/news/microsoft/exchange-online-outage-causes-email-delays-server-busy-errors/) Ce qu'on a fait ? Nous avons travaillé en étroite collaboration avec notre fournisseur de services de courriel pour surveiller la situation et vérifier la cause profonde. Tout au long de l'incident, nous avons surveillé en permanence les services de Signhost et confirmé que la fonctionnalité de base de la plateforme n'était pas affectée. Une fois que Microsoft a résolu l'incident Exchange Online, la livraison de courriels est revenue à la normale. Nous avons vérifié que les notifications par courriel sont maintenant livrées comme prévu, sans autre retard observé. Nous tenons à rassurer les clients qu'aucun document, transaction ou donnée client n'a été touché et qu'aucune action n'est requise de votre part.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous sommes actuellement confrontés à un problème touchant la méthode de vérification de l'identification de son (AES) au sein de Signhost. Par conséquent, les opérations qui utilisent cette méthode de vérification ne peuvent pas être effectuées pour le moment. Nous enquêtons sur cette question.
Le problème a été identifié et une solution est en cours de mise en oeuvre.
Un correctif a été mis en place et nous suivons les résultats.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous sommes actuellement confrontés à un problème affectant les services iDIN et iDEAL au sein de Signhost. Par conséquent, les transactions qui utilisent ces méthodes ne peuvent pas être effectuées pour le moment. Notre équipe enquête activement sur la question et travaille à rétablir le service normal le plus rapidement possible. Nous fournirons d'autres mises à jour à mesure que de plus amples renseignements seront disponibles.
Le problème a été identifié et une solution est en cours de mise en oeuvre.
Un correctif a été mis en place et nous suivons les résultats.
Cet incident a été résolu.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
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.
