Istoricul incidentelor Idnow

1. 16 august 2026 la 18:47 UTCinvestigating

   În prezent ne confruntăm cu o degradare a performanței și investigăm în mod activ această problemă. Echipa noastră lucrează pentru identificarea cauzei profunde și implementarea unei soluții. Clienţii care utilizează eSign cu IDnow QTSP sunt afectaţi.

2. 16 august 2026 la 19:59 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 16 august 2026 la 20:10 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 9 august 2026 la 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 la 01:57 UTCidentified

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

3. 10 august 2026 la 07:59 UTCidentified

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

4. 10 august 2026 la 09:08 UTCmonitoring

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

5. 10 august 2026 la 10:10 UTCresolved

   This incident has been resolved.

1. 27 iulie 2026 la 09:17 UTCinvestigating

   *.identity.tm domenii (inclusiv pagina de stare dedicată) nu sunt rezolvate de către DNS, ceea ce duce la lipsa accesului la sisteme.

2. 27 iulie 2026 la 09:34 UTCmonitoring

   Rezoluţia DNS pare să funcţioneze din nou. Adunăm probe pentru investigaţie.

3. 27 iulie 2026 la 09:46 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 09:31 UTCinvestigating

   În prezent experimentăm o întrerupere a serviciului pentru robotul testat. În timp ce rulează robotul de testare cu scenariul HAPPYPATH, dacă există o incoerență de date între datele inițiale și datele transmise ulterior către TestRobot cu HAPPYPATH, rezultatul run-ului va fi SUCCESS DATA CHANGED (ca în scenariul ChangeALL). De fapt, aceasta înseamnă -HAPPYPATH nu este în prezent capabil să producă un rezultat SUCCES dacă comanda robotului este scrisă primului sau ultimului nume. Alte scenarii robot funcționează în mod corespunzător. Acest lucru afectează doar robotul de testare VideoIdent și eSign. Produsele AutoIdent și InstantSign nu sunt afectate. Producția nu este afectată.

2. 5 august 2026 la 12:42 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 18 august 2026 la 13:55 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 20 iulie 2026 la 14:25 UTCinvestigating

   Avem în prezent o întrerupere a serviciilor. Echipele noastre de inginerie investighează în mod activ problema și lucrează pentru a restabili funcționalitatea completă cât mai repede posibil. Apreciem răbdarea dumneavoastră și vă vom oferi actualizări în timp util până când serviciul este complet restaurat.

2. 20 iulie 2026 la 15:12 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 2 iulie 2026 la 10:06 UTCmonitoring

   Am identificat o problemă tehnică în interfața noastră de agent VideoIdent care cauzează un impact de performanță. Problema a dus la o disponibilitate redusă de agenți video pentru utilizatorii finali pe serviciile noastre VideoIdent și eSign. A fost implementat un fix şi monitorizăm situaţia. Autoident, Autoident QES, EID și InstantSign nu au fost afectate.

2. 3 iulie 2026 la 12:12 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iunie 2026 la 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 iunie 2026 la 07:35 UTCmonitoring

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

3. 10 iunie 2026 la 07:42 UTCresolved

   This incident has been resolved.

1. 9 iunie 2026 la 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 iunie 2026 la 07:38 UTCresolved

   This incident has been resolved.

1. 5 mai 2026 la 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 la 09:43 UTCmonitoring

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

3. 5 mai 2026 la 10:00 UTCresolved

   This incident has been resolved.

1. 28 aprilie 2026 la 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 aprilie 2026 la 08:08 UTCmonitoring

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

3. 28 aprilie 2026 la 08:08 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28 aprilie 2026 la 08:40 UTCresolved

   This incident has been resolved.

1. 21 aprilie 2026 la 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 aprilie 2026 la 17:48 UTCresolved

   This incident has been resolved.

1. 3 aprilie 2026 la 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 aprilie 2026 la 07:44 UTCidentified

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

3. 3 aprilie 2026 la 07:50 UTCmonitoring

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

4. 3 aprilie 2026 la 07:52 UTCresolved

   This incident has been resolved.

1. 25 martie 2026 la 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 martie 2026 la 15:39 UTCidentified

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

3. 25 martie 2026 la 15:46 UTCmonitoring

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

4. 25 martie 2026 la 15:57 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 martie 2026 la 16:01 UTCresolved

   This incident has been resolved.

1. 18 martie 2026 la 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 martie 2026 la 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 martie 2026 la 13:41 UTCidentified

   A fix is being implemented.

4. 18 martie 2026 la 13:53 UTCmonitoring

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

5. 18 martie 2026 la 15:44 UTCmonitoring

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

6. 18 martie 2026 la 16:25 UTCresolved

   This incident has been resolved.

1. 13 martie 2026 la 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 martie 2026 la 15:15 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 martie 2026 la 15:35 UTCidentified

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

4. 13 martie 2026 la 16:44 UTCidentified

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

5. 13 martie 2026 la 17:35 UTCidentified

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

6. 13 martie 2026 la 17:47 UTCmonitoring

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

7. 13 martie 2026 la 18:04 UTCresolved

   This incident has been resolved.

1. 2 februarie 2026 la 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 februarie 2026 la 15:40 UTCidentified

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

3. 2 februarie 2026 la 15:42 UTCmonitoring

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

4. 2 februarie 2026 la 16:24 UTCresolved

   This incident has been resolved.

1. 29 ianuarie 2026 la 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 ianuarie 2026 la 15:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 ianuarie 2026 la 15:58 UTCmonitoring

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

4. 29 ianuarie 2026 la 15:59 UTCresolved

   This incident has been resolved.

1. 29 ianuarie 2026 la 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 ianuarie 2026 la 07:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 ianuarie 2026 la 08:12 UTCidentified

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

4. 29 ianuarie 2026 la 08:29 UTCidentified

   The services are gradually getting back online.

5. 29 ianuarie 2026 la 08:31 UTCidentified

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

6. 29 ianuarie 2026 la 09:26 UTCmonitoring

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

7. 29 ianuarie 2026 la 09:47 UTCresolved

   This incident has been resolved.

1. 11 ianuarie 2026 la 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 ianuarie 2026 la 10:39 UTCidentified

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

3. 11 ianuarie 2026 la 11:11 UTCmonitoring

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

4. 11 ianuarie 2026 la 18:16 UTCresolved

   This incident has been resolved.

1. 5 ianuarie 2026 la 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 ianuarie 2026 la 11:28 UTCidentified

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

3. 5 ianuarie 2026 la 11:46 UTCmonitoring

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

4. 5 ianuarie 2026 la 13:06 UTCresolved

   This incident has been resolved.