There were 6 Evidos outages since February 12, 2026 totaling 90h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
Pingoru polls Evidos's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required