ABBYY incident

FlexiCapture - AU | Degraded Performance: Message Processing Delay

Major Resolved View vendor source →

ABBYY experienced a major incident on February 1, 2026 affecting AU, lasting 3h 9m. The incident has been resolved; the full update timeline is below.

Started
Feb 01, 2026, 11:10 PM UTC
Resolved
Feb 02, 2026, 02:19 AM UTC
Duration
3h 9m
Detected by Pingoru
Feb 01, 2026, 11:10 PM UTC

Affected components

AU

Update timeline

  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.