Störungsverlauf von Evidos

1. 4. September 2026 um 10:12 UTCinvestigating

   Wir haben derzeit ein Problem, das zu Verzögerungen bei der Zustellung von E-Mails führt, die von unserer Plattform gesendet werden. Infolgedessen können E-Mails länger dauern als erwartet, um die Empfänger zu erreichen.

2. 4. September 2026 um 12:49 UTCinvestigating

   Wir untersuchen Verzögerungen bei E-Mail-Benachrichtigungen, die von Signhost gesendet werden. Die Signhost-Plattform bleibt voll funktionsfähig und die Dokumentenverarbeitung ist nicht betroffen. Das Problem ist derzeit auf die E-Mail-Zustellung beschränkt, was dazu führen kann, dass Benachrichtigungen die Empfänger später als üblich erreichen. Wir arbeiten mit unserem E-Mail-Dienstleister zusammen, um das Problem so schnell wie möglich zu lösen

3. 4. September 2026 um 14:28 UTCidentified

   Wir haben festgestellt, dass die Verzögerungen bei den von Signhost gesendeten E-Mail-Benachrichtigungen mit einem umfassenderen Microsoft 365 Exchange Online-Vorfall zusammenhängen. Zu diesem Zeitpunkt bleibt die Signhost-Plattform voll funktionsfähig und die Dokumentenverarbeitung, die Signatur und die Transaktionsbearbeitung sind nicht betroffen. Die Auswirkungen beschränken sich auf E-Mail-Benachrichtigungen, die später als üblich zugestellt werden. Empfänger können Verzögerungen beim Empfang von Benachrichtigungen erleben. Wir beobachten die Situation zusammen mit unserem E-Mail-Dienstleister weiterhin genau. Wir werden das nächste Update am Montagmorgen zur Verfügung stellen.

4. 7. September 2026 um 06:18 UTCresolved

   Das Problem mit der Zustellung von E-Mail-Benachrichtigungen wurde behoben. E-Mail-Benachrichtigungen werden nun wie erwartet zugestellt, ohne dass weitere Verzögerungen beobachtet werden.

5. 7. September 2026 um 08:29 UTCpostmortem

   ### Was ist passiert? Am 4. September 2026 wurden einige Signhost-E-Mail-Benachrichtigungen, einschließlich der Unterzeichnung von Einladungen und Statusaktualisierungen, später als gewöhnlich zugestellt. Während dieser Zeit blieb die Signhost-Plattform voll funktionsfähig. Dokumentensignierung, Transaktionsverarbeitung und API-Funktionalität waren nicht betroffen. ### Was hat das Problem verursacht? Unsere Untersuchung bestätigte, dass die Verzögerungen durch einen umfassenderen Microsoft 365 Exchange Online-Vorfall verursacht wurden, der die Verarbeitung und Zustellung von E-Mails beeinflusste. Microsoft meldete Verzögerungen und "serverbesetzte" Fehler bei der Exchange Online-Infrastruktur. Das Problem entstand außerhalb von Signhost und stand nicht im Zusammenhang mit der Signhost-Anwendung, der Infrastruktur oder den Diensten. Es ist wichtig zu beachten, dass Signhost Microsoft Exchange Online nicht zum Senden von E-Mail-Benachrichtigungen verwendet. Unsere E-Mail-Zustellung erfolgt über SparkPost, unseren E-Mail-Dienstleister. Weitere Informationen zum Microsoft-Vorfall finden Sie hier: [Exchange Online-Ausfall verursacht E-Mail-Verzögerungen und Server-Besetztheitsfehler](https://www.bleepingcomputer.com/news/microsoft/exchange-online-outage-causes-email-delays-server-busy-errors/) ### Was haben wir gemacht? Wir haben eng mit unserem E-Mail-Dienstleister zusammengearbeitet, um die Situation zu überwachen und die Ursache zu überprüfen. Während des gesamten Vorfalls haben wir die Signhost-Dienste kontinuierlich überwacht und bestätigt, dass die Kernfunktionalität der Plattform unberührt bleibt. Sobald Microsoft den Exchange Online-Vorfall behoben hatte, wurde die E-Mail-Zustellung wieder normal. Wir haben überprüft, dass E-Mail-Benachrichtigungen jetzt wie erwartet zugestellt werden, ohne dass weitere Verzögerungen beobachtet werden. Wir möchten den Kunden versichern, dass keine Dokumente, Transaktionen oder Kundendaten betroffen waren und dass keine Maßnahmen Ihrerseits erforderlich sind.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juli 2026 um 12:49 UTCinvestigating

   Wir haben derzeit ein Problem, das die Überprüfungsmethode itsme Identification (AES) innerhalb von Signhost betrifft. Infolgedessen können Transaktionen, die diese Verifizierungsmethode verwenden, zu diesem Zeitpunkt nicht abgeschlossen werden. Wir untersuchen dieses Problem.

2. 23. Juli 2026 um 13:41 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 23. Juli 2026 um 13:57 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 23. Juli 2026 um 14:18 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. Juli 2026 um 14:25 UTCinvestigating

   Wir haben derzeit ein Problem mit iDIN- und iDEAL-Diensten innerhalb von Signhost. Infolgedessen können Transaktionen, die diese Methoden verwenden, zu diesem Zeitpunkt nicht abgeschlossen werden. Unser Team untersucht das Problem aktiv und arbeitet daran, den normalen Service so schnell wie möglich wiederherzustellen. Wir werden weitere Updates bereitstellen, sobald weitere Informationen verfügbar sind.

2. 17. Juli 2026 um 14:44 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 17. Juli 2026 um 14:47 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 17. Juli 2026 um 15:19 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. Juni 2026 um 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. Juni 2026 um 09:02 UTCmonitoring

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

3. 18. Juni 2026 um 09:16 UTCresolved

   This incident has been resolved.

1. 16. Juni 2026 um 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. Juni 2026 um 13:55 UTCmonitoring

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

3. 16. Juni 2026 um 14:09 UTCresolved

   This incident has been resolved.

1. 3. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 05:33 UTCmonitoring

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

4. 3. Juni 2026 um 05:49 UTCmonitoring

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

5. 3. Juni 2026 um 06:55 UTCresolved

   This incident has been resolved.

1. 28. Mai 2026 um 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. Mai 2026 um 08:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 28. Mai 2026 um 10:19 UTCidentified

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

4. 28. Mai 2026 um 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. Mai 2026 um 14:13 UTCmonitoring

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

6. 28. Mai 2026 um 14:24 UTCresolved

   This incident has been resolved.

1. 21. Mai 2026 um 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. Mai 2026 um 23:25 UTCidentified

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

3. 21. Mai 2026 um 23:28 UTCmonitoring

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

4. 21. Mai 2026 um 23:38 UTCresolved

   This incident has been resolved.

1. 5. Mai 2026 um 07:07 UTCidentified

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

2. 5. Mai 2026 um 08:11 UTCmonitoring

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

3. 5. Mai 2026 um 08:42 UTCresolved

   Signhost QES is operational again.

1. 21. April 2026 um 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. April 2026 um 05:48 UTCresolved

   This incident has been resolved.

1. 20. April 2026 um 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. April 2026 um 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. April 2026 um 08:00 UTCresolved

   This incident has been resolved.

1. 10. April 2026 um 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. April 2026 um 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. März 2026 um 12:29 UTCinvestigating

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

2. 23. März 2026 um 13:38 UTCmonitoring

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

3. 23. März 2026 um 14:01 UTCresolved

   The issues with DigiD have been resolved by Logius.

1. 17. März 2026 um 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. März 2026 um 09:59 UTCresolved

   This incident has been resolved.

1. 12. Februar 2026 um 10:07 UTCinvestigating

   We are currently investigating this issue.

2. 12. Februar 2026 um 10:44 UTCinvestigating

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

3. 12. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 15:08 UTCmonitoring

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

7. 12. Februar 2026 um 15:21 UTCresolved

   This incident has been resolved.

8. 18. Februar 2026 um 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. Januar 2026 um 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. Januar 2026 um 09:38 UTCmonitoring

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

3. 23. Januar 2026 um 10:09 UTCresolved

   This incident has been resolved.

1. 10. Dezember 2025 um 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. Dezember 2025 um 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. Dezember 2025 um 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. Dezember 2025 um 09:50 UTCresolved

   This incident has been resolved.

1. 25. November 2025 um 10:33 UTCinvestigating

   We are currently investigating this issue.

2. 25. November 2025 um 12:07 UTCidentified

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

3. 25. November 2025 um 12:10 UTCmonitoring

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

4. 25. November 2025 um 12:12 UTCresolved

   This incident has been resolved.

1. 18. November 2025 um 12:08 UTCinvestigating

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

2. 18. November 2025 um 12:31 UTCidentified

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

3. 18. November 2025 um 12:33 UTCmonitoring

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

4. 18. November 2025 um 12:37 UTCresolved

   This incident has been resolved.

1. 11. November 2025 um 14:40 UTCidentified

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

2. 11. November 2025 um 14:51 UTCidentified

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

3. 11. November 2025 um 15:12 UTCresolved

   This incident has been resolved.