Istoricul incidentelor Veriff

1. 3 septembrie 2026 la 22:18 UTCinvestigating

   Investigăm în prezent o posibilă performanță degradată prin deciziile de verificare. Echipa noastră lucrează la identificarea cauzei profunde a problemei care contribuie la deciziile întârziate și va oferi o actualizare în scurt timp.

2. 3 septembrie 2026 la 22:30 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 3 septembrie 2026 la 22:34 UTCidentified

   S-a identificat o problemă cu unul dintre furnizorii noştri terţi care cauzează o creştere a timpului de decizie de verificare automată în regiunile noastre americane.

4. 3 septembrie 2026 la 22:36 UTCmonitoring

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

5. 3 septembrie 2026 la 23:02 UTCmonitoring

   Continuăm să monitorizăm orice alte probleme.

6. 4 septembrie 2026 la 06:20 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 31 august 2026 la 20:46 UTCidentified

   Investigăm în prezent o posibilă performanță degradată prin deciziile de verificare. Echipa noastră lucrează la identificarea cauzei profunde a problemei care contribuie la deciziile întârziate și va oferi o actualizare în scurt timp.

2. 31 august 2026 la 21:18 UTCidentified

   Investigăm performanțele degradate care afectează Deciziile de verificare pentru un subset mic de verificări în regiunea SUA. Echipa noastră a identificat problema care contribuie şi a redirecţionat noul trafic către un mediu sănătos. Un număr limitat de verificări în curs de desfășurare în regiunea SUA ar putea experimenta decizii întârziate. Vom oferi o actualizare în scurt timp.

3. 31 august 2026 la 21:55 UTCmonitoring

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

4. 31 august 2026 la 22:08 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 26 august 2026 la 16:46 UTCresolved

   Între aproximativ 16:18 și 16:40 UTC la 26 Aug 2026, un subgrup de utilizatori finali ar fi putut întâmpina erori intermitente sau încetinire în timpul completării fluxului de verificare. Echipa noastră a identificat problema și a aplicat un fix, după care serviciul recuperat. Fluxul de verificare funcționează în mod normal. Continuăm să monitorizăm și vom investiga pentru a preveni recurența.

Traducere automată din actualizarea oficială a incidentului.

1. 6 august 2026 la 18:00 UTCinvestigating

   We are currently investigating a potential issue with our services. Our team is investigating to determine if everything is working as expected. We will provide an update on our findings as soon as possible.

2. 6 august 2026 la 18:09 UTCidentified

   We have identified an issue affecting one of our third-party providers and are working closely with them to resolve it as quickly as possible. Because the issue is intermittent, some sessions may experience higher-than-normal decision latency, while others may not be affected. We will continue to provide updates as more information becomes available.

3. 6 august 2026 la 19:24 UTCmonitoring

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

4. 6 august 2026 la 19:33 UTCresolved

   This incident has been resolved.

1. 28 iulie 2026 la 14:00 UTCinvestigating

   Monitorizăm în mod activ o problemă care cauzează unele sesiuni automate să experimenteze momente de decizie mai mari decât de obicei. Această problemă nu afectează toate sesiunile, astfel încât poate fi sau nu pot fi afectate. Echipa noastră investighează cauza principală. Vom furniza o altă actualizare de îndată ce identificăm componenta afectată și vom avea mai multe informații de împărtășit.

2. 28 iulie 2026 la 14:25 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 28 iulie 2026 la 14:25 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

4. 28 iulie 2026 la 14:27 UTCmonitoring

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

5. 28 iulie 2026 la 14:38 UTCresolved

   Ne-am rostogolit înapoi o implementare componentă care nu a fost cauza timpii de decizie ridicate. După o perioadă de monitorizare, toate sistemele au revenit la funcționarea normală. Ne cerem scuze pentru orice neplăceri cauzate.

Traducere automată din actualizarea oficială a incidentului.

1. 24 iulie 2026 la 12:15 UTCinvestigating

   Investigăm în prezent o posibilă performanță degradată prin deciziile de verificare. Echipa noastră lucrează la identificarea cauzei profunde a problemei care contribuie la deciziile întârziate și va oferi o actualizare în scurt timp.

2. 24 iulie 2026 la 16:46 UTCidentified

   Am identificat o problemă care afectează unul dintre furnizorii noștri terți și lucrăm îndeaproape cu aceștia pentru a o rezolva cât mai repede posibil. Deoarece problema este intermitentă, unele sesiuni pot experimenta latență decizie mai mare decât normal, în timp ce altele nu pot fi afectate. Vom continua să oferim actualizări pe măsură ce devin disponibile mai multe informații.

3. 24 iulie 2026 la 20:34 UTCmonitoring

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

4. 25 iulie 2026 la 11:59 UTCresolved

   După o perioadă de monitorizare cu succes, am confirmat că problema este pe deplin rezolvată. Parametrii sistemului au revenit la normal și toate serviciile sunt operaționale. Vă mulțumim pentru răbdare cu noi.

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 11:37 UTCresolved

   Între 2026-07-20 14:50 UTC și 2026-07-20 16:30 UTC, un incident la un furnizor de terțe părți a cauzat performanțe degradate pentru livrarea de Proiecții Watchlist (PEP și sancțiuni) webhooks. În această perioadă, rezultatele de screening Watchlist nu au putut fi generate, iar notificările corespunzătoare de webhook nu au fost livrate pentru un subset mic de sesiuni afectate. Acest incident a fost izolat exclusiv furnizorului terț; verificarea identității și capacitățile decizionale principale ale Veriff nu au fost afectate. Serviciul terţilor a revenit de atunci la funcţionarea normală, iar livrarea webhook-ului a fost reluată. Sesiunile afectate pot fi reprocesate pentru verificarea Watchlist Screening (PEP & Sancțiuni), după care rezultatele vor fi disponibile prin webhook, API-ul public și Veriff Hub/ Station.

Traducere automată din actualizarea oficială a incidentului.

1. 7 iulie 2026 la 21:06 UTCinvestigating

   We are currently investigating potential degraded performance with Verification Decisions. Our team is working on identifying root cause of the issue that is contributing to delayed decisions and will provide an update shortly.

2. 7 iulie 2026 la 21:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 iulie 2026 la 21:32 UTCmonitoring

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

4. 7 iulie 2026 la 23:43 UTCresolved

   This incident has been resolved.

1. 6 iulie 2026 la 20:39 UTCidentified

   We have identified an issue affecting one of our internal components, which is impacting verification decision times. As a result, some verification requests may take longer than usual to receive a decision. Our team is actively working to resolve the issue as quickly as possible and minimize the impact. We apologize for the inconvenience and appreciate your patience.

2. 9 iulie 2026 la 09:29 UTCidentified

   We are experiencing an issue with a component of our OCR (text extraction) service that supports Verification Decisions. This can delay how quickly a decision is returned and, in a small number of cases, affect the outcome. WHO IS AFFECTED - Customers processing verifications in our US region only. Other regions are unaffected. - Impact is intermittent (occurring in waves over the past ~2 days), not a continuous outage. WHAT YOU MAY SEE - Slower decisions (most common): verifications take longer than usual to return, but the decision itself is correct. - Incorrect resubmissions: a small proportion of legitimate verifications may be incorrectly returned for resubmission. An unusual spike in resubmissions may be caused by this. - Lower-confidence decisions: some decisions may be reached with incomplete text-extraction data. WHAT WE ARE DOING - The affected component is partially dependent on a third-party service that is currently experiencing an outage. We are working with the provider on a fix. - We have deployed changes to make the service more resilient and reduce the impact in the meantime. NEXT UPDATE - We will post our next update by 11:00 UTC Thursday, July 9th.

3. 9 iulie 2026 la 13:09 UTCidentified

   We are experiencing an issue with a component of our OCR (text extraction) service that supports Verification Decisions. This can delay how quickly a decision is returned and, in a small number of cases, affect the outcome. WHO IS AFFECTED - Customers processing verifications in our US region only. Other regions are unaffected. - Impact is intermittent (occurring in waves over the past ~2 days), not a continuous outage. WHAT YOU MAY SEE - Slower decisions (most common): verifications take longer than usual to return, but the decision itself is correct. - Incorrect resubmissions: a small proportion of legitimate verifications may be incorrectly returned for resubmission. An unusual spike in resubmissions may be caused by this. - Lower-confidence decisions: some decisions may be reached with incomplete text-extraction data. WHAT WE ARE DOING - We have deployed changes to make the service more resilient and reduce the impact in the meantime. - The affected component is partially dependent on a third-party service that is currently experiencing an outage. They stated that the fix would be deployed by Friday 10th of July. NEXT UPDATE - We will post our next update by 11:00 UTC Friday, July 10th.

4. 10 iulie 2026 la 12:43 UTCresolved

   Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

1. 6 iulie 2026 la 15:15 UTCidentified

   We have identified an issue affecting one of our internal components, which is impacting verification decision times. As a result, some verification requests may take longer than usual to receive a decision. Our team is actively working to resolve the issue as quickly as possible and minimize the impact. We apologize for the inconvenience and appreciate your patience.

2. 6 iulie 2026 la 19:31 UTCresolved

   Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

1. 30 iunie 2026 la 16:32 UTCinvestigating

   We have identified an issue that is preventing new Veriff accounts from being created. This issue does not affect existing customers or their ability to use the service; it only impacts the creation of new accounts. Our team is actively investigating the root cause and working to implement a fix. We will provide updates as more information becomes available.

2. 30 iunie 2026 la 16:57 UTCmonitoring

   The fix has been successfully deployed. While services have returned to operational, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

3. 30 iunie 2026 la 17:21 UTCresolved

   Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

1. 30 iunie 2026 la 15:22 UTCinvestigating

   We have identified an issue affecting manual verifications that may cause delays in verification decisions. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We will provide updates as more information becomes available.

2. 30 iunie 2026 la 15:33 UTCidentified

   The root cause of the issue has been identified. Our team is prioritized on deploying a fix.

3. 30 iunie 2026 la 15:40 UTCresolved

   This incident has been resolved.

1. 18 iunie 2026 la 14:39 UTCinvestigating

   Thank you for your patience. We have identified the components with the issue. Our team is actively investigating the root cause, and we will share a status update shortly.

2. 18 iunie 2026 la 15:03 UTCidentified

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

3. 18 iunie 2026 la 15:56 UTCmonitoring

   We identified an issue affecting the search service in Veriff Station that caused some search requests to fail and return errors. The issue has been resolved, and a fix has been deployed. We are actively monitoring the service to ensure continued stability and performance.

4. 18 iunie 2026 la 18:59 UTCresolved

   Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.

1. 17 iunie 2026 la 15:26 UTCmonitoring

   We have identified an issue affecting one of our services, resulting in longer-than-expected decision times for verifications. A fix has already been deployed; however, some related effects are still being mitigated as the changes continue to propagate through the system. Our team is actively monitoring the situation and will provide further updates as they become available.

2. 17 iunie 2026 la 16:15 UTCresolved

   This incident has been resolved.

1. 12 iunie 2026 la 02:06 UTCinvestigating

   We are currently investigating potential degraded performance with Verification Decisions. Our team is working on identifying root cause of the issue that is contributing to delayed decisions and will provide an update shortly.

2. 12 iunie 2026 la 02:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 12 iunie 2026 la 02:43 UTCidentified

   The issue has been identified.

4. 12 iunie 2026 la 03:11 UTCmonitoring

   The issue has been traced back to an upstream infrastructure outage affecting our platform. We are working closely with the provider to monitor the resolution and restore full functionality.

5. 12 iunie 2026 la 05:45 UTCmonitoring

   The fix has been successfully deployed. While services are returning to operational level, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

6. 12 iunie 2026 la 10:19 UTCresolved

   This incident has been resolved.

1. 11 iunie 2026 la 17:38 UTCresolved

   Between 2026-06-11 11:10 and 2026-06-11 14:50, Auto Decision Time experienced degraded performance. The issue was identified and resolved by our team before this notification was published. System metrics have returned to normal and all services are operational.

1. 8 iunie 2026 la 17:23 UTCresolved

   Between 2026-06-08 16:15 and 2026-06-08 17:00 UTC, our API and Webhook services experienced degraded performance. The issue was identified and resolved by our team before this notification was published. System metrics have returned to normal and all services are operational.

1. 27 mai 2026 la 14:51 UTCresolved

   Between 14:01:00 UTC and 14:15:00 UTC, the decision times experienced degraded performance. The issue was identified and resolved by our team before this notification was published. System metrics have returned to normal and all services are operational.

1. 19 mai 2026 la 07:45 UTCmonitoring

   Hello! We wanted to to inform you that our session expiry is currently experiencing issues, which prevents sessions from getting expired/abandoned once the sessions is past it's validity date. Please also note that decision webhooks notifying about expired/abandoned sessions are also not being sent because of this issue at hand The root cause of the issue was already identified, further impact mitigated and we are waiting for the session backlog to clear out. We will keep you posted on new updates

2. 20 mai 2026 la 06:34 UTCresolved

   This incident has been resolved.

1. 24 aprilie 2026 la 14:18 UTCinvestigating

   We are currently investigating potential degraded performance with INE/ CURP 2.0 validation check. Our team is working on identifying root cause of the issue that is contributing to delayed decisions and will provide an update shortly.

2. 24 aprilie 2026 la 14:32 UTCidentified

   The root cause of the issue has been identified. Our team is prioritized on deploying a fix.

3. 24 aprilie 2026 la 15:30 UTCmonitoring

   The fix has been successfully deployed. While services have returned to operational, our team is actively monitoring system performance and alerts for the next few hours to ensure total stability. We appreciate your patience while we verify the resolution.

4. 24 aprilie 2026 la 15:34 UTCresolved

   Following a period of successful monitoring, we have confirmed that the issue is fully resolved. System metrics have returned to normal and all services are operational. Thank you for your patience with us.