Web Unlocker · status
This page shows how the Web Unlocker did on its latest canary run: how many calls went to bot-protected pages, how many brought back the real page and how long the median call took. The numbers refresh from the live service when the page opens, and the method is written out below.
Latest run: 2026-11-11. 27 pages, 3 runs each.
The latest canary runs reported by the live service, newest first.
| Date | Calls | Real pages | Success | Median time |
|---|---|---|---|---|
| 2026-11-11 | 81 | 72 | 88.9% | 4.1 s |
Generated from the canary run of 2026-11-11, 3 runs on the same targets. Interactive captcha pages are excluded.
| Anti-bot system | Success | Median time | Calls |
|---|---|---|---|
| Cloudflare | 100% | 8.9 s | 9 |
| DataDome | 91.7% | 10.4 s | 12 |
| Akamai | 75% | 2.4 s | 12 |
| PerimeterX / HUMAN | 100% | 1.8 s | 9 |
| Kasada | 100% | 16.1 s | 6 |
| F5 BIG-IP | 100% | 3.4 s | 6 |
| Imperva | 83.3% | 7.4 s | 6 |
| AWS WAF | 66.7% | 14.3 s | 6 |
| Amazon | 66.7% | 4.1 s | 3 |
| 66.7% | 7.5 s | 3 | |
| Other sites | 100% | 2.0 s | 6 |
| 100% | 1.7 s | 3 |
These numbers come from our own canary, a run we repeat on the same pages. Customer traffic is never part of it.
Latest run: 2026-11-11. 27 pages, 3 runs each: 81 calls, 72 real pages (88.9%).
A call counts only when the Web Unlocker returns the real page with status 200. A challenge page, an empty body or a timeout is a failure, whatever the HTTP status says.
It is the rule the product applies to your own calls: a page that is still blocked after every attempt is flagged as blocked, with the block class and the protection system named, and is never handed over as a success.
Operational means the latest run is recent and its success rate is at the level we treat as healthy. Degraded means the latest run is recent and came in below that level.
The state is read from the live service when the page opens. When there is no recent run, or the live service does not answer, the page shows no state and keeps the numbers of the last run it has.
Every number here is produced by our own canary calls. No customer request, URL or account is part of this page.
The Web Unlocker page prints the run it was built with; this page asks the live service for the latest one, so after a new run the figures here are the newer ones.
A canary describes our list of pages, not yours. On your own targets every answer of the REST endpoint carries the status, the blocked flag with the block class and the protection system, the tier that served the page, the attempt log and the cost. The forward proxy reports the same verdict in the x-qp-unlocker-blocked and x-qp-block-class headers.
Count those fields in your logs and you have the success rate on your own pages, by site and by protection system.
The state at the top of this page is read from the live service when you open it. With a recent canary run it says Operational or Degraded, and the table of recent runs lists the calls, the real pages returned, the success rate and the median time of each run.
With a canary: a fixed list of bot-protected pages, grouped by protection system and called through the Web Unlocker in repeated runs. A call is a success only when the real page comes back with status 200. Challenge pages, empty bodies and timeouts are failures; captcha demo pages are run but left out of the count.
No. Every number comes from our own canary calls. Customer requests, URLs and accounts are never published.
The canary measures a fixed list of pages. Your targets, countries and request types are your own, so your rate will differ. Every answer tells you whether the page was blocked, by which protection system and after which attempts, so you can measure your own mix.
The canary runs on a schedule, and this page reads the latest result from the live service each time it is opened. The date of the run is printed next to the numbers.
Skip the marketing. QuantumProxies.io publishes a machine-readable site map, Markdown for every page, a free MCP server, and APIs billed from the same balance as your proxies.
Connect in one command: npx -y quantumproxies-mcp