Evidos Outage History

Evidos is up right now

Evidos had 38 outages in the last 2 years totaling 201h 52m of downtime — averaging 1.6 incidents per month.

There were 38 Evidos outages since July 15, 2024 totaling 201h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.signhost.com

Notice June 3, 2026

Major outage

Detected by Pingoru
Jun 03, 2026, 04:55 AM UTC
Resolved
Jun 03, 2026, 06:55 AM UTC
Duration
2h
Affected: APIUI / View
Timeline · 5 updates
  1. investigating Jun 03, 2026, 04:55 AM UTC

    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. identified Jun 03, 2026, 05:22 AM UTC

    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. monitoring Jun 03, 2026, 05:33 AM UTC

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

  4. monitoring Jun 03, 2026, 05:49 AM UTC

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

  5. resolved Jun 03, 2026, 06:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 28, 2026

Issue with verification method Itsme Identification (AES)

Detected by Pingoru
May 28, 2026, 07:06 AM UTC
Resolved
May 28, 2026, 02:24 PM UTC
Duration
7h 18m
Affected: itsme Identification
Timeline · 6 updates
  1. investigating May 28, 2026, 07:06 AM UTC

    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. investigating May 28, 2026, 08:30 AM UTC

    We are continuing to investigate this issue.

  3. identified May 28, 2026, 10:19 AM UTC

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

  4. investigating May 28, 2026, 01:31 PM UTC

    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. monitoring May 28, 2026, 02:13 PM UTC

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

  6. resolved May 28, 2026, 02:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 21, 2026

Investigating Delays In Transaction Processing

Detected by Pingoru
May 21, 2026, 11:05 PM UTC
Resolved
May 21, 2026, 11:38 PM UTC
Duration
33m
Affected: APIPortal
Timeline · 4 updates
  1. investigating May 21, 2026, 11:05 PM UTC

    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. identified May 21, 2026, 11:25 PM UTC

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

  3. monitoring May 21, 2026, 11:28 PM UTC

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

  4. resolved May 21, 2026, 11:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 5, 2026

Signhost QES - Outage

Detected by Pingoru
May 05, 2026, 07:07 AM UTC
Resolved
May 05, 2026, 08:42 AM UTC
Duration
1h 34m
Affected: Signhost QES
Timeline · 3 updates
  1. identified May 05, 2026, 07:07 AM UTC

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

  2. monitoring May 05, 2026, 08:11 AM UTC

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

  3. resolved May 05, 2026, 08:42 AM UTC

    Signhost QES is operational again.

Read the full incident report →

Minor April 20, 2026

Verification method itsme is currently experiencing issues

Detected by Pingoru
Apr 20, 2026, 07:52 AM UTC
Resolved
Apr 20, 2026, 08:00 AM UTC
Duration
7m
Affected: itsme sign (qualified signature)itsme Identification
Timeline · 3 updates
  1. investigating Apr 20, 2026, 07:52 AM UTC

    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. monitoring Apr 20, 2026, 07:57 AM UTC

    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. resolved Apr 20, 2026, 08:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 10, 2026

ID Proof - ID validation fails to start in Signhost Android app

Detected by Pingoru
Apr 10, 2026, 01:29 PM UTC
Resolved
Apr 13, 2026, 10:35 AM UTC
Duration
2d 21h
Affected: ID ProofSignhost App
Timeline · 2 updates
  1. identified Apr 10, 2026, 01:29 PM UTC

    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. resolved Apr 13, 2026, 10:35 AM UTC

    A fix has been released to the Google app store and the deeplink problem is solved. Updating the Android app lets users finish identification.

Read the full incident report →

Critical March 23, 2026

DigiD outage

Detected by Pingoru
Mar 23, 2026, 12:29 PM UTC
Resolved
Mar 23, 2026, 02:01 PM UTC
Duration
1h 32m
Affected: DigiD
Timeline · 3 updates
  1. investigating Mar 23, 2026, 12:29 PM UTC

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

  2. monitoring Mar 23, 2026, 01:38 PM UTC

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

  3. resolved Mar 23, 2026, 02:01 PM UTC

    The issues with DigiD have been resolved by Logius.

Read the full incident report →

Minor March 17, 2026

Degraded Performance – CSC Qualified Verification

Detected by Pingoru
Mar 17, 2026, 09:34 AM UTC
Resolved
Mar 17, 2026, 09:59 AM UTC
Duration
25m
Affected: itsme sign (qualified signature)ZealiD QualifiedSignhost QES
Timeline · 2 updates
  1. monitoring Mar 17, 2026, 09:34 AM UTC

    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. resolved Mar 17, 2026, 09:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 23, 2026

Issues with logging in to Signhost web portal

Detected by Pingoru
Jan 23, 2026, 09:21 AM UTC
Resolved
Jan 23, 2026, 10:09 AM UTC
Duration
48m
Affected: PortalAuth and login service
Timeline · 3 updates
  1. investigating Jan 23, 2026, 09:21 AM UTC

    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. monitoring Jan 23, 2026, 09:38 AM UTC

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

  3. resolved Jan 23, 2026, 10:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 25, 2025

Issues with creating transactions in webportal using Onfido verification

Detected by Pingoru
Nov 25, 2025, 10:33 AM UTC
Resolved
Nov 25, 2025, 12:12 PM UTC
Duration
1h 38m
Affected: IDV Sign (Onfido)
Timeline · 4 updates
  1. investigating Nov 25, 2025, 10:33 AM UTC

    We are currently investigating this issue.

  2. identified Nov 25, 2025, 12:07 PM UTC

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

  3. monitoring Nov 25, 2025, 12:10 PM UTC

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

  4. resolved Nov 25, 2025, 12:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Issues when signing with CSC Qualified verification

Detected by Pingoru
Nov 18, 2025, 12:08 PM UTC
Resolved
Nov 18, 2025, 12:37 PM UTC
Duration
29m
Affected: itsme sign (qualified signature)ZealiD Qualified
Timeline · 4 updates
  1. investigating Nov 18, 2025, 12:08 PM UTC

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

  2. identified Nov 18, 2025, 12:31 PM UTC

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

  3. monitoring Nov 18, 2025, 12:33 PM UTC

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

  4. resolved Nov 18, 2025, 12:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 11, 2025

issue with signing transactions

Detected by Pingoru
Nov 11, 2025, 02:40 PM UTC
Resolved
Nov 11, 2025, 03:12 PM UTC
Duration
31m
Affected: APIUI / ViewPortal
Timeline · 3 updates
  1. identified Nov 11, 2025, 02:40 PM UTC

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

  2. identified Nov 11, 2025, 02:51 PM UTC

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

  3. resolved Nov 11, 2025, 03:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 6, 2025

Issues with ID Proof web form

Detected by Pingoru
Nov 06, 2025, 09:20 AM UTC
Resolved
Nov 06, 2025, 09:53 AM UTC
Duration
32m
Affected: ID Proof
Timeline · 3 updates
  1. investigating Nov 06, 2025, 09:20 AM UTC

    We are currently experiencing an issue with our ID Proof web forms where not all text and options are displaying correctly Our provider is investigating the cause.

  2. monitoring Nov 06, 2025, 09:32 AM UTC

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

  3. resolved Nov 06, 2025, 09:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 21, 2025

Issues with ID Proof

Detected by Pingoru
Oct 21, 2025, 07:09 AM UTC
Resolved
Oct 21, 2025, 09:27 AM UTC
Duration
2h 17m
Affected: ID Proof
Timeline · 3 updates
  1. identified Oct 21, 2025, 07:09 AM UTC

    ID Proof validations are not resulting in transactions being created. A cause has been identified with a third party. They are working on a fix.

  2. monitoring Oct 21, 2025, 09:13 AM UTC

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

  3. resolved Oct 21, 2025, 09:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 3, 2025

Issues with creating and signing transactions

Detected by Pingoru
Sep 03, 2025, 11:23 AM UTC
Resolved
Sep 03, 2025, 01:32 PM UTC
Duration
2h 9m
Affected: APIUI / ViewPortalSignhost App
Timeline · 4 updates
  1. investigating Sep 03, 2025, 11:23 AM UTC

    We are experiencing issues with creating and signing transactions. We are investigating the issues.

  2. investigating Sep 03, 2025, 11:42 AM UTC

    We have placed the platform in maintenance as we continue our investigation.

  3. monitoring Sep 03, 2025, 12:05 PM UTC

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

  4. resolved Sep 03, 2025, 01:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2025

Issues in web portal

Detected by Pingoru
Mar 05, 2025, 03:32 PM UTC
Resolved
Mar 05, 2025, 06:46 PM UTC
Duration
3h 14m
Affected: Portal
Timeline · 3 updates
  1. investigating Mar 05, 2025, 03:32 PM UTC

    We are experiencing issues in the portal with slow loading times and errors. We are investigating the issues.

  2. monitoring Mar 05, 2025, 04:37 PM UTC

    We're monitoring the situation as the issues with our portal have decreased. We're still investigating what might have caused this.

  3. resolved Mar 05, 2025, 06:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 28, 2025

ID Proof Signhost app issues

Detected by Pingoru
Feb 28, 2025, 03:38 PM UTC
Resolved
Mar 04, 2025, 11:14 AM UTC
Duration
3d 19h
Affected: ID ProofSignhost App
Timeline · 3 updates
  1. identified Feb 28, 2025, 03:38 PM UTC

    We are investigating an issue with ID proof. It seems our last fix solved all issues on the web end, but for customers that are using the Signhost mobile app for ID proofing, there still remains an issue connecting to the IDV backend when trying to scan a document or make a selfie. It looks like we need to update our mobile IOS and Android apps to get this right, and are working with the app dev team and IOS/Android to get a new build fast tracked. We will keep you updated through this channel. NFC and webbrowser based IDV are not impacted.

  2. identified Mar 03, 2025, 09:31 AM UTC

    A new build is created and pushed to IOS/Android. We are awaiting approval from the OS vendors and will update this space when any news comes in.

  3. resolved Mar 04, 2025, 11:14 AM UTC

    A new app update was deployed and approved by IOS/Android this morning around 9:00. Downloading the latests app version restores ID Proof functionality for people that identify.

Read the full incident report →

Minor February 28, 2025

ID Proof - Issues with Camera method (OCR) and Signhost app validations

Detected by Pingoru
Feb 28, 2025, 10:32 AM UTC
Resolved
Feb 28, 2025, 03:30 PM UTC
Duration
4h 57m
Affected: ID ProofSignhost App
Timeline · 4 updates
  1. investigating Feb 28, 2025, 10:32 AM UTC

    We are experiencing issues with our identity verification product ID Proof. Users trying to validate their ID document using the camera method (OCR) or the Signhost app are not able to complete the process of scanning their document. We are investigating the issues. Document signing is not affected.

  2. identified Feb 28, 2025, 10:46 AM UTC

    The issue has been identified and we are working on a fix.

  3. identified Feb 28, 2025, 12:27 PM UTC

    We are continuing to work on a fix for this issue together with our partners.

  4. resolved Feb 28, 2025, 03:30 PM UTC

    After working with our IDV partner, we managed to solve the incident. ID Proof is back up again.

Read the full incident report →

Notice February 27, 2025

Issues creating and signing transactions

Detected by Pingoru
Feb 27, 2025, 02:19 PM UTC
Resolved
Feb 27, 2025, 02:56 PM UTC
Duration
37m
Affected: APIUI / ViewPortalAuth and login service
Timeline · 4 updates
  1. investigating Feb 27, 2025, 02:19 PM UTC

    We are experiencing issues on the platform. We have placed the platform in maintenance while we are investigating the issues.

  2. identified Feb 27, 2025, 02:27 PM UTC

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

  3. monitoring Feb 27, 2025, 02:43 PM UTC

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

  4. resolved Feb 27, 2025, 02:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 14, 2025

Issues with CSC Qualified verification method

Detected by Pingoru
Feb 14, 2025, 02:10 PM UTC
Resolved
Feb 14, 2025, 02:57 PM UTC
Duration
47m
Affected: itsme sign (qualified signature)ZealiD Qualified
Timeline · 3 updates
  1. investigating Feb 14, 2025, 02:10 PM UTC

    We are experiencing issues with the CSC Qualified verification method for Qualified Electronic Signatures. Signers get stuck in the process of signing and are not able to finish the signing process. We are investigating the issue.

  2. identified Feb 14, 2025, 02:48 PM UTC

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

  3. resolved Feb 14, 2025, 02:57 PM UTC

    This incident has been resolved.

Read the full incident report →