Cronologia delle interruzioni di Veriff

1. 3 settembre 2026 alle ore 22:18 UTCinvestigating

   Stiamo attualmente indagando sulle potenziali prestazioni degradate con le decisioni di verifica. Il nostro team sta lavorando per identificare la causa principale del problema che sta contribuendo a decisioni ritardate e fornirà un aggiornamento a breve.

2. 3 settembre 2026 alle ore 22:30 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

3. 3 settembre 2026 alle ore 22:34 UTCidentified

   Un problema è stato identificato con uno dei nostri fornitori di terze parti che causa un aumento dei tempi di decisione di verifica automatica nelle nostre regioni degli Stati Uniti.

4. 3 settembre 2026 alle ore 22:36 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

5. 3 settembre 2026 alle ore 23:02 UTCmonitoring

   Stiamo continuando a monitorare eventuali ulteriori problemi.

6. 4 settembre 2026 alle ore 06:20 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 31 agosto 2026 alle ore 20:46 UTCidentified

   Stiamo attualmente indagando sulle potenziali prestazioni degradate con le decisioni di verifica. Il nostro team sta lavorando per identificare la causa principale del problema che sta contribuendo a decisioni ritardate e fornirà un aggiornamento a breve.

2. 31 agosto 2026 alle ore 21:18 UTCidentified

   Stiamo indagando sulle prestazioni degradate che riguardano le decisioni di verifica per un piccolo sottoinsieme di verifiche nella regione degli Stati Uniti. Il nostro team ha identificato il problema di contribuire e reindirizzato nuovo traffico a un ambiente sano. Un numero limitato di verifiche in corso nella regione degli Stati Uniti può sperimentare decisioni ritardate. Forniamo un aggiornamento a breve.

3. 31 agosto 2026 alle ore 21:55 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 31 agosto 2026 alle ore 22:08 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 26 agosto 2026 alle ore 16:46 UTCresolved

   Tra circa 16:18 e 16:40 UTC il 26 Aug 2026, un sottoinsieme di utenti finali può avere incontrato errori intermittenti o lentezza durante il completamento del flusso di verifica. Il nostro team ha identificato il problema e applicato una correzione, dopo di che il servizio recuperato. Il flusso di verifica è ora operativo normalmente. Stiamo continuando a monitorare e indagare per prevenire il ripetersi.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 6 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 19:24 UTCmonitoring

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

4. 6 agosto 2026 alle ore 19:33 UTCresolved

   This incident has been resolved.

1. 28 luglio 2026 alle ore 14:00 UTCinvestigating

   Stiamo monitorando attivamente un problema che sta causando alcune sessioni automatizzate per sperimentare tempi di decisione più elevati del solito. Questo problema non riguarda tutte le sessioni, quindi si può o non può essere influenzato. Il nostro team sta attualmente indagando sulla causa principale. Forneremo un altro aggiornamento non appena identifichiamo il componente interessato e avremo maggiori informazioni da condividere.

2. 28 luglio 2026 alle ore 14:25 UTCinvestigating

   Stiamo continuando a indagare su questo problema.

3. 28 luglio 2026 alle ore 14:25 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

4. 28 luglio 2026 alle ore 14:27 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

5. 28 luglio 2026 alle ore 14:38 UTCresolved

   Abbiamo rimboccato un dispiegamento dei componenti inadeguato che stava causando tempi di decisione elevati. Dopo un periodo di monitoraggio, tutti i sistemi sono tornati al normale funzionamento. Ci scusiamo per qualsiasi inconveniente che possa aver causato.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 24 luglio 2026 alle ore 12:15 UTCinvestigating

   Stiamo attualmente indagando sulle potenziali prestazioni degradate con le decisioni di verifica. Il nostro team sta lavorando per identificare la causa principale del problema che sta contribuendo a decisioni ritardate e fornirà un aggiornamento a breve.

2. 24 luglio 2026 alle ore 16:46 UTCidentified

   Abbiamo identificato un problema che riguarda uno dei nostri fornitori di terze parti e stiamo lavorando a stretto contatto con loro per risolverlo il più rapidamente possibile. Poiché il problema è intermittente, alcune sessioni possono sperimentare la latenza decisionale più alta di normale, mentre altri potrebbero non essere colpiti. Continueremo a fornire aggiornamenti come ulteriori informazioni diventano disponibili.

3. 24 luglio 2026 alle ore 20:34 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 25 luglio 2026 alle ore 11:59 UTCresolved

   Dopo un periodo di monitoraggio di successo, abbiamo confermato che il problema è pienamente risolto. Le metriche di sistema sono tornate alla normalità e tutti i servizi sono operativi. Grazie per la vostra pazienza con noi.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 21 luglio 2026 alle ore 11:37 UTCresolved

   Tra 2026-07-20 14:50 UTC e 2026-07-20 16:30 UTC, un incidente a un fornitore di terze parti ha causato le prestazioni degradate per la consegna di Screening Watchlist (PEP e Sanzioni) webhooks. Durante questo periodo, i risultati di Screening della Watchlist non potrebbero essere generati, e le notifiche webhook corrispondenti non sono state fornite per un piccolo sottoinsieme di sessioni interessate. Questo incidente è stato isolato esclusivamente al fornitore di terze parti; la verifica dell'identità principale di Veriff e le capacità decisionali non sono state influenzate. Il servizio di terze parti è tornato al normale funzionamento e Watchlist Screening webhook consegna è ripreso. Le sessioni colpite possono essere rielaborate per il controllo Screening della lista di vigilanza (PEP & Sanctions), dopo di che i risultati saranno disponibili tramite webhook, l'API Pubblica e Veriff Hub/ Station.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 7 luglio 2026 alle ore 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 luglio 2026 alle ore 21:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 luglio 2026 alle ore 21:32 UTCmonitoring

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

4. 7 luglio 2026 alle ore 23:43 UTCresolved

   This incident has been resolved.

1. 6 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 15:33 UTCidentified

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

3. 30 giugno 2026 alle ore 15:40 UTCresolved

   This incident has been resolved.

1. 18 giugno 2026 alle ore 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 giugno 2026 alle ore 15:03 UTCidentified

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

3. 18 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 16:15 UTCresolved

   This incident has been resolved.

1. 12 giugno 2026 alle ore 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 giugno 2026 alle ore 02:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 12 giugno 2026 alle ore 02:43 UTCidentified

   The issue has been identified.

4. 12 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 10:19 UTCresolved

   This incident has been resolved.

1. 11 giugno 2026 alle ore 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 giugno 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 06:34 UTCresolved

   This incident has been resolved.

1. 24 aprile 2026 alle ore 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 aprile 2026 alle ore 14:32 UTCidentified

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

3. 24 aprile 2026 alle ore 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 aprile 2026 alle ore 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.