Evidos 中断历史

1. 2026年9月4日 UTC 10:12investigating

   我们目前正在经历一个问题,它正在造成从我们的平台发送电子邮件的延迟。 因此,电子邮件可能要花费比预期的时间才能到达收件人.

2. 2026年9月4日 UTC 12:49investigating

   我们正在调查Signhost发送的电子邮件通知的延误。 Signhost平台仍然充分运作,文件处理没有受到影响。 这个问题目前仅限于电子邮件发送,可能导致通知送达给接收者的时间比通常要晚. 我们正在与我们的电子邮件服务供应商合作,以尽快解决这一问题

3. 2026年9月4日 UTC 14:28identified

   我们确认,Signhost发送电子邮件通知的延误与更广泛的Microsoft 365 Exchange Online事件有关。 此时,Signhost平台仍然全面运行,文件处理,签名,交易处理不受影响. 影响仅限于电子邮件通知的发送比通常晚。 收款人可能在收到通知方面出现延误。 我们正在继续与我们的电子邮件服务提供方一起密切监测局势。 我们将在星期一上午提供下一次最新情况.

4. 2026年9月7日 UTC 06:18resolved

   影响电子邮件通知发送的问题已经解决。 电子邮件通知现在按预期发送,不再出现任何延误.

5. 2026年9月7日 UTC 08:29postmortem

   发生了什么事? 2026年9月4日,一些Signhost电子邮件通知,包括签名邀请和状态更新,比平时晚发. 在此期间,Signhost平台仍然全面运作. 文件签名、交易处理和API功能没有受到影响。 问题是什么引起的? 我们的调查证实,延误是由于Microsoft 365 Exchange Online的一次更广泛的事件影响了电子邮件的处理和发送。 微软报告了影响交易所在线基础设施的延误和“服务器繁忙”错误。 这个问题起源于Signhost之外,与Signhost应用,基础设施或服务无关. 需要注意的是,Signhost没有使用Microsoft Exchange Online发送电子邮件通知. 我们的电子邮件发送是通过我们的电子邮件服务供应商SparkPost处理的. 有关微软事件的更多信息,可在此查阅:[Exchange Online出局导致电子邮件延迟和服务器繁忙出错](https://www.bleeping copy.com/news/microsoft/exchange-online-outage-causes-email-delays-server-busy-errors/). 我们做了什么? 我们与我们的电子邮件服务供应商密切合作,监测局势并核实其根源。 在整个事件中,我们不断监测Signhost服务,并证实核心平台功能没有受到影响。 微软解决了"交易所在线"事件后,电子邮件发送恢复正常. 我们已核实,电子邮件通知现已按预期发送,不再出现任何延误。 我们向客户保证,没有任何文件、交易或客户数据受到影响,你无需采取任何行动.

自动翻译自官方事件更新。

1. 2026年7月23日 UTC 12:49investigating

   我们目前正在经历一个影响Signhost内部的识别方法的问题。 因此,目前无法完成使用这种核查方法的交易。 我们正在调查这个问题.

2. 2026年7月23日 UTC 13:41identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年7月23日 UTC 13:57monitoring

   一项措施已经执行,我们正在监测结果.

4. 2026年7月23日 UTC 14:18resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月17日 UTC 14:25investigating

   我们目前正在经历一个影响Signhost内部iDIN和iDEAL服务的问题. 因此,使用这些方法的交易此时无法完成. 我们的小组正在积极调查这一问题并努力尽快恢复正常服务。 一旦获得更多信息,我们将提供进一步的最新资料.

2. 2026年7月17日 UTC 14:44identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年7月17日 UTC 14:47monitoring

   一项措施已经执行,我们正在监测结果.

4. 2026年7月17日 UTC 15:19resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年6月18日 UTC 07:16investigating

   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. 2026年6月18日 UTC 09:02monitoring

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

3. 2026年6月18日 UTC 09:16resolved

   This incident has been resolved.

1. 2026年6月16日 UTC 13:27investigating

   We are currently experiencing problems with ID Proof. We are investigating this issue. ID Proof is unable to be used momentarily.

2. 2026年6月16日 UTC 13:55monitoring

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

3. 2026年6月16日 UTC 14:09resolved

   This incident has been resolved.

1. 2026年6月3日 UTC 04:55investigating

   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. 2026年6月3日 UTC 05:22identified

   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. 2026年6月3日 UTC 05:33monitoring

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

4. 2026年6月3日 UTC 05:49monitoring

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

5. 2026年6月3日 UTC 06:55resolved

   This incident has been resolved.

1. 2026年5月28日 UTC 07:06investigating

   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. 2026年5月28日 UTC 08:30investigating

   We are continuing to investigate this issue.

3. 2026年5月28日 UTC 10:19identified

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

4. 2026年5月28日 UTC 13:31investigating

   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. 2026年5月28日 UTC 14:13monitoring

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

6. 2026年5月28日 UTC 14:24resolved

   This incident has been resolved.

1. 2026年5月21日 UTC 23:05investigating

   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. 2026年5月21日 UTC 23:25identified

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

3. 2026年5月21日 UTC 23:28monitoring

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

4. 2026年5月21日 UTC 23:38resolved

   This incident has been resolved.

1. 2026年5月5日 UTC 07:07identified

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

2. 2026年5月5日 UTC 08:11monitoring

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

3. 2026年5月5日 UTC 08:42resolved

   Signhost QES is operational again.

1. 2026年4月21日 UTC 15:35identified

   Our provider is experiencing problems. Signhost QES cannot be used. The issue has been identified, the resolution is being handled.

2. 2026年4月22日 UTC 05:48resolved

   This incident has been resolved.

1. 2026年4月20日 UTC 07:52investigating

   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. 2026年4月20日 UTC 07:57monitoring

   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. 2026年4月20日 UTC 08:00resolved

   This incident has been resolved.

1. 2026年4月10日 UTC 13:29identified

   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. 2026年4月13日 UTC 10:35resolved

   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. 2026年3月23日 UTC 12:29investigating

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

2. 2026年3月23日 UTC 13:38monitoring

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

3. 2026年3月23日 UTC 14:01resolved

   The issues with DigiD have been resolved by Logius.

1. 2026年3月17日 UTC 09:34monitoring

   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. 2026年3月17日 UTC 09:59resolved

   This incident has been resolved.

1. 2026年2月12日 UTC 10:07investigating

   We are currently investigating this issue.

2. 2026年2月12日 UTC 10:44investigating

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

3. 2026年2月12日 UTC 11:58investigating

   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. 2026年2月12日 UTC 13:00investigating

   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. 2026年2月12日 UTC 14:05investigating

   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. 2026年2月12日 UTC 15:08monitoring

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

7. 2026年2月12日 UTC 15:21resolved

   This incident has been resolved.

8. 2026年2月18日 UTC 09:45postmortem

   ### 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. 2026年1月23日 UTC 09:21investigating

   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. 2026年1月23日 UTC 09:38monitoring

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

3. 2026年1月23日 UTC 10:09resolved

   This incident has been resolved.

1. 2025年12月10日 UTC 09:10investigating

   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. 2025年12月10日 UTC 09:33investigating

   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. 2025年12月10日 UTC 09:37monitoring

   itsme has implemented a solution, and the service has been restored. The situation is being closely monitored to ensure stability.

4. 2025年12月10日 UTC 09:50resolved

   This incident has been resolved.

1. 2025年11月25日 UTC 10:33investigating

   We are currently investigating this issue.

2. 2025年11月25日 UTC 12:07identified

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

3. 2025年11月25日 UTC 12:10monitoring

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

4. 2025年11月25日 UTC 12:12resolved

   This incident has been resolved.

1. 2025年11月18日 UTC 12:08investigating

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

2. 2025年11月18日 UTC 12:31identified

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

3. 2025年11月18日 UTC 12:33monitoring

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

4. 2025年11月18日 UTC 12:37resolved

   This incident has been resolved.

1. 2025年11月11日 UTC 14:40identified

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

2. 2025年11月11日 UTC 14:51identified

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

3. 2025年11月11日 UTC 15:12resolved

   This incident has been resolved.