Documentation Python quickstart Blog Free tools Enterprise solutions hello@quanticdata.ioLog in

Web Unlocker · canary runs

Web Unlocker status

The Web Unlocker is tested on a fixed list of protected pages. This page shows the latest run and the runs before it: how many calls came back with the real page, and how long they took.

88.9%
calls answered with the real page, canary of 11 November 2026
4.1 s
median response on the same run, p95 28.8 s
81
calls on 27 protected targets, 3 runs, default settings

Latest run by protection system

Canary of 11 November 2026: 72 of 81 calls came back with the real page. Each row is one group of the fixed list.

Protected byCallsReal page backSuccessMedianp95
Cloudflare999 of 98.9 s23.7 s
DataDome121191.7%10.4 s28.8 s
Akamai12975%2.4 s53.6 s
PerimeterX / HUMAN999 of 91.8 s14.4 s
Kasada666 of 616.1 s29.3 s
F5 BIG-IP666 of 63.4 s4.3 s
Imperva6583.3%7.4 s11.4 s
AWS WAF6466.7%14.3 s33.6 s
Amazon3266.7%4.1 s7.1 s
Google3266.7%7.5 s10.5 s
Other sites666 of 62 s2.3 s
Reddit333 of 31.7 s5.1 s
All targets817288.9%4.1 s28.8 s

Last runs

Up to the last 12 runs, newest first. A row is added after each run.

DateCallsReal pages backRateMedian
11 November 2026817288.9%4.1 s

How the canary is measured

  • A fixed list of 27 protected pages, grouped by the system that protects them. The groups are the rows of the first table.
  • 3 runs of the whole list, with the default settings.
  • A call is a success when the real page comes back with status 200. A challenge page, an empty body or a timeout counts as a failure.
  • Captcha demo pages run too and are left out of the count: interactive captchas are not solved.

The file behind this page: canary of 11 November 2026 (JSON). What the Web Unlocker is and how to call it: Web Unlocker API and proxy.

Send your own URL through it

Create the free account, open Web Unlocker in the dashboard and send a call. The response says which tier served the page, how many attempts it took and what it cost.

Published · Updated · Read as Markdown