26 February 2013
- Last edited 04 March 2013
Some of you were affected by the ABBYY Cloud OCR SDK service failure occurred on February, 22.
We apologize for potential impact to your business and thank you for your patience. The problem has been already resolved, please see the details below.
Our monitoring service showed that ABBYY Cloud OCR SDK service was not working from 20:30 of February, 22 to 05:45 of February, 23 (UTC). The failure was caused by Windows Azure Storage service SSL certificate unexpectedly expiring worldwide, please see the details here: http://blogs.msdn.com/b/windowsazure/archive/2013/03/01/details-of-the-february-22nd-2013-windows-azure-storage-disruption.aspx
Preventive measures taken by ABBYY Cloud OCR SDK team:
Despite of the fact the failure was caused by issues on Windows Azure side, we understand that to our customers it’s still a problem with our service. In this case the certificate was available for examination to anyone at any time and technically we could have monitored Windows Azure Storage certificate and know it was going to expire in advance and take some proactive action.
That’s why we decided to implement periodic check of SSL certificates of all services we depend upon to prevent such issues from reoccurring. This is not a widely accepted practice but we’re sure it is necessary to implement.
Please be assured that system reliability is a top priority at ABBYY, and we are making continuous improvements to make our service the best on the web.