Störungsverlauf von Veriff

1. 3. September 2026 um 22:18 UTCinvestigating

   Wir untersuchen derzeit potenzielle Leistungseinbußen mit Verifizierungsentscheidungen. Unser Team arbeitet daran, die Ursache des Problems zu identifizieren, das zu verzögerten Entscheidungen beiträgt, und wird in Kürze ein Update bereitstellen.

2. 3. September 2026 um 22:30 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 3. September 2026 um 22:34 UTCidentified

   Ein Problem wurde mit einem unserer Drittanbieter identifiziert, was zu einer Erhöhung der Entscheidungszeiten für die automatische Überprüfung in unseren US-Regionen führt.

4. 3. September 2026 um 22:36 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

5. 3. September 2026 um 23:02 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

6. 4. September 2026 um 06:20 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 31. August 2026 um 20:46 UTCidentified

   Wir untersuchen derzeit potenzielle Leistungseinbußen mit Verifizierungsentscheidungen. Unser Team arbeitet daran, die Ursache des Problems zu identifizieren, das zu verzögerten Entscheidungen beiträgt, und wird in Kürze ein Update bereitstellen.

2. 31. August 2026 um 21:18 UTCidentified

   Wir untersuchen eine beeinträchtigte Leistung, die Verifizierungsentscheidungen für eine kleine Teilmenge von Verifizierungen in der US-Region beeinflusst. Unser Team hat das beitragende Problem identifiziert und neuen Traffic in eine gesunde Umgebung umgeleitet. Eine begrenzte Anzahl von laufenden Überprüfungen in der US-Region kann zu verzögerten Entscheidungen führen. Wir werden in Kürze ein Update bereitstellen.

3. 31. August 2026 um 21:55 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 31. August 2026 um 22:08 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 26. August 2026 um 16:46 UTCresolved

   Zwischen etwa 16:18 und 16:40 UTC am 26. August 2026 ist eine Teilmenge von Endbenutzern möglicherweise auf intermittierende Fehler oder Langsamkeit beim Abschluss des Verifizierungsflusses gestoßen. Unser Team identifizierte das Problem und wandte einen Fix an, woraufhin sich der Service erholte. Der Verifikationsfluss funktioniert jetzt normal. Wir beobachten weiterhin und werden untersuchen, um Wiederholungen zu verhindern.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. August 2026 um 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 um 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 um 19:24 UTCmonitoring

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

4. 6. August 2026 um 19:33 UTCresolved

   This incident has been resolved.

1. 28. Juli 2026 um 14:00 UTCinvestigating

   Wir überwachen aktiv ein Problem, das dazu führt, dass bei einigen automatisierten Sitzungen höhere Entscheidungszeiten als üblich auftreten. Dieses Problem betrifft nicht alle Sitzungen, so dass Sie möglicherweise betroffen sind oder nicht. Unser Team untersucht derzeit die Ursache. Wir werden ein weiteres Update bereitstellen, sobald wir die betroffene Komponente identifizieren und weitere Informationen teilen können.

2. 28. Juli 2026 um 14:25 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 28. Juli 2026 um 14:25 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

4. 28. Juli 2026 um 14:27 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

5. 28. Juli 2026 um 14:38 UTCresolved

   Wir haben eine fehlerhafte Komponentenbereitstellung zurückgenommen, die zu erhöhten Entscheidungszeiten führte. Nach einem Überwachungszeitraum sind alle Systeme in den Normalbetrieb zurückgekehrt. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. Juli 2026 um 12:15 UTCinvestigating

   Wir untersuchen derzeit potenzielle Leistungseinbußen mit Verifizierungsentscheidungen. Unser Team arbeitet daran, die Ursache des Problems zu identifizieren, das zu verzögerten Entscheidungen beiträgt, und wird in Kürze ein Update bereitstellen.

2. 24. Juli 2026 um 16:46 UTCidentified

   Wir haben ein Problem identifiziert, das einen unserer Drittanbieter betrifft, und arbeiten eng mit ihnen zusammen, um es so schnell wie möglich zu lösen. Da das Problem intermittierend ist, können einige Sitzungen eine höhere Latenz als die normale Entscheidung aufweisen, während andere möglicherweise nicht betroffen sind. Wir werden weiterhin Updates bereitstellen, sobald mehr Informationen verfügbar sind.

3. 24. Juli 2026 um 20:34 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 25. Juli 2026 um 11:59 UTCresolved

   Nach einer Phase erfolgreicher Überwachung haben wir bestätigt, dass das Problem vollständig gelöst ist. Die Systemmetriken sind wieder normal und alle Dienste sind funktionsfähig. Vielen Dank für Ihre Geduld mit uns.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 11:37 UTCresolved

   Zwischen 2026-07-20 14:50 UTC und 2026-07-20 16:30 UTC verursachte ein Vorfall bei einem Drittanbieter eine beeinträchtigte Leistung für die Lieferung von Watchlist Screening (PEP und Sanktionen) Webhooks. Während dieses Zeitraums konnten keine Watchlist-Screening-Ergebnisse generiert werden, und die entsprechenden Webhook-Benachrichtigungen wurden für eine kleine Teilmenge der betroffenen Sitzungen nicht geliefert. Dieser vorfall wurde ausschließlich auf den drittanbieter isoliert; veriffs kernidentitätsprüfung und entscheidungsfähigkeiten waren nicht betroffen. Der Drittanbieter-Service ist seitdem wieder in den normalen Betrieb zurückgekehrt und die Watchlist Screening-Webhook-Lieferung wurde wieder aufgenommen. Betroffene Sitzungen können für die Überprüfung des Watchlist-Screenings (PEP & Sanctions) erneut verarbeitet werden, Danach werden die ergebnisse über webhook, die public api und veriff hub/station verfügbar sein.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 7. Juli 2026 um 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 um 21:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 7. Juli 2026 um 21:32 UTCmonitoring

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

4. 7. Juli 2026 um 23:43 UTCresolved

   This incident has been resolved.

1. 6. Juli 2026 um 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 um 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 um 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 um 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 um 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 um 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 um 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 um 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 um 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 um 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 um 15:33 UTCidentified

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

3. 30. Juni 2026 um 15:40 UTCresolved

   This incident has been resolved.

1. 18. Juni 2026 um 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 um 15:03 UTCidentified

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

3. 18. Juni 2026 um 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 um 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 um 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 um 16:15 UTCresolved

   This incident has been resolved.

1. 12. Juni 2026 um 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 um 02:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 12. Juni 2026 um 02:43 UTCidentified

   The issue has been identified.

4. 12. Juni 2026 um 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 um 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 um 10:19 UTCresolved

   This incident has been resolved.

1. 11. Juni 2026 um 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 um 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 um 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 um 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 um 06:34 UTCresolved

   This incident has been resolved.

1. 24. April 2026 um 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 um 14:32 UTCidentified

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

3. 24. April 2026 um 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 um 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.