Solves, 24 hours
22,242,367
132,934,551 over 7 days
Active tasks
1,150
1 pending · 1,149 processing
Total node load
57.4%
Across active processing capacity
Active nodes
66
66 visible nodes
Volume
Completed solves
- 24 hours
- 22,242,367
- 7 days
- 132,934,551
- 30 days
- 468,319,226
- All time
- 8,750,851,948
Last three minutes
Average solve time
| Captcha | Avg time |
|---|---|
| interstitial | 11.5s |
| turnstile | 5.2s |
Processing network
Node load
1–10 of 66
- 85%
1f614eda
active85% - 90%
f3669a09
active90% - 100%
8fd6b3f9
active100% - 75%
bee6d90e
active75% - 85%
f6fddbf9
active85% - 26%
e808c7d8
active26% - 100%
d45388a2
active100% - 100%
a38ec91d
active100% - 90%
63793062
active90% - 90%
ebbb43c1
active90%
Metric guide
Reading the operational signals
Use solve volume, queue depth, node load, and recent latency together before changing submission rates.
Solve activity
Completed totals cover 24-hour, 7-day, 30-day, and all-time windows. Recent solve times vary by challenge and demand.
Capacity and queues
Sustained node load together with growing pending work is a stronger queue-pressure signal than a short traffic spike.
Automated monitoring
Combine this page with the API health endpoint and task-level error handling for reliable alerting.
Building automated health checks?
Use the health endpoint for availability and continue handling validation, balance, and task errors separately.