Evidos outage history

We are currently experiencing an issue that is causing delays in the delivery of emails sent from our platform. As a result, emails may take longer than expected to reach recipients.

We are investigating delays affecting email notifications sent by Signhost. The Signhost platform remains fully operational and document processing is not impacted. The issue is currently limited to email delivery, which may result in notifications reaching recipients later than usual. We are working with our email service provider to resolve the issue as quickly as possible

We have identified that the delays affecting email notifications sent by Signhost are related to a broader Microsoft 365 Exchange Online incident. At this time, the Signhost platform remains fully operational, and document processing, signing, and transaction handling are not affected. The impact is limited to email notifications being delivered later than usual. Recipients may experience delays in receiving notifications. We are continuing to monitor the situation closely together with our email service provider. We will provide the next update on Monday morning.

The issue affecting email notification delivery has been resolved. Email notifications are now being delivered as expected, with no further delays observed.

### What happened? On September 4th 2026, some Signhost email notifications, including signing invitations and status updates, were delivered later than usual. During this period, the Signhost platform remained fully operational. Document signing, transaction processing and API functionality were not affected. ### What caused the issue? Our investigation confirmed that the delays were caused by a broader Microsoft 365 Exchange Online incident affecting email processing and delivery. Microsoft reported delays and “server busy“ errors affecting Exchange Online infrastructure. The issue originated outside of Signhost and was not related to the Signhost application, infrastructure or services. It is important to note that Signhost does not use Microsoft Exchange Online to send email notifications. Our email delivery is handled through SparkPost, our email service provider. More information about the Microsoft incident can be found here: [Exchange Online outage causes email delays and server busy errors](https://www.bleepingcomputer.com/news/microsoft/exchange-online-outage-causes-email-delays-server-busy-errors/) ### What we did? We worked closely with our email service provider to monitor the situation and verify the root cause. Throughout the incident, we continuously monitored Signhost services and confirmed that core platform functionality remained unaffected. Once Microsoft resolved the Exchange Online incident, email delivery returned to normal. We have verified that email notifications are now being delivered as expected, with no further delays observed. We would like to reassure customers that no documents, transactions or customer data were impacted and no action is required on your part.

We are currently experiencing an issue affecting the itsme Identification (AES) verification method within Signhost. As a result, transactions that use this verification method cannot be completed at this time. We are 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.

We are currently experiencing an issue affecting iDIN and iDEAL services within Signhost. As a result, transactions that use these methods cannot be completed at this time. Our team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

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.

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.

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

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

This incident has been resolved.