Hi,
Over 2 years of operation, we have had no incidents which made reCAPTCHA completely unavailable. Using a distributed network of redundant datacenters has allowed us to achieve this record of uptime.
There have been a few incidents where reCAPTCHA was inaccessible from a specific region -- for example, when dealing with a specific ISP that had connectivity problems. These types of problems are typical of all internet sites and when they occur tend to affect many websites.
In terms of monitoring our service, we suggest that you focus not on attempting to make sure
our service is working, but that
your service is working. For example, if your site typically registers 10,000 users per hour (each of which must solve a CAPTCHA), you should monitor that number. Failures often occur in strange ways (for example, we've seen cases where newly introduced code creates a problem even though our servers are working fine). Rather than try to anticipate all the possible modes of failure, you should monitor the metrics that are important to your profitability.
One other thing you can use is checking the occurrence of network errors when contacting
api-verify.recaptcha.net (eg, network not reachable errors, or HTTP return codes like 404 or 500). This might indicate a local routing issue between you and reCAPTCHA. As long as calls to the verification service work, additional checks (such as trying to generate CAPTCHAs) are very much redundant -- our code has many checks to make sure that as long as our servers are reachable, we are able to serve CAPTCHAs.
- Ben
--
reCAPTCHA: stop spam, read books
http://recaptcha.net