Service Status

History
ABBYY Cloud OCR SDK Status

ABBYY Cloud OCR SDK Status Reports

This page contains reports about the problems with ABBYY Cloud OCR SDK service and corrective and preventive measures taken.


Smooth Operation: 56 Days     Last 6 months average availability: 99.994%
Available Slowdown Interruption

Details of the May 25, 2017 Partial Service Interruption

Posted on May 25, 2017, last updated on June 23, 2017

Duration: May 25 2017 01:45 – May 25 2017 02:00 UTC
Scope: Some user affected

On May 25th between 1:45 and 2:00 UTC some users might have experienced problems with submitting tasks / downloading results due to partial short-time Azure Blob Storage outage.

Read more

Details of the September 27, 2016 Service Interruption

Posted on September 27, 2016, last updated on October 11, 2016

Duration: September 27 2016 12:19 – September 27 2016 13:13 UTC
Scope: All users affected

Between 12:19 and 13:13 UTC on September 27th, 2016 ABBYY Cloud OCR SDK was unavailable due to unexpected loss of connectivity to the SQL Azure database server, probably caused by database server's IP address change.

Read more

Details of the September 9, 2016 Service Interruption

Posted on September 9, 2016, last updated on September 12, 2016

Duration: September 9 2016 15:12 – September 9 2016 16:48 UTC
Scope: All users affected

ABBYY Cloud OCR SDK service was unavailable between 15:12 and 16:48 UTC on September 9th, 2016 due to a networking issue occurred at the Microsoft Azure side. According to Microsoft Azure status history, multiple Azure services hosted in West Europe and Northern Europe were impacted by this networking issue caused by routing misconfiuration.

Read more

Details of the March 7, 2016 Service Interruption

Posted on July 4, 2016

Duration: March 7 2016 15:10 – March 7 2016 17:10 UTC
Scope: All users affected

Between 15:10 and 17:20 UTC on March 7th, 2016 Cloud OCR SDK was declining new tasks due to database performance degradation caused by unexpected usage pattern. Users submitting tasks during this period of time were getting error notifications.

Read more

Details of the February 20, 2016 Service Interruption

Posted on July 4, 2016

ABBYY Cloud OCR SDK service was unavailable between 16:15 and 20:45 UTC on February 20th, 2016 due to a major database service performance issue which was linked to a resource-intensive maintenance operation. Normally the database service performance is appropriately increased before the maintenance operation and then lowered to normal once the maintenance operation is completed.

Read more

Details of the February 17, 2016 - February 24, 2016 Issue with Certificates

Posted on July 4, 2016, last updated on July 12, 2016

Duration: February 17 2016 00:00 – February 24 2016 00:00 UTC
Scope: Some users affected

From February 17th till February 24th some users might have experienced problems with establishing secure connection over SSL. The issue affected only particular platforms, including, but not limited to iOS.

Read more

Details of the February 7, 2016 - February 8, 2016 Service Slowdown

Posted on July 4, 2016

Duration: February 7 2016 19:50 – February 8 2016 02:22 UTC
Scope: Some users affected

Between 19:50 on 07 FEB 2016 UTC and 02:22 on 08 FEB 2016 UTC some ABBYY Cloud OCR SDK users experienced a delay in their tasks processing due to Azure Network Infrastructure issues in Western Europe, where our Service is hosted. Temporary unavailability of Azure resources affected scalability of ABBYY Cloud OCR SDK. The problem was mitigated at around 02:30 UTC and shortly thereafter the Service began to scale up. Following that the Service capacity was increased and by 04:15 UTC the accumulated queue had been fully processed.

Read more

Details of the November 24, 2015 Service Interruption

Posted on July 4, 2016

ABBYY Cloud OCR SDK service was unavailable between 05:01 and 06:54 UTC on November 24th, 2015 due to a networking issue occurred at the Microsoft Azure side: multiple Azure services in West Europe were impacted by this networking issue.

Read more

Details of the October 26, 2014 - October 27, 2014 Service Slowdown

Posted on July 4, 2016

From yesterday’s evening we have problems with Windows Azure Management API, it is not working correctly. As a result, we can’t scale up our service and you can see ABBYY Cloud OCR SDK service slowdown. We are trying to fix this with the highest priority, but we are still waiting for Windows Azure team to fix the issue.

Read more

Details of the October 20, 2014 - October 21, 2014 Service Slowdown

Posted on July 4, 2016

ABBYY Cloud OCR SDK service was processing incoming tasks very slowly from October 20, 20.00 UTC to October 21, 07.00 UTC.

Read more

Details of the October 20, 2014 Service Slowdown

Posted on July 4, 2016

ABBYY Cloud OCR SDK service was processing incoming tasks very slowly from October, 20 14.00 to 18.00 UTC

Read more

Details of the December 12, 2013 Service Slowdown

Posted on July 4, 2016

ABBYY Cloud OCR SDK service was very slow between 10:45 and 13:00 UTC on December 12th, 2013. Slowdown happened due to some not yet fully identified problem in accessing SQL Azure from our service, we are still doing research to understand all details. After that our development team initiated scaling out in manual mode, and ABBYY Cloud OCR SDK returned to it’s normal processing speed. At about 14:30 UTC the same day we’ve registered that the problem with SQL Azure disappeared, and since that time our service is running in normal mode.

Read more

Details of the April 16, 2013 Service Interruption

Posted on July 4, 2016

ABBYY Cloud OCR SDK service was unavailable between 07:16 and 07:23 UTC on April 16th, 2013. All requests submitted during that time received status “ProcessingFailed” or HTTP 500 “Internal server error” was returned. The issue was linked to SQL Azure connection timeouts. After getting the errors, the processors were automatically restarted, and after 15 minutes the server was working normally again.

Read more

Contact Support

Need to talk to support? Contact Us