Single-region deployment means a single point of failure and added latency for distant targets. Multi-region architecture deploys CAPTCHA workers close to target sites, reduces API round-trip time, and survives regional outages.
Architecture Overview
[Task Router]
(Route53 / Load Balancer)
↙ ↓ ↘
[US-East] [EU-West] [AP-Southeast]
Workers Workers Workers
↓ ↓ ↓
[CaptchaAI API] ← shared API key
↓ ↓ ↓
[Central DB / Queue]
(Results aggregation)
Each region runs independent workers. All share the same CaptchaAI API key and push results to a central store.
When Multi-Region Matters
| Situation | Single Region | Multi-Region |
|---|---|---|
| Target sites in one country | Sufficient | Overkill |
| Global target sites | 100–300 ms added latency | Local latency per region |
| 99.9% uptime requirement | Hard to guarantee | Natural redundancy |
| Regulatory data residency | Can't comply | Process locally |
| < 1,000 tasks/hour | Fine | Unnecessary complexity |
| > 10,000 tasks/hour | Scaling limits | Distributes load |
Regional Worker Deployment
Python Worker (Region-Aware)
import os
import time
import requests
API_KEY = os.environ["CAPTCHAAI_API_KEY"]
REGION = os.environ.get("WORKER_REGION", "us-east-1")
RESULT_QUEUE_URL = os.environ["RESULT_QUEUE_URL"]
def solve_captcha(task):
"""Solve CAPTCHA and tag with region metadata."""
start = time.time()
resp = requests.post("https://ocr.captchaai.com/in.php", data={
"key": API_KEY,
"method": task["method"],
"googlekey": task["sitekey"],
"pageurl": task["pageurl"],
"json": 1
})
data = resp.json()
if data.get("status") != 1:
return {
"task_id": task["task_id"],
"error": data.get("request"),
"region": REGION
}
captcha_id = data["request"]
for _ in range(60):
time.sleep(5)
result = requests.get("https://ocr.captchaai.com/res.php", params={
"key": API_KEY, "action": "get", "id": captcha_id, "json": 1
}).json()
if result.get("status") == 1:
return {
"task_id": task["task_id"],
"solution": result["request"],
"region": REGION,
"duration": time.time() - start,
"api_latency_ms": round((time.time() - start) * 1000)
}
if result.get("request") != "CAPCHA_NOT_READY":
return {
"task_id": task["task_id"],
"error": result.get("request"),
"region": REGION
}
return {"task_id": task["task_id"], "error": "TIMEOUT", "region": REGION}
Task Router
Route tasks to the region closest to the target site:
from urllib.parse import urlparse
# Region mapping by target site TLD/domain
REGION_MAP = {
".co.uk": "eu-west-1",
".de": "eu-central-1",
".fr": "eu-west-3",
".jp": "ap-northeast-1",
".com.au": "ap-southeast-2",
".com": "us-east-1", # Default
}
REGION_QUEUES = {
"us-east-1": "sqs://captcha-tasks-us-east",
"eu-west-1": "sqs://captcha-tasks-eu-west",
"ap-southeast-1": "sqs://captcha-tasks-ap-southeast",
}
def route_task(task):
"""Route task to the closest regional queue."""
domain = urlparse(task["pageurl"]).netloc
target_region = "us-east-1" # Default
for suffix, region in REGION_MAP.items():
if domain.endswith(suffix):
target_region = region
break
queue = REGION_QUEUES.get(target_region, REGION_QUEUES["us-east-1"])
send_to_queue(queue, task)
return target_region
Infrastructure Setup
Terraform Skeleton
# Define regions
variable "regions" {
default = ["us-east-1", "eu-west-1", "ap-southeast-1"]
}
# Deploy worker fleet per region
module "captcha_workers" {
for_each = toset(var.regions)
source = "./modules/captcha-worker"
region = each.key
worker_count = var.workers_per_region
api_key_secret_arn = aws_secretsmanager_secret.captchaai_key.arn
task_queue_arn = aws_sqs_queue.tasks[each.key].arn
result_queue_arn = aws_sqs_queue.results.arn
}
# SQS queue per region for task intake
resource "aws_sqs_queue" "tasks" {
for_each = toset(var.regions)
name = "captcha-tasks-${each.key}"
}
# Central result queue
resource "aws_sqs_queue" "results" {
name = "captcha-results-central"
}
Docker Compose (Local Multi-Region Simulation)
version: "3.8"
services:
worker-us:
build: ./worker
environment:
- CAPTCHAAI_API_KEY=${CAPTCHAAI_API_KEY}
- WORKER_REGION=us-east-1
- TASK_QUEUE=redis://redis:6379/0
depends_on:
- redis
worker-eu:
build: ./worker
environment:
- CAPTCHAAI_API_KEY=${CAPTCHAAI_API_KEY}
- WORKER_REGION=eu-west-1
- TASK_QUEUE=redis://redis:6379/1
worker-ap:
build: ./worker
environment:
- CAPTCHAAI_API_KEY=${CAPTCHAAI_API_KEY}
- WORKER_REGION=ap-southeast-1
- TASK_QUEUE=redis://redis:6379/2
redis:
image: redis:7-alpine
Health Monitoring Per Region
JavaScript
const axios = require("axios");
const REGIONS = ["us-east-1", "eu-west-1", "ap-southeast-1"];
async function checkRegionHealth() {
const health = {};
for (const region of REGIONS) {
const endpoint = `https://${region}.workers.example.com/health`;
try {
const start = Date.now();
const resp = await axios.get(endpoint, { timeout: 5000 });
health[region] = {
status: "healthy",
latencyMs: Date.now() - start,
activeWorkers: resp.data.activeWorkers,
queueDepth: resp.data.queueDepth,
};
} catch (err) {
health[region] = { status: "unhealthy", error: err.message };
}
}
return health;
}
// Periodic health check
setInterval(async () => {
const health = await checkRegionHealth();
console.table(health);
}, 60000);
Failover Strategy
When a region goes down, redistribute its tasks:
def failover_check(region_health):
"""Redirect tasks from unhealthy regions."""
healthy_regions = [
r for r, h in region_health.items()
if h["status"] == "healthy"
]
if not healthy_regions:
raise RuntimeError("All regions unhealthy")
redirects = {}
for region, health in region_health.items():
if health["status"] == "unhealthy":
# Pick the healthy region with lowest queue depth
target = min(
healthy_regions,
key=lambda r: region_health[r].get("queue_depth", 0)
)
redirects[region] = target
print(f"Failover: {region} → {target}")
return redirects
Cost Considerations
| Component | Cost Factor | Optimization |
|---|---|---|
| Worker instances | Per-region compute | Auto-scale to 0 when idle |
| Cross-region data transfer | $0.02/GB between regions | Minimize result payload size |
| SQS queues | Per-request pricing | Batch messages where possible |
| CaptchaAI API | Same cost regardless of region | No multi-region premium |
CaptchaAI charges the same rates regardless of worker location — the multi-region cost is infrastructure only.
Troubleshooting
| Issue | Cause | Fix |
|---|---|---|
| One region consistently slower | Distance from CaptchaAI servers | Compare baseline latency; may be expected |
| Task routing sends everything to one region | Domain-based routing too broad | Add more granular routing rules |
| Failover not triggering | Health check endpoint not responding | Ensure health endpoint is on a separate path from worker logic |
| API key balance draining faster | All regions share one key | Expected — monitor aggregate usage |
FAQ
Do I need separate CaptchaAI API keys per region?
No. One API key works globally. Use a single key and track per-region usage through your own metrics.
What's the minimum number of regions for high availability?
Two regions in different geographic areas (e.g., US + EU) provide basic HA. Three regions (US + EU + Asia) cover global availability.
Should I deploy workers in the same region as CaptchaAI's servers?
CaptchaAI's infrastructure handles global requests. Deploy workers close to your target sites for proxy optimization, not close to CaptchaAI.
Related Articles
Next Steps
Deploy CaptchaAI workers across multiple regions — get your API key and build global CAPTCHA solving infrastructure.
Related guides:
Discussions (0)
Join the conversation
Sign in to share your opinion.
Sign InNo comments yet.