メール配信の問題
Outage重大なインシデント
影響を受けたコンポーネント
APIPortal
- investigating
現在、この問題を調査中です.
- monitoring
修正を実装し、結果を監視しています.
- resolved
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
54 Evidos incidents · 2024年7月 — official updates, affected components, duration and resolution details.
現在、この問題を調査中です.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
現在、プラットフォームから送信されたメールの配信に遅れが生じている問題が発生しています。 その結果、メールは受取人に連絡する予定よりも時間がかかることがあります.
Signhost が送信したメール通知に影響する遅延を調査しています。 Signhost プラットフォームは、完全に運用され、文書処理は影響を受けません。 問題は現在、電子メール配信に限定されています, これは、後で通常のよりも受信者に到達通知をもたらす可能性があります. 当社は、Eメールサービスプロバイダと協力して、問題を迅速に解決します
当社は、Signhostから送信されたメール通知に影響を及ぼす遅延が、より広範なMicrosoft 365 Exchange Onlineインシデントに関連していることを認識しました。 現時点では、Signhostプラットフォームは完全に運用し、文書処理、署名、取引処理は影響を受けません。 影響は、メール通知が通常よりも遅く配信されるのに限られます。 受信通知の遅延が発生する可能性があります。 今後もメールサービス提供者と密接に状況を監視してまいります。 月曜日の朝は、次の更新を行います.
メール通知配信に影響を及ぼす問題が解決しました。 メールでの通知が期待通りに配信され、さらに遅延が発生しません.
### 何が起こったのか? 9月4日2026日には、招待状やステータスの更新など、いくつかのSignhostメール通知が、後で通常よりも配信されました。 この期間中、Signhostプラットフォームは完全に稼働しています。 ドキュメント署名、トランザクション処理、API の機能が影響されなかった。 ### 問題の原因は? 当社の調査では、メール処理や配信に影響を及ぼす広範なMicrosoft 365 Exchange Onlineインシデントによる遅延が発生したことを確認しました。 Microsoftは、取引所のオンラインインフラに影響を与える遅延と「サーバーの忙しい」エラーを報告しました。 Signhost の外部から発信された問題は、Signhost アプリケーション、インフラ、サービスに関連していませんでした。 Signhost が Microsoft Exchange Online を使用してメール通知を送信することが重要です。 弊社のメール配信は、当社のメールサービスプロバイダであるSparkPostを通じて行います。 Microsoftインシデントに関する詳細情報は、こちらで確認できます。[Exchange Online outage はメールの遅延とサーバーの忙しいエラーを引き起こします](https://www.bleepingcomputer.com/news/microsoft/exchange-online-outage-causes-email-delays-server-busy-errors/) ### 何をしたの? 私たちは、状況を監視し、根本原因を検証するために、当社の電子メールサービスプロバイダと密接に連携しました。 インシデントを通じて、Signhostサービスを継続的に監視し、コアプラットフォームの機能性が影響を受けていないことを確認しました。 Microsoft が Exchange Online のインシデントを解決したら、メール配信が正常に戻りました。 今後、メール通知が期待どおりに配信されていることを検証しました。 お客様からの書面、取引、顧客データが影響されず、お客様の一部にアクションが要求されないことをお詫び申し上げます.
公式のインシデント更新を自動翻訳しています。
現時点では、Signhost内での、その確認方法(AES)に影響を及ぼす問題が発生しています。 その結果、この検証方法を使用する取引は、この時点で完了できません。 本件を調査しています.
問題が特定され、修正が実装されています.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
現在、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.