54 Idnow incidents · marzec 2025 — official updates, affected components, duration and resolution details.
Obecnie doświadczamy degradacji wydajności i aktywnie badamy tę kwestię. Nasz zespół pracuje nad zidentyfikowaniem przyczyny i wdrożeniem rozwiązania. Klienci korzystający z eSign z IDnow QTSP są dotknięci.
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
We are currently experiencing a service disruption on our advanced signature service Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.
We are continuing to work on a fix for this issue.
The team is fixing the issue, the service should be restored within the next hour.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
* .identity.tm domeny (w tym dedykowana strona statusu) nie są rozwiązywane przez DNS, co powoduje brak dostępu do systemów.
Rozdzielczość DNS znów działa. Zbieramy dowody do śledztwa.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie doświadczamy zakłóceń w obsłudze robota testowego. Podczas uruchamiania robota testowego ze scenariuszem HAPPYPATH, jeśli istnieje niezgodność danych między danymi początkowymi a późniejszymi danymi przekazanymi do TestRobot z HAPPIPATH, rezultatem uruchomienia będzie SUCCESS _ DATA _ CHANGED (jak w scenariuszu CHANGEAL.) W efekcie oznacza to, że -HAPPYPATH nie jest obecnie w stanie wygenerować wyniku SUCCESS, jeśli polecenie robota jest napisane na imię lub nazwisko. Inne scenariusze robota działają prawidłowo. Dotyczy to tylko robota VideoIdent i eSign TEST. Produkty AutoIdent i Signature nie mają wpływu. Produkcja nie jest naruszona.
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie doświadczamy zakłóceń w obsłudze. Nasze zespoły inżynieryjne aktywnie badają tę kwestię i pracują nad jak najszybszym przywróceniem pełnej funkcjonalności. Doceniamy Państwa cierpliwość i zapewnimy terminowe aktualizacje aż do pełnego przywrócenia usługi.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Zidentyfikowaliśmy problem techniczny w naszym interfejsie czynników VideoIdent, który powoduje wpływ na wydajność. Ta kwestia doprowadziła do zmniejszenia dostępności agentów wideo dla użytkowników końcowych na naszych usługach VideoIdent i eSign. Namierzono go i monitorujemy sytuację. AutoIdent, AutoIdent QES, eID i Signature nie zostały naruszone.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a performance degradation and are actively investigating the issue. Our team is working to identify the root cause and implement a solution. Customers using eSign with IDnow QTSP are affected.
This incident has been resolved.
We are currently experiencing a service disruption on PVID. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently experiencing a service disruption. Our DevOps team is working to identify the root cause and implement a solution. eSigning users who use the Namirial TSP are affected. We will keep you updated with any new developments.
This incident has been resolved.
We are currently experiencing a service disruption on Check'n'Sign service. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
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.
We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
For the last couple of hours, we're experiencing a performance degradation and are currently looking into the issue We will provide regular updates on the issue.
A 3rd party provider API is experiencing an outage, impacting the performance of Check'n'Sign. We are considering options to workaround the issue.
A fix is being implemented.
A fix has been implemented and we are monitoring the results.
The 3rd party provider API is up and running again so we are removing the workaround.
This incident has been resolved.
We're experiencing an performance degradation and are currently looking into the issue. We will provide regular updates on the issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
The team identified the root cause. We are investigating it further to restore the services as soon as possible.
We are still working on restoring the service. It may take another couple of hours.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
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.
We are currently experiencing a service disruption. Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a service disruption. Our DevOps team is working to identify the root cause and implement a solution. We will send an additional update in 60 minutes.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
The services are gradually getting back online.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a service disruption. Our engineering teams are actively investigating the issue and working to restore full functionality as quickly as possible. We appreciate your patience and will provide timely updates until the service is fully restored.
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.
We are currently experiencing a service disruption on NG. Our DevOps team is working to identify the root cause and implement a solution. *detail impact* users may be affected. We will send an additional update in 60 minutes.
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.