ABBYY Outage History

ABBYY degraded · 1 active incident View live status →

Pingoru has recorded 53 incidents for ABBYY: 34 in the last 12 months and 11 in the last 90 days.

Source: status.abbyy.com

53incidents recorded
34last 12 months
11last 90 days
25 hourstypical duration

Incidents, newest first

Minor August 25, 2025 FlexCapture Cloud US - Performance Degradation 2h 43m US

Started Aug 25, 2025, 02:53 PM UTC· resolved Aug 25, 2025, 05:37 PM UTC

  1. investigating Aug 25, 2025, 02:53 PM UTC

    We have observed performance degradation in FlexCapture Cloud US. You may experience slowness in document processing times. We are actively investigating the issue for a resolution and will keep you informed of any significant developments.

  2. monitoring Aug 25, 2025, 03:32 PM UTC

    We have applied a fix and processing times should be stabilized. We are closely monitoring the situation.

  3. resolved Aug 25, 2025, 05:37 PM UTC

    The issue has been fully resolved, and we have not observed any further reoccurrences. Thank you for your patience and understanding while we worked to restore normal operations.

Read the full incident report →

Minor August 20, 2025 FlexiCapture - EU | Degraded Performance: Message Processing Delay 8h 26m EU

Started Aug 20, 2025, 08:08 AM UTC· resolved Aug 20, 2025, 04:35 PM UTC

  1. investigating Aug 20, 2025, 08:08 AM UTC

    We are currently observing slowness in FlexiCapture EU. 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 Aug 20, 2025, 08:46 AM UTC

    In addition to the ongoing slowness in FlexiCapture EU, we are also observing errors in the Event Viewer logs. Troubleshooting is currently in progress, and we’ll share further updates as soon as available.

  3. investigating Aug 20, 2025, 09:25 AM UTC

    Update: The issue has our full attention, and an investigation is actively in progress. We will continue to share updates as we work toward restoring normal performance.

  4. investigating Aug 20, 2025, 12:23 PM UTC

    Update: The issue is ongoing and we are working in restoring normal performance. We'll share updates as soon available. Thank you for your patience.

  5. investigating Aug 20, 2025, 02:07 PM UTC

    Update: A temporary solution has been applied and processing times have decreased. We'll share further updates on progress as soon as available.

  6. investigating Aug 20, 2025, 03:06 PM UTC

    Users are reporting that processing times have improved. We are actively working to fully resolve the issue and implement a permanent fix. Thank you for your patience.

  7. monitoring Aug 20, 2025, 03:58 PM UTC

    Update: Processing times have stabilized and we are monitoring the situation.

  8. resolved Aug 20, 2025, 04:35 PM UTC

    Resolved: A permanent fix has been implemented and issue has now resolved.

Read the full incident report →