Is there an ABBYY outage?
ABBYY status: Systems Active
Last checked: a minute ago
Get notified about any outages, downtime or incidents for ABBYY and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: a minute ago
Get notified about any outages, downtime or incidents for ABBYY and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for ABBYY.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| FlexiCapture Cloud AU | Active |
| FlexiCapture Cloud EU | Active |
| FlexiCapture Cloud EU2 | Active |
| FlexiCapture Cloud US | Active |
| Proof of Identity US | Active |
| Timeline AU | Active |
| Timeline EU | Active |
| Timeline JP | Active |
| Timeline US | Active |
| Vantage AU | Active |
| Vantage EU | Active |
| Vantage US | Active |
View the latest incidents for ABBYY and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 31, 2024, 12:07 a.m.
Description: **Dear Customer,** On July 26, 2024, ABBYY FlexiCapture Cloud EU experienced severe service interruptions. We are pleased to confirm that the issues have been mitigated and the service is now fully functional again. Please review the following incident Root Cause Analysis \(RCA\) information: **Cloud instance** * Europe **Incident timeframe** * July 26, 2024 * 03:18 – 16:30 UTC **Incident status** * Fully mitigated **Customer impact** * Document import, processing, and export were interrupted or experienced significant delays. * Most processing tasks created via the REST API timed out during the incident. * The Web Verification Station could not open verification tasks and displayed the message _“No License. Cannot get license ticket”_. * The Remote Verification Station could not open verification tasks and displayed the message _“Failed to get licensing ticket”_. * The Administration and Monitoring Console displayed the error message _“License has expired or has been deleted”_. **Incident history** * 03:18 UTC: The Processing Server stopped after multiple unsuccessful attempts to restart and automatically resume task processing. * 03:22 UTC: The service health monitoring system was triggered, notifying the on-duty team of a service interruption. * 03:25 UTC: The team began identifying the root cause of the service interruption according to internal playbooks. * 06:00 UTC: After multiple unsuccessful attempts to recover the service, the team started reconfiguring the system to switch to the backup Processing Server. * 06:26 UTC: The switch to the backup Processing Server was completed, heartbeats were restored, and the service returned to normal operation. * 06:37 UTC: Task processing stopped again, triggering another alert from the service health monitoring system. * 08:00 UTC: The team discovered that the Processing Server was stopping due to the licensing service's inability to access the Azure storage holding customer licenses. A shared backup license was used to restore task processing for some customer tenants. * 12:00 UTC: Further analysis confirmed an issue with the Azure storage holding customer licenses. The team created new storage and began transferring customer licenses to it, restoring service operations for the remaining customer tenants. * 16:30 UTC: The license transfer was completed for all customer tenants, fully restoring service operations. The incident was considered fully mitigated. **Root cause** * An outage of the Azure storage holding customer licenses led to the Processing Server stopping after several minutes of operation. **Mitigation measures** * New Azure storage was created, and customer licenses were transferred to this new storage, restoring service operations. **Prevention measures** * Extend the logging capabilities of the licensing service to enable immediate identification of license access issues, as outlined in internal playbooks. * Enhance internal infrastructure to facilitate an immediate switch to a storage-independent backup license in the event of future outages of the Azure storage used for holding customer licenses. We apologize for any inconvenience and most of all, for the potential impact on your business. We are committed to preventing the issue in the future and will continue working on improving the infrastructure and our monitoring solutions. Thank you for using ABBYY FlexiCapture Cloud! If you have any questions or feedback, please feel free to contact our support team via the [Help Center](https://support.abbyy.com) portal. Yours faithfully, [ABBYY FlexiCapture Cloud](https://www.abbyy.com/flexicapture-cloud-login) Team
Status: Postmortem
Impact: Critical | Started At: July 26, 2024, 7:10 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: July 26, 2024, 6:21 a.m.
Description: The incident is resolved, mistakes were fixed.
Status: Resolved
Impact: Major | Started At: July 11, 2024, 6 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 17, 2024, 10:44 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
