ABBYY Outage History

Started Oct 26, 2026, 08:00 AM UTC· resolved Oct 26, 2026, 10:40 AM UTC

1. resolved Oct 26, 2026, 08:00 AM UTC

   Transactions in Vantage 3 Cloud EU were slow or failed between approximately 08:00 and 10:40 UTC on October 26, 2026, because of a degraded infrastructure node. The node was removed from service and processing is back to normal. Transactions that failed in this period can be resubmitted. We apologize for the disruption.

Read the full incident report →

Started Oct 21, 2026, 05:23 PM UTC· resolved Oct 26, 2026, 02:26 PM UTC

1. investigating Oct 21, 2026, 05:23 PM UTC

   We are aware of processing delays affecting some customers in the Vantage US environment. Our team is investigating and working to restore normal processing times.

2. identified Oct 22, 2026, 01:15 PM UTC

   We have identified that the slow processing in Vantage US is caused by storage performance issues with our cloud provider, and we are working with the provider to resolve them. Error rates have been falling steadily over the past few days. We expect further improvement each day and a full resolution over the coming days. Until then, some customers may still see slower processing or occasional errors.

3. resolved Oct 26, 2026, 02:26 PM UTC

   The storage performance issues affecting Vantage US have been resolved, and processing times have returned to normal. Error rates fell steadily after we identified the cause, and we have confirmed that the environment is now operating as expected. If you still see slower processing or errors, please contact ABBYY Support. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Sep 24, 2026, 08:00 PM UTC· resolved Sep 25, 2026, 01:49 AM UTC

1. investigating Sep 24, 2026, 08:00 PM UTC

   We are investigating an issue affecting email imports in Vantage Cloud 3. Some customers may find that new emails are not being imported and may see an OAuth 2.0 authentication error when configuring email import. We have identified an issue with the authentication credentials used for email import and are working to restore service. We will share another update as soon as we have more information.

2. monitoring Sep 24, 2026, 08:39 PM UTC

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

3. resolved Sep 25, 2026, 01:49 AM UTC

   The incident has been resolved.

Read the full incident report →

Started Sep 24, 2026, 02:11 AM UTC· resolved Sep 24, 2026, 03:34 AM UTC

1. investigating Sep 24, 2026, 02:11 AM UTC

   We are currently experiencing ongoing message processing delays in the FlexiCapture AU environment due to sustained high queue volumes. This is impacting processing speeds for some users. Our technical team is actively working to reduce the backlog and restore system performance. Please be assured that resolving this issue remains a top priority. We appreciate your patience and will continue to provide timely updates as progress is made.

2. monitoring Sep 24, 2026, 02:22 AM UTC

   We’re pleased to inform you that the earlier issue affecting the FlexiCapture AU environment has been fully resolved. Message processing performance has returned to normal, and the message queue has been cleared. Our team has continued to monitor the system following recovery and no further delays have been observed. Thank you for your patience and understanding throughout this incident. If you have any further questions or concerns, please feel free to reach out.

3. resolved Sep 24, 2026, 03:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 23, 2026, 07:57 PM UTC· resolved Sep 23, 2026, 11:10 PM UTC

1. investigating Sep 23, 2026, 07:57 PM UTC

   We are investigating reports of failed transactions in the ABBYY Vantage Cloud 3 US environment. Our teams are working to identify the cause. We will provide an update as more information becomes available.

2. identified Sep 23, 2026, 08:30 PM UTC

   We have identified an issue with the infrastructure supporting ABBYY Vantage Cloud 3 in the US that is causing transaction failures. Our team is working to resolve it and will provide another update as soon as more information is available.

3. monitoring Sep 23, 2026, 08:58 PM UTC

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

4. resolved Sep 23, 2026, 11:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 23, 2026, 02:35 PM UTC· resolved Sep 23, 2026, 07:56 PM UTC

1. investigating Sep 23, 2026, 02:35 PM UTC

   We are investigating an issue affecting multiple FlexiCapture Cloud customers. Affected customers may see “License has expired or has been deleted” in the Administration and Monitoring console, or a “No License” error. This may prevent document ingestion and other production work. Our teams are investigating with high priority. We will share an update as soon as we have confirmed information about the cause or recovery.

2. investigating Sep 23, 2026, 02:40 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 23, 2026, 03:29 PM UTC

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

4. resolved Sep 23, 2026, 07:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 04:30 PM UTC· resolved Sep 10, 2026, 08:39 PM UTC

1. identified Sep 09, 2026, 04:30 PM UTC

   We are experiencing degraded performance in the ABBYY Vantage 3 Cloud US region due to very high system load. Customers may experience slower-than-normal response and processing times. Our teams are monitoring the environment closely and working to restore normal performance. We apologize for the inconvenience and will provide another update as soon as more information becomes available.

2. monitoring Sep 09, 2026, 06:29 PM UTC

   Performance in the ABBYY Vantage 3 Cloud US region has returned to normal levels. Our teams will continue to monitor the environment closely to confirm that performance remains stable. We apologize for the inconvenience and will provide a further update once monitoring is complete.

3. resolved Sep 10, 2026, 08:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 27, 2026, 12:58 PM UTC· resolved Sep 01, 2026, 05:00 PM UTC

1. investigating Aug 27, 2026, 12:58 PM UTC

   We are investigating an issue affecting mailbox imports in FlexiCapture Cloud and on-premises environments. Customers using OAuth authentication may be unable to import documents from configured mailboxes. We have identified the cause and are preparing an emergency fix for FlexiCapture Cloud. FlexiCapture on-premises customers should create a support ticket for assistance with the required remediation. https://support.abbyy.com/hc/en-us/requests/new We apologize for the inconvenience and will provide another update as soon as more information is available.

2. identified Aug 27, 2026, 05:12 PM UTC

   We are continuing work to resolve the issue affecting mailbox imports using OAuth authentication in FlexiCapture Cloud and on-premises environments. The required update is currently being built and will undergo validation before being deployed across our Cloud environments. Updated installers for on-premises customers will follow the Cloud deployment. As a temporary workaround, customers may use an alternative document import method where available. We will provide another update as the deployment progresses.

3. monitoring Aug 27, 2026, 10:56 PM UTC

   A fix is now available for an issue affecting Microsoft OAuth 2.0–based connections in FlexiCapture Cloud and on-premises environments, including IMAP, Microsoft Graph, and SharePoint import sources. Customers must apply the required updates to their FlexiCapture components to restore affected OAuth connections. A knowledge base article is now available with further information and remediation guidance for FlexiCapture customers: https://support.abbyy.com/hc/en-us/articles/38431926057618-Error-ERR-OAUTH-SECRET-EXPIRED-FlexiCapture-12 Customers requiring assistance should submit a request through ABBYY Customer Support. https://support.abbyy.com/hc/en-us/requests/new We sincerely apologize for the disruption and appreciate your patience while we complete the deployment and validation process. We will provide another update as work progresses.

4. resolved Sep 01, 2026, 05:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 12, 2026, 12:33 AM UTC· resolved Aug 12, 2026, 02:21 AM UTC

1. investigating Aug 12, 2026, 12:33 AM UTC

   We are investigating reports of increased transaction processing times in the ABBYY FlexiCapture Cloud AU environment. Some customers may experience delays in transaction processing. Our teams are actively investigating the issue and working to restore normal processing performance. We will provide further updates as more information becomes available.

2. monitoring Aug 12, 2026, 01:05 AM UTC

   We have identified the cause of the increased transaction processing times and implemented a fix. Our monitoring shows that processing performance has returned to normal. We will continue to closely monitor the environment for the next hour to ensure service remains stable before closing the incident. We will provide a final update once monitoring is complete.

3. resolved Aug 12, 2026, 02:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 11, 2026, 01:47 PM UTC· resolved Aug 11, 2026, 04:02 PM UTC

1. investigating Aug 11, 2026, 01:47 PM UTC

   We are investigating reports of increased transaction processing times in the ABBYY Vantage 3 Cloud US environment. Some customers may experience delays in transaction processing. Our teams are actively investigating the issue and working to restore normal processing performance. We will provide further updates as more information becomes available.

2. monitoring Aug 11, 2026, 02:11 PM UTC

   We have identified the cause of the increased transaction processing times in the ABBYY Vantage 3 Cloud US environment and have implemented a fix. The system is now recovering and processing the accumulated workload. Customers may continue to experience some processing delays while the backlog is cleared. We will continue to monitor the environment closely and provide a further update once processing has returned to normal.

3. monitoring Aug 11, 2026, 02:29 PM UTC

   Our monitoring indicates that the transaction backlog has been cleared and the ABBYY Vantage 3 Cloud US environment is now operating normally. We will continue to closely monitor the environment for the next hour to confirm that performance remains stable before closing the incident.

4. resolved Aug 11, 2026, 04:02 PM UTC

   This incident has been resolved

Read the full incident report →

Started Jul 04, 2026, 02:16 PM UTC· resolved Jul 04, 2026, 07:03 PM UTC

1. identified Jul 04, 2026, 02:16 PM UTC

   We are currently investigating reports of delayed document processing in the Vantage 3 US region. Some transactions may remain in a processing state longer than expected, and users may experience delays as documents move through the workflow or load in Manual Review. We have identified that the delays are related to an unusual increase in processing load, which is exceeding the currently available resources. Our Engineering and Cloud Operations teams are actively working to increase available capacity and restore normal processing performance. Customers may continue to experience delays while transactions are processed and the backlog is reduced. We will provide another update as soon as additional progress has been made.

2. monitoring Jul 04, 2026, 04:33 PM UTC

   Our cloud provider has completed the required remediation actions, and document processing performance in the Vantage 3 US region has returned to expected levels. Transactions are now processing normally, and any remaining backlog is continuing to clear. ABBYY Engineering and Cloud Operations teams are monitoring the environment closely to confirm continued stability. We will keep this incident in a monitoring state and provide another update if any additional issues are observed.

3. resolved Jul 04, 2026, 07:03 PM UTC

   The infrastructure issue affecting ABBYY Vantage 3 US has been resolved following corrective actions completed by our cloud provider. ABBYY has validated that platform services are operating normally, and we have monitored the environment to confirm stability. Processing performance has returned to expected levels, and the intermittent platform errors observed during the incident are no longer occurring. We appreciate your patience while we worked with our cloud provider to restore service and apologize for the disruption this incident caused. If you continue to experience issues that you believe are related to this incident, please contact ABBYY Support for assistance.

Read the full incident report →

Started Jul 03, 2026, 03:54 PM UTC· resolved Jul 03, 2026, 08:01 PM UTC

1. investigating Jul 03, 2026, 03:54 PM UTC

   Investigating - We are currently investigating issues affecting ABBYY Vantage 3.0 in the US region. One reported symptom is related to catalogs, including intermittent errors when accessing or creating catalogs and catalog lookups not appearing or functioning as expected. Our teams are actively reviewing the issue and working to identify the cause. We will provide another update within the next 60 minutes, or sooner if additional information becomes available.

2. identified Jul 03, 2026, 05:02 PM UTC

   We have identified the issue as being related to a cloud provider scaling activity that did not complete as expected. Our team is actively working with the cloud provider to resolve the issue and restore normal processing performance. We are continuing to monitor the environment closely while remediation work is underway. We understand the impact this may have on your operations and apologize for the disruption. We will provide another update within the next 90 minutes, or sooner if additional information becomes available.

3. identified Jul 03, 2026, 06:28 PM UTC

   Our cloud provider is actively working to resolve the underlying infrastructure issue. ABBYY teams remain engaged with the provider, are monitoring the environment, and will validate recovery once remediation is completed. Customers may continue to experience intermittent platform errors and elevated processing times until the cloud provider completes the required corrective actions. We apologize for the disruption and will provide another update within the next 90 minutes, or sooner if additional information becomes available.

4. monitoring Jul 03, 2026, 07:14 PM UTC

   Our cloud provider has completed the corrective actions to resolve the underlying infrastructure issue affecting ABBYY Vantage 3 US. ABBYY teams are now validating recovery and closely monitoring the environment.

5. resolved Jul 03, 2026, 08:01 PM UTC

   The infrastructure issue affecting ABBYY Vantage 3 US has been resolved following corrective actions completed by our cloud provider. ABBYY has validated that platform services are operating normally, and we have monitored the environment to confirm stability. Processing performance has returned to expected levels, and the intermittent platform errors observed during the incident are no longer occurring. We appreciate your patience while we worked with our cloud provider to restore service and apologize for the disruption this incident caused. If you continue to experience issues that you believe are related to this incident, please contact ABBYY Support for assistance.

Read the full incident report →

Started Jul 02, 2026, 08:36 PM UTC· resolved Jul 02, 2026, 09:11 PM UTC

1. identified Jul 02, 2026, 08:36 PM UTC

   We are currently seeing elevated transaction processing times for Vantage 3 US and are actively working on a fix. We understand the impact this may have on your operations and apologize for the disruption. We will provide another update within the next 90 minutes, or sooner if additional information becomes available.

2. resolved Jul 02, 2026, 09:11 PM UTC

   The issue causing elevated transaction processing times in Vantage 3 US has been resolved. The root cause was identified as a bug in the scaling configuration, which has now been corrected. Transaction processing performance has returned to normal, and we are continuing to monitor the environment to ensure stability. We apologize for the disruption and appreciate your patience while our team worked to resolve the issue.

Read the full incident report →

Started Jun 24, 2026, 04:24 PM UTC· resolved Jun 30, 2026, 05:40 PM UTC

1. investigating Jun 24, 2026, 04:24 PM UTC

   We are currently investigating reports of delayed document processing in the Vantage 3 US region. Some transactions may remain in a processing state longer than expected, and users may experience delays as documents move through the workflow or load in Manual Review. We have identified that the delays are related to an unusual increase in processing load, which is exceeding the currently available resources. Our Engineering and Cloud Operations teams are actively working to increase available capacity and restore normal processing performance. Customers may continue to experience delays while transactions are processed and the backlog is reduced. We will provide another update as soon as additional progress has been made.

2. identified Jun 24, 2026, 07:26 PM UTC

   Our Engineering and Cloud Operations teams continue to work on increasing available capacity in the Vantage 3 US region. We are also working with our cloud provider to investigate challenges with scaling the environment. At this time, customers may continue to experience delayed document processing, with some transactions remaining in a processing state longer than expected. Users may also experience delays as documents move through the workflow or load in Manual Review. We will provide another update as soon as additional progress has been made.

3. identified Jun 25, 2026, 05:55 AM UTC

   We are continuing to work on the fix, and we will keep you posted as and when we have further updates. Next Update will be at 8:00 AM UTC.

4. identified Jun 25, 2026, 08:13 AM UTC

   We are actively working with our cloud provider on infrastructure changes to address the ongoing performance degradation. We continue to monitor the platform closely and will provide further updates as progress is made. Next Update: 11 AM UTC

5. monitoring Jun 25, 2026, 10:48 AM UTC

   Performance has returned to normal, and document processing is operating as expected. We will continue to closely monitor the platform to ensure stability and will provide further updates if needed.

6. identified Jun 25, 2026, 05:58 PM UTC

   We have identified that some transactions became stuck in a processing state during the incident. This issue is affecting both the Vantage 3 EU and US regions, although it is currently more prevalent in the US region. Document processing performance has improved; however, infrastructure scaling efforts with our cloud provider are still ongoing. Our cloud provider has estimated that these scaling activities will be completed this weekend. Until those activities are complete, some transactions may continue to become stuck or remain in processing longer than expected. Users may also experience intermittent failures when attempting to open documents in Manual Review. Our Engineering and Cloud Operations teams continue to work with our cloud provider to complete the required scaling activities and reduce customer impact. We will provide additional guidance in future updates on how customers should proceed with transactions that remain stuck. We will continue to provide updates as additional progress is made.

7. monitoring Jun 26, 2026, 04:38 PM UTC

   Our cloud provider has successfully completed the required scaling activities, and performance has returned to normal in the ABBYY Vantage 3 US region. Document processing is operating as expected. We will continue to closely monitor the platform to ensure stability and will provide further updates if needed. Customers experiencing stuck transactions and/or Manual Review issues will need to reprocess the affected transactions. If assistance is needed with reprocessing stuck transactions, please create a ticket with ABBYY Support using the following link: https://support.abbyy.com/hc/en-us/requests/new

8. resolved Jun 30, 2026, 05:40 PM UTC

   The required infrastructure scaling activities have been completed and document processing is operating as expected. We have monitored the environment for several business days without the issue returning. Based on this continued stability, we are marking this incident as resolved. Customers who still have stuck transactions from last week’s incident, or who are continuing to experience Manual Review issues related to last week’s incident, should create a support ticket with ABBYY Support for assistance: https://support.abbyy.com/hc/en-us/requests/new

Read the full incident report →

Started Jun 24, 2026, 03:27 PM UTC· resolved Jun 30, 2026, 05:40 PM UTC

1. investigating Jun 24, 2026, 03:27 PM UTC

   We are currently investigating reports of delayed document processing in the Vantage 3 EU region. Some transactions may remain in a processing state longer than expected, and users may experience delays when documents are moving through the workflow or loading in Manual Review. Our engineering and cloud operations teams are actively reviewing the affected services and processing queues. We will provide an update as soon as more information is available. We apologize for the disruption and appreciate your patience while we work to restore normal processing performance.

2. identified Jun 24, 2026, 04:23 PM UTC

   We have identified that the processing delays in the Vantage 3 EU region are related to an unusual increase in load that is overwhelming the available processing resources. Our engineering and cloud operations teams are actively working to increase available resources and restore normal processing performance. Customers may continue to experience delays while transactions are processed and the backlog is reduced. We will provide another update as soon as additional progress has been made.

3. identified Jun 24, 2026, 07:25 PM UTC

   Our Engineering and Cloud Operations teams continue to work on increasing available capacity in the Vantage 3 EU region. We are also working with our cloud provider to investigate challenges with scaling the environment. At this time, customers may continue to experience delayed document processing, with some transactions remaining in a processing state longer than expected. Users may also experience delays as documents move through the workflow or load in Manual Review. We will provide another update as soon as additional progress has been made.

4. identified Jun 25, 2026, 12:17 AM UTC

   We continue to work with our cloud provider to scale additional resources. This process is taking longer than expected due to resource constraints reported by the provider, and we have been advised that scaling efforts may continue through the weekend. In parallel, we are performing optimizations within the existing environment to help reduce customer impact as much as possible. During this time, some transactions may remain in a processing state longer than expected, and users may also experience delays or errors when attempting to open documents in Manual Review. We understand how important timely processing and access to Manual Review are to our customers’ operations, and we are treating this issue with urgency. We will continue to provide updates as meaningful progress is made.

5. identified Jun 25, 2026, 05:55 AM UTC

   We are continuing to work on the fix, and we will keep you posted as and when we have further updates. Next Update will be at 8:00 AM UTC.

6. identified Jun 25, 2026, 08:14 AM UTC

   We are actively working with our cloud provider on infrastructure changes to address the ongoing performance degradation. We continue to monitor the platform closely and will provide further updates as progress is made. Next Update: 11 AM UTC

7. monitoring Jun 25, 2026, 10:48 AM UTC

   Performance has returned to normal, and document processing is operating as expected. We will continue to closely monitor the platform to ensure stability and will provide further updates if needed.

8. identified Jun 25, 2026, 05:58 PM UTC

   We have identified that some transactions became stuck in a processing state during the incident. This issue is affecting both the Vantage 3 EU and US regions, although it is currently more prevalent in the US region. Document processing performance has improved; however, infrastructure scaling efforts with our cloud provider are still ongoing. Our cloud provider has estimated that these scaling activities will be completed this weekend. Until those activities are complete, some transactions may continue to become stuck or remain in processing longer than expected. Users may also experience intermittent failures when attempting to open documents in Manual Review. Our Engineering and Cloud Operations teams continue to work with our cloud provider to complete the required scaling activities and reduce customer impact. We will provide additional guidance in future updates on how customers should proceed with transactions that remain stuck. We will continue to provide updates as additional progress is made.

9. resolved Jun 30, 2026, 05:40 PM UTC

   The required infrastructure scaling activities have been completed, and document processing is operating as expected. We have monitored the environment for several business days without the issue returning. Based on this continued stability, we are marking this incident as resolved. Customers who still have stuck transactions from last week’s incident, or who are continuing to experience Manual Review issues related to last week’s incident, should create a support ticket with ABBYY Support for assistance: https://support.abbyy.com/hc/en-us/requests/new

Read the full incident report →

Started Jun 04, 2026, 04:38 PM UTC· resolved Jun 04, 2026, 05:44 PM UTC

1. investigating Jun 04, 2026, 04:38 PM UTC

   Dear All, We are currently investigating slow performance affecting ABBYY Vantage 2.7 in the EU region. Customers may experience increased processing times or delays when using Vantage 2.7 EU. At this time, no other regions are affected. Our team is urgently investigating the root cause and working to restore normal performance as quickly as possible. We will provide another update as soon as more information is available.

2. investigating Jun 04, 2026, 05:13 PM UTC

   Update: Cloud Operations has implemented a fix. Initial validation was completed by processing a test document, and performance appears to be back to normal. Awaiting confirmation from the customer on whether they are seeing the expected performance on their tenant.

3. resolved Jun 04, 2026, 05:44 PM UTC

   The mitigation actions have been completed, and service performance has returned to expected levels. Platform monitoring shows stable operation, and no additional customer reports have been received. This incident is now considered resolved.

Read the full incident report →

Started Apr 24, 2026, 02:35 PM UTC· resolved Apr 24, 2026, 08:35 PM UTC

1. investigating Apr 24, 2026, 02:35 PM UTC

   ABBYY Vantage 3.0 US is currently unavailable. We are actively investigating the issue and working to restore service as quickly as possible. We apologize for the inconvenience and will provide updates as more information becomes available.

2. investigating Apr 24, 2026, 03:11 PM UTC

   We are continuing to work to resolve the issue affecting ABBYY Vantage 3.0 US. At this time, ABBYY Vantage 3.0 US is the only affected version and region. No other ABBYY Vantage versions or regions are currently impacted.

3. investigating Apr 24, 2026, 03:40 PM UTC

   We are actively investigating the impact of an issue with our cloud provider on ABBYY Vantage 3.0 US.

4. identified Apr 24, 2026, 04:00 PM UTC

   We are actively working with our cloud provider to resolve an incident affecting their ability to provision and scale resources. We will continue to monitor progress and provide updates as more information becomes available.

5. identified Apr 24, 2026, 04:45 PM UTC

   We continue to investigate the issue with our cloud provider and are working with them to restore normal provisioning and scaling capabilities. ABBYY Vantage 3.0 US remains the only affected version and region at this time. The next update will be provided at 17:10 UTC.

6. identified Apr 24, 2026, 05:10 PM UTC

   We continue to work with our cloud provider to resolve the incident affecting their ability to provision and scale resources. ABBYY Vantage 3.0 US remains the only affected version and region at this time. The next update will be provided at 18:10 UTC.

7. identified Apr 24, 2026, 06:10 PM UTC

   Our cloud provider continues to implement mitigation steps across the affected environment. Recovery efforts remain in progress, but full recovery has not yet been validated. ABBYY Vantage 3.0 US remains the only affected version and region at this time. The next update will be provided at 19:10 UTC.

8. identified Apr 24, 2026, 07:14 PM UTC

   Our cloud provider continues to experience issues within the affected environment; however, mitigation efforts are showing signs of improvement. Recovery work remains in progress, and ABBYY continues to monitor the situation closely. The next update will be provided at 20:10 UTC

9. resolved Apr 24, 2026, 08:35 PM UTC

   Service has been restored for ABBYY Vantage 3.0 US. ABBYY has validated recovery and will continue to monitor the environment to ensure ongoing stability. A Root Cause Analysis will be provided once the incident review is complete. Thank you for your patience, and we apologize for the disruption.

Read the full incident report →

Started Mar 22, 2026, 07:48 PM UTC· resolved Mar 23, 2026, 01:34 AM UTC

1. identified Mar 22, 2026, 07:48 PM UTC

   The FlexiCapture platform is currently processing an unplanned spike in data volume and is operating at full capacity with no backlog in the queue. As a result, some partners may notice intermittent slowness when initiating batch or document processing. Our team is actively working with affected parties to distribute volume across off-peak hours better.

2. identified Mar 22, 2026, 09:12 PM UTC

   The number of batches submitted by the bulk processing partner has been reduced. I can confirm there is no backlog, and documents and batches are currently being processed in real time. We will continue to monitor the queue and will let you know if any issues arise.

3. monitoring Mar 22, 2026, 11:17 PM UTC

   The volume of batches submitted by the bulk processing client has now reduced. The system remains stable, with no backlog, and all documents and batches are being processed in real time. We are continuing to monitor the platform closely to ensure consistent performance. At this stage, no further impact is observed.

4. monitoring Mar 23, 2026, 12:44 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Mar 23, 2026, 01:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 24, 2026, 08:48 AM UTC· resolved Feb 24, 2026, 11:50 AM UTC

1. investigating Feb 24, 2026, 08:48 AM UTC

   We are currently observing elevated message queue volumes in the FlexiCapture AU environment. While the system remains operational, you may experience slower-than-usual message processing during this time. Our engineering team is closely monitoring the situation and actively working to restore processing speeds to normal levels. We will continue to keep you informed of any significant developments. Thank you for your understanding.

2. identified Feb 24, 2026, 09:14 AM UTC

   A partial fix has been implemented, and we can see that the queue has started to decrease. We are continuing to monitor the situation and investigate further to ensure full resolution.

3. monitoring Feb 24, 2026, 09:25 AM UTC

   The fix has been applied, the instance has been restored, and the backlog has been cleared. Services are operating normally. Monitoring will continue to ensure stability.

4. resolved Feb 24, 2026, 11:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 10, 2026, 08:18 AM UTC· resolved Feb 15, 2026, 12:58 AM UTC

1. investigating Feb 10, 2026, 08:18 AM UTC

   We are currently experiencing issues running our ABBYY FineReader solution, where document processing is failing due to licensing server communication errors. The FineReader workers are getting stuck because they are unable to communicate properly with the Licensing Server.

2. investigating Feb 10, 2026, 08:18 AM UTC

   We are continuing to investigate this issue.

3. investigating Feb 10, 2026, 09:25 AM UTC

   We are seeing a similar issue in FineReader Server. Our team is currently investigating and will provide updates as they become available.

4. investigating Feb 10, 2026, 10:07 AM UTC

   As a temporary workaround, we are assigning temporary software licenses to impacted clients to ensure continued service while we work on a permanent resolution. If you experience any issues or require a temporary license, please write to us and we will allocate one promptly.

5. investigating Feb 10, 2026, 04:53 PM UTC

   We are actively working on the issue. In the meantime, please open a support case at support.abbyy.com so we can allocate a workaround.

6. investigating Feb 12, 2026, 09:32 AM UTC

   Additionally, licensing-related issues have been identified impacting FineReader Server 14, FlexiCapture SDK, and FlexiCapture 12. Our team is actively working on a permanent solution.

7. investigating Feb 12, 2026, 11:38 AM UTC

   We are continuing to investigate the licensing server communication issue currently affecting ABBYY products. Impacted Products The following products may be impacted: FineReader Server 14 FineReader Engine 12 for Windows FineReader Engine 12 for Linux FlexiCapture 12 FlexiCapture 12 SDK Summary of Progress Temporary software licenses are being issued as a mitigation while ABBYY Engineering works on a permanent resolution. However, please note: a)The temporary software license workaround applies only to environments where the ABBYY License Manager is deployed. b)Customers running services in Docker/Kubernetes environments without a License Manager instance may not be able to use this workaround. For such environments, resolution depends on restoration of normal licensing server communication. Current Actions & Nex Steps a)Engineering is now analyzing logs and connection metadata to determine common factors (license type, client version, network path, etc.) for remaining license connection failures. b)Restoration of stable licensing communication remains the top priority. c)We will share the next update in another 1 hour with more details. If you are impacted, please contact support. We sincerely appreciate your patience while we work toward full resolution.

8. investigating Feb 12, 2026, 01:25 PM UTC

   Update - We are continuing to investigate the root cause of the licensing issue and are actively validating a workaround for cases where a temporary license cannot be used. Restoring full licensing stability is our highest priority, and we are addressing this with urgency.

9. identified Feb 12, 2026, 02:52 PM UTC

   We’ve identified an interim solution and are actively applying it to restore service for impacted customers as quickly as possible. As part of this work, we are validating serial numbers to ensure they are configured correctly. We appreciate your patience while we complete this effort and will continue to share updates.

10. monitoring Feb 12, 2026, 04:06 PM UTC

    A fix has now been applied to address the licensing issue. Our Support team is actively reviewing open tickets to confirm resolution with affected customers. If you are still experiencing any licensing-related issues, please submit a request through Support at https://support.abbyy.com/ so we can assist you directly.

11. resolved Feb 15, 2026, 12:58 AM UTC

    Please reach out to support if you encounter any issues.

Read the full incident report →

Started Feb 02, 2026, 01:47 PM UTC· resolved Feb 03, 2026, 08:15 PM UTC

1. investigating Feb 02, 2026, 01:47 PM UTC

   Communication with the online licensing service is failing. We are actively investigating the cause and working on a resolution. Updates will be provided as they become available.

2. investigating Feb 02, 2026, 04:30 PM UTC

   The investigation is ongoing, and our teams are actively working on the matter. We will provide further updates when available.

3. investigating Feb 02, 2026, 05:24 PM UTC

   The investigation is ongoing, and our teams are actively working on the matter. We will provide further updates when available.

4. investigating Feb 02, 2026, 10:08 PM UTC

   The investigation is ongoing, and our teams are actively working on the matter. We will provide further updates when available.

5. identified Feb 02, 2026, 10:51 PM UTC

   A permanent fix is in progress and will take additional time to complete. As a temporary workaround, please reach out to Support for assistance.

6. resolved Feb 03, 2026, 08:15 PM UTC

   This incident has been resolved. Please reach out to support if you encounter any issues.

Read the full incident report →

Started Feb 02, 2026, 09:07 AM UTC· resolved Feb 02, 2026, 06:26 PM UTC

1. investigating Feb 02, 2026, 09:07 AM UTC

   Communication with the online licensing service is failing. We are actively investigating the cause and working on a resolution. Updates will be provided as they become available.

2. investigating Feb 02, 2026, 09:49 AM UTC

   The issue still remains under investigation. The teams are actively working on the issue. Further updates will be shared as available.

3. investigating Feb 02, 2026, 12:01 PM UTC

   The investigation is ongoing, and our teams are actively working on the matter. We will provide further updates when available.

4. identified Feb 02, 2026, 12:28 PM UTC

   We have identified an issue and our teams are actively working on remediation. We will provide additional updates as progress continues. Thank you for your patience.

5. monitoring Feb 02, 2026, 01:58 PM UTC

   A fix has been implemented and we are monitoring the system to ensure stability. Services are currently operating as expected. We will continue to observe performance and provide further updates if needed.

6. resolved Feb 02, 2026, 06:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 01, 2026, 11:10 PM UTC· resolved Feb 02, 2026, 02:19 AM UTC

1. investigating Feb 01, 2026, 11:10 PM UTC

   We are currently observing elevated message queue volumes in the FlexiCapture AU environment. While the system remains operational, you may experience slower-than-usual message processing during this time. Our engineering team is closely monitoring the situation and actively working to restore processing speeds to normal levels. We will continue to keep you informed of any significant developments. Thank you for your understanding.

2. investigating Feb 01, 2026, 11:40 PM UTC

   Investigation still in progress. We will get back to you as soon as we have more details.

3. investigating Feb 02, 2026, 12:01 AM UTC

   Our investigation is still in progress, and based on the current impact, we have escalated this issue to a Major Outage. Our teams are actively working to identify the root cause and restore full service as quickly as possible. We will continue to provide updates as more information becomes available. Thank you for your patience and understanding.

4. investigating Feb 02, 2026, 12:31 AM UTC

   The issue remains under investigation. Our engineering teams are actively working to resolve the outage and restore normal service. Further updates will be shared as available.

5. monitoring Feb 02, 2026, 12:53 AM UTC

   A fix has been implemented, and the system has resumed processing messages. We are actively monitoring the queues to ensure they fully drain and that the service stabilizes.

6. monitoring Feb 02, 2026, 01:25 AM UTC

   The system is back to normal operation after implementing the fix. We will continue to monitor the system for next couple of hours.

7. resolved Feb 02, 2026, 02:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 21, 2026, 07:53 PM UTC· resolved Jan 22, 2026, 06:13 AM UTC

1. investigating Jan 21, 2026, 07:53 PM UTC

   Our teams are actively investigating potential contributing factors and we will provide an update as soon as more information is available.

2. investigating Jan 21, 2026, 08:16 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 21, 2026, 08:33 PM UTC

   We are actively troubleshooting and investigating remediation steps. Thank you for your patience.

4. investigating Jan 21, 2026, 09:04 PM UTC

   Our teams are actively troubleshooting. Thank you for your patience.

5. investigating Jan 21, 2026, 09:21 PM UTC

   Our teams are working on a remediation. Thank you for your patience.

6. identified Jan 21, 2026, 09:41 PM UTC

   We’ve implemented improvement measures in the AU and EU regions, and services are operational. US remediation efforts are still ongoing.

7. identified Jan 21, 2026, 09:48 PM UTC

   We are continuing to work on a fix for this issue.

8. identified Jan 21, 2026, 10:41 PM UTC

   We are still observing the issue. Operations teams continues working to resolve it. We will update the status within 30 minutes or as soon as more information becomes available.

9. identified Jan 21, 2026, 11:27 PM UTC

   Vantage AU, EU, and US instances are fully functioning. However, there are still some internal errors being investigated.

10. monitoring Jan 21, 2026, 11:53 PM UTC

    We are seeing a recurrence of service issues in Vantage US. The team is actively working remediation.

11. identified Jan 22, 2026, 12:10 AM UTC

    We are actively addressing the issue in the US region. Thank you for your patience.

12. identified Jan 22, 2026, 12:35 AM UTC

    We are still actively addressing the issue in the US region.

13. identified Jan 22, 2026, 01:13 AM UTC

    We are working on a remediation for the US Region. Thank you for your patience.

14. identified Jan 22, 2026, 01:45 AM UTC

    The team is actively investigating the issue in the Vantage US environment and is applying corrective measures. We will provide further updates as progress continues.

15. monitoring Jan 22, 2026, 02:14 AM UTC

    The issue affecting the Vantage US environment has been resolved. Services are now operating normally. We will continue to monitor the system to ensure stability.

16. resolved Jan 22, 2026, 06:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Jan 20, 2026, 05:52 PM UTC· resolved Jan 21, 2026, 02:44 AM UTC

1. monitoring Jan 20, 2026, 05:52 PM UTC

   We experienced a service disruption in the Vantage US environment due to a storage capacity issue. Our SRE team detected the condition and remediated it promptly, and services have been restored. We will continue monitoring the environment to ensure stability.

2. investigating Jan 20, 2026, 06:17 PM UTC

   We are currently investigating this issue.

3. investigating Jan 20, 2026, 06:18 PM UTC

   We are receiving reports that the issue in the Vantage US environment may not fully resolved. Our SRE team is actively investigating and working to restore full service as quickly as possible.

4. investigating Jan 20, 2026, 06:29 PM UTC

   We are still investigating the issue. Thank you for your patience.

5. investigating Jan 20, 2026, 08:09 PM UTC

   We are actively troubleshooting the issue and have involved our Cloud Provider for assistance. Thank you for your patience.

6. investigating Jan 20, 2026, 08:31 PM UTC

   We are still actively troubleshooting the issue with our Cloud Provider. We appreciate your patience.

7. investigating Jan 20, 2026, 08:57 PM UTC

   We are actively troubleshooting and investigating remediation steps. Thank you for your patience.

8. monitoring Jan 20, 2026, 09:16 PM UTC

   We have implemented a solution and are actively monitoring the systems to ensure stability. Thank you for your patience.

9. resolved Jan 21, 2026, 02:44 AM UTC

   This incident has been resolved.

Read the full incident report →