ABBYY Cloud OCR Service Status Indicators

Language:
EN
Product-Line:
Cloud OCR SDK
Version:
11
Type:
Business with ABBYY SDKs
Category:
General Features, Recognition, OCR: Speed & Quality

General

ABBYY's Cloud OCR Service is designed to deliver high-quality OCR and the best availability, so that the developers, companies and their end users always have the ability to convert their PDFs or images into valuable documents and data.

But the document processing chain uses different machines and networks - so there is a chance that errors might occur along the way. They might cause slow processing or error messages that state that the service is not available. To be able to fix the problem, it is important to know what might cause the failure.

Multiple, different things can happen so that a cloud service is not available or even not running:

  • the sender computer has no internet connection or DNS problems
  • the SSL encryption can not be established correctly, so no data is sent
  • the data centre is not reachable
  • none of the redundant servers that, for example accept the OCR jobs, are reachable
  • the system has a high load and is busy, so new jobs are rejected
  • the system can not scale up, because of problem in the data center
  • the database that manages the tasks has a problem or is running slow.

… all of them are unlikely but possible. :-(

You can check the health status of the ABBYY Cloud OCR service here: http://status.ocrsdk.com/

This article contains further explanations of the the different ABBYY Cloud OCR SDK health status indicators.

Long Time Statistics

Under http://status.ocrsdk.com/history you can check the general availability of the OCR service over the last days, weeks, months and even years. Just use the arrows on the left side of the timeline.

Cloud OCR availability timeline illustration  - click to see the live data
(Screenshot from 11. August 2016)

Current Status Overview

Here the information that shows the current status of different technical sub systems: Cloud OCR Status Indicators illustration  - click to see the live data
(Screenshot from 11. August 2016)

Incoming Workload

The incoming workload is a ratio of the incoming tasks for a short period of time to an average weekly task amount for similar period.
This number indicates the currently incoming tasks quantity.

Here are some example situations:

  • From 50% to 200% - more or less the same task amount as usual, everything is fine,
  • More than 200% - some users have submitted a lot more tasks than on average, the servers load will increase.

The service's current computing power may be enough to handle the load in case of a short-time workload peak. The service may scale up (automatically) if the workload stays high for long.

Average Time in Queue

This value indicates how long in average it takes before a recently submitted high-priority task processing begins.

Each newly submitted task is enqueued to wait for the processing starts. The ordering of the tasks in queue depends on the task priority: the high-priority tasks processing starts first.

The ABBYY Cloud OCR SDK assigns a priority to every submitted task. The priority is based on the user's current workload profile.
The general rule is: most users have the highest priority. High non-uniform workload with frequent peaks and drops decreases priority.

The average time in the processing queue will increase when more tasks are submitted. The service may scale up if the time in the queue gets longer.

Scaling Status

The backend of the ABBYY Cloud OCR SDK is automatically adding or removing computing resources to be able to process your tasks reliably and in a timely manner.

Here you can see if the service is running fine or if it is scaling up or down.

  • Scaling usually performs automatically (scaling mode is “Auto”) but
  • it may be performed manually (scaling mode is “Manual”) in case of service maintenance.

Server Load

The service's current computing power depends on the incoming workload and may vary significantly.
The servers load is some integral value based on the CPU load of all the servers ABBYY Cloud OCR SDK service currently runs on.

Most of the time the value of servers load is “Average”. If a large amount of new tasks is submitted then servers load may switch to “High” or even “Full” and existing processing capabilities will be increased by adding new processing servers. If no new tasks are coming in, the backend runs idle (servers load is “Low”), so the available computing power for the OCR will be reduced automatically.

The scaling process is automated and the decision making is based on multiple parameters.
Further information about Scalability of the ABBYY Cloud OCR Service

Task Acceptance

The ABBYY Cloud OCR monitoring system submits special,diagnostic recognition tasks on a regular basis to ensure that service will be able to accept and process newly submitted tasks correctly.
The monitoring system is located in a different geographic area to test the international availability, independently from the OCR service location.

  • The green indicator means that everything is fine.
  • The red indicator means that some applications might get errors while submitting new tasks. If this happens, the ABBYY team will be notified.

User Console Availability

Our monitoring system tries to log in into ABBYY Cloud OCR SDK User Console on a regular basis to ensure that User Console is available and users are able to manage their accounts and applications. Monitoring system is located in the geographic area different from the OCR service location.

  • The green indicator means that everything is fine.
  • The red indicator means that User Console is unavailable for some reason. We are already aware of the problem.

SSL Certificate

This indicates that the SSL setup is fine. If a SSL certificate is expired, then the secured https connection cannot be guaranteed and your application might get unexpected error messages from the underlying network layers.

ABBYY will ensure always to provide valid SSL certificates.

Deployment Availability

Shows that:

  • underlying components of the service are up and running,
  • the service deployment is properly published in the Azure data center,
  • the service is reachable via ocrsdk.cloudapp.net domain name managed by Microsoft internal DNS servers.

Deployment Availability via CNAME

Shows that:

  • underlying components of the service are up and running,
  • the service deployment is properly published in the Azure data center,
  • the service is reachable via cloud.ocrsdk.com domain name.

If the indicator is green but you cannot reach the ABBYY Cloud OCR SDK service via cloud.ocrsdk.com then you might face some DNS lookup problems on your network or device.

Database availability

The ABBYY Cloud OCR SDK uses the Microsoft Azure SQL database. The green indicator flag shows that all is fine.

If technical problems with the database subsystem occur, then your communication with the service might slow or you might get some database timeout errors.

Both ABBYY and Microsoft are constantly monitoring the database services to ensure high speed and stability.


Back to: