电子邮件发送问题
Outage重大事件
受影响的组件
APIPortal
- investigating
我们目前正在调查这一问题.
- monitoring
一项措施已经执行,我们正在监测结果.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
54 Evidos incidents · 2024年7月 — official updates, affected components, duration and resolution details.
我们目前正在调查这一问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在经历一个问题,它正在造成从我们的平台发送电子邮件的延迟。 因此,电子邮件可能要花费比预期的时间才能到达收件人.
我们正在调查Signhost发送的电子邮件通知的延误。 Signhost平台仍然充分运作,文件处理没有受到影响。 这个问题目前仅限于电子邮件发送,可能导致通知送达给接收者的时间比通常要晚. 我们正在与我们的电子邮件服务供应商合作,以尽快解决这一问题
我们确认,Signhost发送电子邮件通知的延误与更广泛的Microsoft 365 Exchange Online事件有关。 此时,Signhost平台仍然全面运行,文件处理,签名,交易处理不受影响. 影响仅限于电子邮件通知的发送比通常晚。 收款人可能在收到通知方面出现延误。 我们正在继续与我们的电子邮件服务提供方一起密切监测局势。 我们将在星期一上午提供下一次最新情况.
影响电子邮件通知发送的问题已经解决。 电子邮件通知现在按预期发送,不再出现任何延误.
发生了什么事? 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服务,并证实核心平台功能没有受到影响。 微软解决了"交易所在线"事件后,电子邮件发送恢复正常. 我们已核实,电子邮件通知现已按预期发送,不再出现任何延误。 我们向客户保证,没有任何文件、交易或客户数据受到影响,你无需采取任何行动.
自动翻译自官方事件更新。
我们目前正在经历一个影响Signhost内部的识别方法的问题。 因此,目前无法完成使用这种核查方法的交易。 我们正在调查这个问题.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在经历一个影响Signhost内部iDIN和iDEAL服务的问题. 因此,使用这些方法的交易此时无法完成. 我们的小组正在积极调查这一问题并努力尽快恢复正常服务。 一旦获得更多信息,我们将提供进一步的最新资料.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
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.