Veryfi had 14 outages in the last 2 years totaling 36h 22m of downtime — averaging 0.6 incidents per month.
There were 14 Veryfi outages since June 24, 2025 totaling 36h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.
Lens SDK Repository recovered.
Lens SDK Repository went down.
Lens SDK Repository recovered.
We are observing an elevated error count related to processing of documents in files that are submitted in pre-signed S3 URLs. Other files appear to be processing as expected. We are investigating the issue.
Elevated error rates have now stopped without our intervention. We are continuing to investigate the incident, however all services are now back to normal.
Email collector is back online
We have identified the root cause being silent failures in a recent deployment to some servers. The issue has been resolved and services are operating normally again.
We have identified an increased error rate as of 01:17 UTC and are investigating the underlying cause.
We have identified the root cause being silent failures in a recent deployment to some servers. The issue has been resolved and services are operating normally again.
Lens SDK Repository went down.
We are currently addressing an issue with our Nexus repository caused by data corruption. Our team is actively working to recover all artifacts and restore full functionality as quickly as possible. To prevent future issues, we are also migrating to improved infrastructure for greater reliability and performance. We apologize for any inconvenience and appreciate your patience. Updates will be provided as we make progress. For urgent concerns, please contact [email protected]
We have completed recovering the Nexus repository. While all artifacts have been recovered, some authentication keys were not recoverable. If you experience authentication errors while connecting to Lens SDK repositories, please reset your keys at https://app.veryfi.com/api/settings/keys/ For further help, please contact [email protected]
The processing time has returned to its normal value.
We recently made a change to our infrastructure that temporarily increased processing times (14:00 - 15:05 UTC). We've resolved the issue, and everything is now operating as normal.
The processing time has returned to its normal value.
Some customers are experiencing 403 errors affecting some specific document processing requests. This is impacting a low volume of traffic.
We have identified the root cause of the issue as a recently updated Web Application Firewall (WAF) rule. The impact was confined to POST requests containing multipart/form-data payloads with specific data patterns that triggered the WAF rule. Given the nature of the rule, the specific data required to activate it, and the low volume of affected requests, this false positive scenario was not detected during our testing phase. The change has been reverted, and the issue is now fully resolved.
Start Time: 09:48:00 UTC Failure Period: - High failure rate: 09:45:00-10:10:00 UTC - Medium failure rate: 10:10:00-13:10:00 UTC Current Status: Problem fully mitigated Recovery Actions: - Utilize the retry mechanism as the retried calls would return the correct response - Veryfi can assist with reprocessing requests with lost OCR text, please request We experienced a significant degradation in our document extraction service, specifically impacting the Optical Character Recognition (OCR) text extraction process. This failure prevented text retrieval from a substantial portion of processed documents. Our team is actively investigating the cause of the issues.
Start Time: 09:48:00 UTC Failure Period: - High failure rate: 09:45:00-10:10:00 UTC - Medium failure rate: 10:10:00-13:10:00 UTC Current Status: Problem fully mitigated Recovery Actions: - Utilize the retry mechanism as the retried calls would return the correct response - Veryfi can assist with reprocessing requests with lost OCR text, please request We experienced a significant degradation in our document extraction service, specifically impacting the Optical Character Recognition (OCR) text extraction process. This failure prevented text retrieval from a substantial portion of processed documents. Our team is actively investigating the cause of the issues.
We have implemented a fix to DNS records to exclude Cloudflare. Services are currently once again reachable and operational.
All services are currently back to normal. The root cause of this issue is related to underlying, intermittent network latencies in AWS and is a recurrence of an earlier issue that we are currently still investigating with AWS. While investigations continue, we have restructured our infrastructure workloads such that fewer customers are impacted during these network latencies. We truly value your ongoing trust and appreciate your patience and understanding as we continue to work on this issue.
We are currently experiencing degradation in processing time, which may impact a subset of clients. Start time: 13:15:00 UTC. Our team is actively working to resolve the issue and restore optimal performance. We’re reviewing the root cause of the incident. Thank you for your patience and understanding .
All services have been operating at improved levels for the last 50 mins, however we do still observe somewhat higher than normal processing times for some customers. We are continuing to work on this issue.
All services are currently back to normal. The root cause of this issue is related to underlying, intermittent network latencies in AWS and is a recurrence of an earlier issue that we are currently still investigating with AWS. While investigations continue, we have restructured our infrastructure workloads such that fewer customers are impacted during these network latencies. We truly value your ongoing trust and appreciate your patience and understanding as we continue to work on this issue.
Status: Investigating Affected Services: User Authentication (Sign-In) and Profile Switching We are currently experiencing temporary issues with the sign-in process on the Veryfi platform caused by the recent security rollout. This is primarily impacting: Non-admin users attempting to sign in via Multi-Factor Authentication (MFA). Users signing in through connected third-party apps like Google. Profile switching functionality across accounts. Admin users using standard email/password sign-in are generally unaffected. Our engineering team is actively investigating and working to resolve these issues as quickly as possible. We expect a fix within the next few hours and will provide updates here. Workaround: In the meantime, we encourage affected users to sign in using their email and password directly. We apologize for the inconvenience and thank you for your patience while we address this.
We are pleased to report that the sign-in issues affecting non-admin users with Multi-Factor Authentication (MFA) and connected third-party apps (e.g., Google) have been resolved. Users should now be able to sign in normally using these methods. However, we are still experiencing issues with profile switching functionality across accounts. Our engineering team is actively working to resolve this as quickly as possible. We expect a fix soon.
We are happy to announce that the remaining issues with profile switching functionality across accounts have been fully resolved. All affected features, including sign-in via Multi-Factor Authentication (MFA), connected third-party apps (e.g., Google), and profile switching, are now operating normally. Admin users and standard email/password sign-ins were unaffected throughout. No further workarounds are necessary. Our engineering team has implemented the fix and is monitoring the system closely to ensure stability. We apologize for the inconvenience caused and appreciate your patience during this time.
We are experiencing an increased error rate in document processing requests. A small percentage of requests are returning a 504 error response. We are investigating the issue.
We have reduced error rates further by over provisioning compute resources and spreading requests across more worker nodes. We are continuing work on identifying the root cause of the issue.
We have identified the root cause as being a newly surfaced edge case scenario in requests being submitted for processing. These particular requests consume an unusually high level of compute resources, which has downstream impact on other requests processed by the same worker processes. We are currently working on a solution to handle these edge cases gracefully.
We have implemented and validated a fix for the problematic edge case. All systems are back to normal.
All services are stable and operating at normal levels. We identified a component in the Veryfi API that scaled insufficiently under a particularly high load. This issue was resolved and services began to operate once again at stable levels.
We are currently experiencing cloud networking issues. The Veryfi API performance is degraded. Some requests' latency has increased. We're doing our best in order to found out the root cause of these networking issues and fix it.
All services are stable and operating at normal levels. We identified a component in the Veryfi API that scaled insufficiently under a particularly high load. This issue was resolved and services began to operate once again at stable levels.