Idnow driftsforstyrrelser

1. 16. august 2026 kl. 18.47 UTCinvestigating

   Vi oplever i øjeblikket en forringelse af ydeevnen og undersøger aktivt spørgsmålet. Vores team arbejder på at identificere årsagen og gennemføre en løsning. Kunder der bruger eSign med IDnow QTSP påvirkes.

2. 16. august 2026 kl. 19.59 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 16. august 2026 kl. 20.10 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. august 2026 kl. 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 kl. 01.57 UTCidentified

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

3. 10. august 2026 kl. 07.59 UTCidentified

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

4. 10. august 2026 kl. 09.08 UTCmonitoring

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

5. 10. august 2026 kl. 10.10 UTCresolved

   This incident has been resolved.

1. 27. juli 2026 kl. 09.17 UTCinvestigating

   * .identity.tm domæner (herunder dedikeret status side) ikke løses af DNS, hvilket resulterer i manglende adgang til systemerne.

2. 27. juli 2026 kl. 09.34 UTCmonitoring

   DNS-opløsning synes at fungere igen. Vi indsamler beviser til efterforskning.

3. 27. juli 2026 kl. 09.46 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. juli 2026 kl. 09.31 UTCinvestigating

   Vi oplever i øjeblikket en serviceforstyrrelse for testrobotten. Under kørsel af testrobotten med HAPPYPATH scenario, hvis der er en datauoverensstemmelse mellem de oprindelige data og de senere indsendte data til TestRobot med HAPPYPATH, vil resultatet af løbet være SUCCESS _ DATA _ Changed (som i ChangeALL scenario.) I virkeligheden betyder dette -HAPPYPATH er i øjeblikket ikke i stand til at producere en SUCCESS resultat, hvis robotten kommando er skrevet til det første eller efternavn. Andre robot scenarier fungerer korrekt. Dette påvirker kun VideoIdent og eSign TEST robot. AutoIdent-produkterne og InstantSign påvirkes ikke. Produktionen påvirkes ikke.

2. 5. august 2026 kl. 12.42 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 18. august 2026 kl. 13.55 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. juli 2026 kl. 14.25 UTCinvestigating

   Vi oplever i øjeblikket en serviceforstyrrelse. Vores ingeniørhold undersøger aktivt problemet og arbejder på at genoprette fuld funktionalitet så hurtigt som muligt. Vi sætter pris på din tålmodighed og vil give rettidige opdateringer, indtil tjenesten er fuldt restaureret.

2. 20. juli 2026 kl. 15.12 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. juli 2026 kl. 10.06 UTCmonitoring

   Vi identificerede et teknisk problem i vores VideoIdent agent interface, som forårsager en ydeevne indvirkning. Problemet førte til en reduceret tilgængelighed af videoagenter for slutbrugerne på vores VideoIdent og eSign-tjenester. Et fix blev udsendt, og vi overvåger situationen. AutoIdent, AutoIdent QES, eID og InstantSign blev ikke påvirket.

2. 3. juli 2026 kl. 12.12 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juni 2026 kl. 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 kl. 07.35 UTCmonitoring

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

3. 10. juni 2026 kl. 07.42 UTCresolved

   This incident has been resolved.

1. 9. juni 2026 kl. 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 kl. 07.38 UTCresolved

   This incident has been resolved.

1. 5. maj 2026 kl. 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. maj 2026 kl. 09.43 UTCmonitoring

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

3. 5. maj 2026 kl. 10.00 UTCresolved

   This incident has been resolved.

1. 28. april 2026 kl. 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 kl. 08.08 UTCmonitoring

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

3. 28. april 2026 kl. 08.08 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28. april 2026 kl. 08.40 UTCresolved

   This incident has been resolved.

1. 21. april 2026 kl. 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 kl. 17.48 UTCresolved

   This incident has been resolved.

1. 3. april 2026 kl. 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 kl. 07.44 UTCidentified

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

3. 3. april 2026 kl. 07.50 UTCmonitoring

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

4. 3. april 2026 kl. 07.52 UTCresolved

   This incident has been resolved.

1. 25. marts 2026 kl. 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. marts 2026 kl. 15.39 UTCidentified

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

3. 25. marts 2026 kl. 15.46 UTCmonitoring

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

4. 25. marts 2026 kl. 15.57 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25. marts 2026 kl. 16.01 UTCresolved

   This incident has been resolved.

1. 18. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 13.41 UTCidentified

   A fix is being implemented.

4. 18. marts 2026 kl. 13.53 UTCmonitoring

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

5. 18. marts 2026 kl. 15.44 UTCmonitoring

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

6. 18. marts 2026 kl. 16.25 UTCresolved

   This incident has been resolved.

1. 13. marts 2026 kl. 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. marts 2026 kl. 15.15 UTCinvestigating

   We are continuing to investigate this issue.

3. 13. marts 2026 kl. 15.35 UTCidentified

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

4. 13. marts 2026 kl. 16.44 UTCidentified

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

5. 13. marts 2026 kl. 17.35 UTCidentified

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

6. 13. marts 2026 kl. 17.47 UTCmonitoring

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

7. 13. marts 2026 kl. 18.04 UTCresolved

   This incident has been resolved.

1. 2. februar 2026 kl. 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 kl. 15.40 UTCidentified

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

3. 2. februar 2026 kl. 15.42 UTCmonitoring

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

4. 2. februar 2026 kl. 16.24 UTCresolved

   This incident has been resolved.

1. 29. januar 2026 kl. 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 kl. 15.13 UTCinvestigating

   We are continuing to investigate this issue.

3. 29. januar 2026 kl. 15.58 UTCmonitoring

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

4. 29. januar 2026 kl. 15.59 UTCresolved

   This incident has been resolved.

1. 29. januar 2026 kl. 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 kl. 07.27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29. januar 2026 kl. 08.12 UTCidentified

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

4. 29. januar 2026 kl. 08.29 UTCidentified

   The services are gradually getting back online.

5. 29. januar 2026 kl. 08.31 UTCidentified

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

6. 29. januar 2026 kl. 09.26 UTCmonitoring

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

7. 29. januar 2026 kl. 09.47 UTCresolved

   This incident has been resolved.

1. 11. januar 2026 kl. 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 kl. 10.39 UTCidentified

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

3. 11. januar 2026 kl. 11.11 UTCmonitoring

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

4. 11. januar 2026 kl. 18.16 UTCresolved

   This incident has been resolved.

1. 5. januar 2026 kl. 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 kl. 11.28 UTCidentified

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

3. 5. januar 2026 kl. 11.46 UTCmonitoring

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

4. 5. januar 2026 kl. 13.06 UTCresolved

   This incident has been resolved.