Is Evidos down?
Last checked 5m agoNo incidents right now.
Evidos is operational right now. Last checked 5m ago; the most recent incident resolved 6d ago.
Real-time Evidos status, recent outages, and incident history — pulled directly from Evidos's official status page at https://status.signhost.com every 5 minutes. Pingoru tracks 23 Evidos services and has captured 5 incidents in the last 90 days (99.73% uptime). Get email, Slack, Discord, or webhook alerts the moment Evidos reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Mail service
Timeline · 5 updates
- investigating · Sep 04, 2026, 10:12 AM UTC
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.
- investigating · Sep 04, 2026, 12:49 PM UTC
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
- identified · Sep 04, 2026, 02:28 PM UTC
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.
- resolved · Sep 07, 2026, 06:18 AM UTC
The issue affecting email notification delivery has been resolved. Email notifications are now being delivered as expected, with no further delays observed.
- postmortem · Sep 07, 2026, 08:29 AM UTC
### 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.
Latest: ### What happened? On September 4th 2026, some Signhost email notifications, including signing invitations and status updates, were delivered later than usual. During this period, …
-
- itsme Identification
Timeline · 4 updates
- investigating · Jul 23, 2026, 12:49 PM UTC
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.
- identified · Jul 23, 2026, 01:41 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Jul 23, 2026, 01:57 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jul 23, 2026, 02:18 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- iDINiDEAL
Timeline · 4 updates
- investigating · Jul 17, 2026, 02:25 PM UTC
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.
- identified · Jul 17, 2026, 02:44 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Jul 17, 2026, 02:47 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jul 17, 2026, 03:19 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- itsme Identification
Timeline · 3 updates
- investigating · Jun 18, 2026, 07:16 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.
- monitoring · Jun 18, 2026, 09:02 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jun 18, 2026, 09:16 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- ID ProofWebforms
Timeline · 3 updates
- investigating · Jun 16, 2026, 01:27 PM UTC
We are currently experiencing problems with ID Proof. We are investigating this issue. ID Proof is unable to be used momentarily.
- monitoring · Jun 16, 2026, 01:55 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jun 16, 2026, 02:09 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Email Delivery Delays ResolvedStarted Sep 04, 2026, 10:12 AM UTC · Resolved Sep 07, 2026, 06:18 AM UTC · 2d 20h
- Started Jul 23, 2026, 12:49 PM UTC · Resolved Jul 23, 2026, 02:18 PM UTC · 1h 29m
- Started Jul 17, 2026, 02:25 PM UTC · Resolved Jul 17, 2026, 03:19 PM UTC · 53m
- Started Jun 18, 2026, 07:16 AM UTC · Resolved Jun 18, 2026, 09:16 AM UTC · 2h
- ID Proof - Outage ResolvedStarted Jun 16, 2026, 01:27 PM UTC · Resolved Jun 16, 2026, 02:09 PM UTC · 41m