Veriff driftsforstyrrelser

1. 3. september 2026 kl. 22.18 UTCinvestigating

   Vi er i øjeblikket ved at undersøge potentielle forringet ydeevne med Verifikation beslutninger. Vores team arbejder på at identificere den grundlæggende årsag til problemet, der bidrager til forsinkede beslutninger og vil give en opdatering inden længe.

2. 3. september 2026 kl. 22.30 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 3. september 2026 kl. 22.34 UTCidentified

   Et problem er blevet identificeret med en af vores tredjeparts udbydere, der forårsager en stigning i auto kontrol beslutningstider i vores amerikanske regioner.

4. 3. september 2026 kl. 22.36 UTCmonitoring

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

5. 3. september 2026 kl. 23.02 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

6. 4. september 2026 kl. 06.20 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 31. august 2026 kl. 20.46 UTCidentified

   Vi er i øjeblikket ved at undersøge potentielle forringet ydeevne med Verifikation beslutninger. Vores team arbejder på at identificere den grundlæggende årsag til problemet, der bidrager til forsinkede beslutninger og vil give en opdatering inden længe.

2. 31. august 2026 kl. 21.18 UTCidentified

   Vi er ved at undersøge forringet ydeevne påvirker Verifikation beslutninger for en lille delmængde af verifikationer i den amerikanske region. Vores team har identificeret det medvirkende problem og omdirigeret ny trafik til et sundt miljø. Et begrænset antal kontroller af fremskridt i den amerikanske region kan opleve forsinkede beslutninger. Vi vil levere en opdatering snart.

3. 31. august 2026 kl. 21.55 UTCmonitoring

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

4. 31. august 2026 kl. 22.08 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. august 2026 kl. 16.46 UTCresolved

   Mellem ca. 16: 18 og 16: 40 UTC den 26. august 2026 kan en delmængde af slutbrugere være stødt på periodiske fejl eller langsommelighed, mens verifikationsstrømmen er afsluttet. Vores team identificerede problemet og anvendte et fix, hvorefter tjenesten inddrives. Verifikationsstrømmen fungerer nu normalt. Vi fortsætter med at overvåge og vil undersøge for at forhindre gentagelse.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 6. august 2026 kl. 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 kl. 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 kl. 19.24 UTCmonitoring

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

4. 6. august 2026 kl. 19.33 UTCresolved

   This incident has been resolved.

1. 28. juli 2026 kl. 14.00 UTCinvestigating

   Vi overvåger aktivt et spørgsmål, der får nogle automatiserede sessioner til at opleve højere beslutningstider end normalt. Dette spørgsmål påvirker ikke alle sessioner, så du kan eller ikke kan blive påvirket. Vores hold undersøger i øjeblikket årsagen. Vi vil give en anden opdatering, så snart vi identificere den berørte komponent og har flere oplysninger at dele.

2. 28. juli 2026 kl. 14.25 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 28. juli 2026 kl. 14.25 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

4. 28. juli 2026 kl. 14.27 UTCmonitoring

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

5. 28. juli 2026 kl. 14.38 UTCresolved

   Vi har kastet en fejlkomponent ud, der forårsagede øgede beslutningstider. Efter en overvågningsperiode er alle systemer vendt tilbage til normal drift. Vi undskylder for eventuelle ulemper.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 12.15 UTCinvestigating

   Vi er i øjeblikket ved at undersøge potentielle forringet ydeevne med Verifikation beslutninger. Vores team arbejder på at identificere den grundlæggende årsag til problemet, der bidrager til forsinkede beslutninger og vil give en opdatering inden længe.

2. 24. juli 2026 kl. 16.46 UTCidentified

   Vi har identificeret et spørgsmål, der berører en af vores tredjepartsleverandører og arbejder tæt sammen med dem for at løse det så hurtigt som muligt. Da problemet er intermitterende, kan nogle sessioner opleve højere end normal beslutning latency, mens andre måske ikke påvirkes. Vi vil fortsætte med at levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

3. 24. juli 2026 kl. 20.34 UTCmonitoring

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

4. 25. juli 2026 kl. 11.59 UTCresolved

   Efter en periode med vellykket overvågning har vi bekræftet, at spørgsmålet er helt løst. System målinger er vendt tilbage til normal og alle tjenester er operationelle. Tak for din tålmodighed med os.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. juli 2026 kl. 11.37 UTCresolved

   Mellem 2026- 07- 20 14: 50 UTC og 2026- 07- 20 16: 30 UTC forårsagede en hændelse på en tredjeparts udbyder forringet ydeevne for levering af Watchlist Screening (PEP og sanktioner) webkroge. I denne periode, Watchlist Screening resultater kunne ikke genereres, og de tilsvarende webhook meddelelser blev ikke leveret til en lille delmængde af berørte sessioner. Denne hændelse blev udelukkende isoleret til tredjepartsudbyderen; Veriffs centrale identitetskontrol og beslutningsmæssige kapaciteter blev ikke påvirket. Den tredje part service er siden vendt tilbage til normal drift og Watchlist Screening webhook levering er genoptaget. Berørte sessioner kan ombehandles til Watchlist Screening (PEP & Sanctions) kontrol, hvorefter resultater vil være tilgængelige via webhook, den offentlige API, og Veriff Hub / Station.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. juli 2026 kl. 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. juli 2026 kl. 21.07 UTCinvestigating

   We are continuing to investigate this issue.

3. 7. juli 2026 kl. 21.32 UTCmonitoring

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

4. 7. juli 2026 kl. 23.43 UTCresolved

   This incident has been resolved.

1. 6. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 15.33 UTCidentified

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

3. 30. juni 2026 kl. 15.40 UTCresolved

   This incident has been resolved.

1. 18. juni 2026 kl. 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. juni 2026 kl. 15.03 UTCidentified

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

3. 18. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 16.15 UTCresolved

   This incident has been resolved.

1. 12. juni 2026 kl. 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. juni 2026 kl. 02.25 UTCinvestigating

   We are continuing to investigate this issue.

3. 12. juni 2026 kl. 02.43 UTCidentified

   The issue has been identified.

4. 12. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 10.19 UTCresolved

   This incident has been resolved.

1. 11. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 06.34 UTCresolved

   This incident has been resolved.

1. 24. april 2026 kl. 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. april 2026 kl. 14.32 UTCidentified

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

3. 24. april 2026 kl. 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. april 2026 kl. 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.