Störungsverlauf von Idnow

1. 16. August 2026 um 18:47 UTCinvestigating

   Wir erleben derzeit eine Leistungsminderung und untersuchen das Problem aktiv. Unser Team arbeitet daran, die Ursache zu identifizieren und eine Lösung zu implementieren. Kunden, die eSign mit IDnow QTSP nutzen, sind betroffen.

2. 16. August 2026 um 19:59 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 16. August 2026 um 20:10 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 9. August 2026 um 01:16 UTCidentified

   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.

2. 9. August 2026 um 01:57 UTCidentified

   We are continuing to work on a fix for this issue.

3. 10. August 2026 um 07:59 UTCidentified

   The team is fixing the issue, the service should be restored within the next hour.

4. 10. August 2026 um 09:08 UTCmonitoring

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

5. 10. August 2026 um 10:10 UTCresolved

   This incident has been resolved.

1. 27. Juli 2026 um 09:17 UTCinvestigating

   *.identity.tm-Domains (einschließlich dedizierter Statusseite) werden vom DNS nicht aufgelöst, was zu einem fehlenden Zugriff auf die Systeme führt.

2. 27. Juli 2026 um 09:34 UTCmonitoring

   Die DNS-Auflösung scheint wieder zu funktionieren. Wir sammeln Beweise für Untersuchungen.

3. 27. Juli 2026 um 09:46 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 09:31 UTCinvestigating

   Wir erleben derzeit eine Servicestörung für den Testroboter. Wenn beim Betrieb des Testroboters mit HAPPYPATH-Szenario eine Dateninkonsistenz zwischen den Ausgangsdaten und den später an den TestRobot mit HAPPYPATH übermittelten Daten besteht, wird das Ergebnis des Laufs SUCCESS DATA CHANGED (wie im CHANGEALL-Szenario) sein. In der Tat bedeutet dies -HAPPYPATH ist derzeit nicht in der Lage, ein ERFOLGUNGSergebnis zu erzeugen, wenn der Roboterbefehl auf den Vor- oder Nachnamen geschrieben wird. Andere Roboterszenarien funktionieren richtig. Dies betrifft nur VideoIdent und eSign TEST Roboter. Die AutoIdent-Produkte und InstantSign sind nicht betroffen. Die Produktion ist nicht betroffen.

2. 5. August 2026 um 12:42 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 18. August 2026 um 13:55 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Juli 2026 um 14:25 UTCinvestigating

   Wir erleben derzeit eine Service-Störung. Unsere Engineering-Teams untersuchen das Problem aktiv und arbeiten daran, die volle Funktionalität so schnell wie möglich wiederherzustellen. Wir schätzen Ihre Geduld und werden zeitnahe Updates bereitstellen, bis der Service vollständig wiederhergestellt ist.

2. 20. Juli 2026 um 15:12 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juli 2026 um 10:06 UTCmonitoring

   Wir haben ein technisches Problem in unserer VideoIdent-Agent-Schnittstelle festgestellt, das Auswirkungen auf die Leistung hat. Das Problem führte zu einer reduzierten Verfügbarkeit von Videoagenten für Endbenutzer auf unseren VideoIdent- und eSign-Diensten. Ein Fix wurde bereitgestellt und wir überwachen die Situation. AutoIdent, AutoIdent QES, eID und InstantSign waren nicht betroffen.

2. 3. Juli 2026 um 12:12 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. Juni 2026 um 07:24 UTCinvestigating

   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.

2. 10. Juni 2026 um 07:35 UTCmonitoring

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

3. 10. Juni 2026 um 07:42 UTCresolved

   This incident has been resolved.

1. 9. Juni 2026 um 14:07 UTCinvestigating

   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.

2. 10. Juni 2026 um 07:38 UTCresolved

   This incident has been resolved.

1. 5. Mai 2026 um 09:32 UTCinvestigating

   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.

2. 5. Mai 2026 um 09:43 UTCmonitoring

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

3. 5. Mai 2026 um 10:00 UTCresolved

   This incident has been resolved.

1. 28. April 2026 um 07:44 UTCinvestigating

   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.

2. 28. April 2026 um 08:08 UTCmonitoring

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

3. 28. April 2026 um 08:08 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28. April 2026 um 08:40 UTCresolved

   This incident has been resolved.

1. 21. April 2026 um 15:59 UTCinvestigating

   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.

2. 21. April 2026 um 17:48 UTCresolved

   This incident has been resolved.

1. 3. April 2026 um 07:29 UTCinvestigating

   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.

2. 3. April 2026 um 07:44 UTCidentified

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

3. 3. April 2026 um 07:50 UTCmonitoring

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

4. 3. April 2026 um 07:52 UTCresolved

   This incident has been resolved.

1. 25. März 2026 um 15:27 UTCinvestigating

   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.

2. 25. März 2026 um 15:39 UTCidentified

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

3. 25. März 2026 um 15:46 UTCmonitoring

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

4. 25. März 2026 um 15:57 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25. März 2026 um 16:01 UTCresolved

   This incident has been resolved.

1. 18. März 2026 um 12:52 UTCinvestigating

   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.

2. 18. März 2026 um 12:58 UTCidentified

   A 3rd party provider API is experiencing an outage, impacting the performance of Check'n'Sign. We are considering options to workaround the issue.

3. 18. März 2026 um 13:41 UTCidentified

   A fix is being implemented.

4. 18. März 2026 um 13:53 UTCmonitoring

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

5. 18. März 2026 um 15:44 UTCmonitoring

   The 3rd party provider API is up and running again so we are removing the workaround.

6. 18. März 2026 um 16:25 UTCresolved

   This incident has been resolved.

1. 13. März 2026 um 14:47 UTCinvestigating

   We're experiencing an performance degradation and are currently looking into the issue. We will provide regular updates on the issue.

2. 13. März 2026 um 15:15 UTCinvestigating

   We are continuing to investigate this issue.

3. 13. März 2026 um 15:35 UTCidentified

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

4. 13. März 2026 um 16:44 UTCidentified

   The team identified the root cause. We are investigating it further to restore the services as soon as possible.

5. 13. März 2026 um 17:35 UTCidentified

   We are still working on restoring the service. It may take another couple of hours.

6. 13. März 2026 um 17:47 UTCmonitoring

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

7. 13. März 2026 um 18:04 UTCresolved

   This incident has been resolved.

1. 2. Februar 2026 um 15:08 UTCinvestigating

   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.

2. 2. Februar 2026 um 15:40 UTCidentified

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

3. 2. Februar 2026 um 15:42 UTCmonitoring

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

4. 2. Februar 2026 um 16:24 UTCresolved

   This incident has been resolved.

1. 29. Januar 2026 um 15:13 UTCinvestigating

   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.

2. 29. Januar 2026 um 15:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 29. Januar 2026 um 15:58 UTCmonitoring

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

4. 29. Januar 2026 um 15:59 UTCresolved

   This incident has been resolved.

1. 29. Januar 2026 um 07:26 UTCinvestigating

   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.

2. 29. Januar 2026 um 07:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29. Januar 2026 um 08:12 UTCidentified

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

4. 29. Januar 2026 um 08:29 UTCidentified

   The services are gradually getting back online.

5. 29. Januar 2026 um 08:31 UTCidentified

   We are continuing to work on a fix for this issue.

6. 29. Januar 2026 um 09:26 UTCmonitoring

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

7. 29. Januar 2026 um 09:47 UTCresolved

   This incident has been resolved.

1. 11. Januar 2026 um 10:04 UTCinvestigating

   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.

2. 11. Januar 2026 um 10:39 UTCidentified

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

3. 11. Januar 2026 um 11:11 UTCmonitoring

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

4. 11. Januar 2026 um 18:16 UTCresolved

   This incident has been resolved.

1. 5. Januar 2026 um 11:15 UTCinvestigating

   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.

2. 5. Januar 2026 um 11:28 UTCidentified

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

3. 5. Januar 2026 um 11:46 UTCmonitoring

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

4. 5. Januar 2026 um 13:06 UTCresolved

   This incident has been resolved.