54 Evidos incidents · lipiec 2024 — official updates, affected components, duration and resolution details.
Obecnie badamy tę kwestię.
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie doświadczamy problemu, który powoduje opóźnienia w dostarczaniu e-maili wysłanych z naszej platformy. W rezultacie, e-maile mogą trwać dłużej niż oczekiwano dotrzeć do odbiorców.
Prowadzimy śledztwo w sprawie opóźnień wpływających na powiadomienia e-mail wysyłane przez Sighost. Platforma Sighost pozostaje w pełni operacyjna i przetwarzanie dokumentów nie ma wpływu. Kwestia ta jest obecnie ograniczona do dostawy poczty elektronicznej, co może skutkować powiadomieniami do odbiorców później niż zwykle. Pracujemy z naszym dostawcą usług e-mail, aby rozwiązać problem jak najszybciej
Zidentyfikowaliśmy, że opóźnienia wpływające na powiadomienia e-mail wysyłane przez Sighost są związane z szerszym incydentem Microsoft 365 Exchange Online. W tym czasie platforma Sighost pozostaje w pełni operacyjna i nie ma wpływu na przetwarzanie, podpisywanie dokumentów i obsługę transakcji. Wpływ ogranicza się do powiadomień e-mail dostarczanych później niż zwykle. Odbiorcy mogą mieć opóźnienia w otrzymywaniu powiadomień. Nadal uważnie monitorujemy sytuację wraz z naszym dostawcą usług e-mail. W poniedziałek rano przekażemy kolejną aktualizację.
Kwestia dotycząca doręczenia powiadomienia e-mail została rozwiązana. Powiadomienia e-mail są obecnie dostarczane zgodnie z oczekiwaniami, bez dalszych opóźnień.
- Co się stało? W dniu 4 września 2026 r. niektóre powiadomienia e-mail Sighost, w tym podpisanie zaproszeń i aktualizacje statusu, zostały dostarczone później niż zwykle. W tym okresie platforma Signhost pozostała w pełni operacyjna. Podpisanie dokumentów, przetwarzanie transakcji i funkcjonalność API nie zostały naruszone. - Co spowodowało problem? Nasze dochodzenie potwierdziło, że opóźnienia zostały spowodowane przez szerszy incydent Microsoft 365 Exchange Online wpływający na przetwarzanie i dostarczanie poczty elektronicznej. Microsoft zgłosił opóźnienia i błędy "serwera zajęty" wpływające na infrastrukturę Exchange Online. Kwestia ta powstała poza Sighost i nie była związana z aplikacją, infrastrukturą lub usługami Sighost. Należy pamiętać, że Sighost nie używa Microsoft Exchange Online do wysyłania powiadomień e-mail. Nasza dostawa e-mail jest obsługiwana przez SparkPost, naszego dostawcy usług e-mail. Więcej informacji na temat incydentu Microsoft można znaleźć tutaj: [Exchange Online exage powoduje opóźnienia e-mail i błędy serwera zajęty] (https: / / www.bleepingcomputer.com / news / microsoft / exchange- online- over- causes-email- delays- server- busy- error /) - Co zrobiliśmy? Współpracowaliśmy ściśle z naszym dostawcą usług e-mail, aby monitorować sytuację i zweryfikować przyczynę. Podczas całego incydentu stale monitorowaliśmy usługi Sighost i potwierdziliśmy, że funkcjonalność platformy bazowej pozostaje nienaruszona. Po rozwiązaniu przez Microsoft incydentu Exchange Online, przesyłka e-mail wróciła do normy. Potwierdziliśmy, że powiadomienia e-mail są obecnie dostarczane zgodnie z oczekiwaniami, bez dalszych opóźnień. Chcielibyśmy zapewnić klientów, że nie wpłynęły na nie żadne dokumenty, transakcje ani dane klientów i nie są wymagane żadne działania z Twojej strony.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie mamy do czynienia z problemem wpływającym na metodę weryfikacji identyfikacji (AES) w ramach Signhost. W związku z tym transakcje, które stosują tę metodę weryfikacji, nie mogą być obecnie zrealizowane. Badamy tę kwestię.
Problem został zidentyfikowany i jest w trakcie wdrażania.
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie mamy do czynienia z problemem dotyczącym usług iDIN i iDEAL w ramach Signhost. W związku z tym transakcje, które wykorzystują te metody, nie mogą być obecnie zrealizowane. Nasz zespół aktywnie bada tę kwestię i pracuje nad jak najszybszym przywróceniem normalnej obsługi. Dostarczymy dalsze aktualizacje w miarę dostępności większej ilości informacji.
Problem został zidentyfikowany i jest w trakcie wdrażania.
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
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.
