"Pardon Our Interruption": what the message means

The page explains itself more than most block pages do, but it never says who wrote it. These are the marks of Imperva.

The page gives its own reasons, and they are the real ones: the check needs JavaScript and cookies, and it reacts to speed. Nothing is wrong with your account. The decision is about this browser session.

• Enable cookies and JavaScript for the site, then reload. The check writes a cookie when it passes; if the browser refuses it, the page comes back.
• Pause extensions that block scripts or trackers on that site.
• Slow down for a minute. Many pages or tabs of the same site opened at once is what the page means by super-human speed.
• Turn off the VPN or proxy, or switch network.
• Try a private window or another browser: a clean session starts the check from zero.
• If the page follows you across browsers and networks, contact the site. Only its team can see why its bot protection flags you.

Imperva checks in two layers, and this page belongs to the second. Knowing which layer stopped a request tells you what to change.

• The firewall layer classifies the client on the first request: the address, the handshake, the headers. Its refusal is a different page, the one with the Incapsula incident ID.
• The bot layer loads a script that inspects the browser and writes the reese84 cookie. A client that never runs it receives "Pardon Our Interruption" on every request.
• Speed is a signal: many requests in one session, without the pauses a person makes, bring the page back even after a pass.
• The status hides it: the check often comes with 200, so a scraper that looks only at the status stores the interruption page as if it were data.

The whole picture of the system is in the guide: Bypass Imperva Incapsula When Scraping.

Send the URL to the REST endpoint. With mode: "auto", the default, the first attempt is a browser-grade request from a residential IP. When Imperva serves its check, a real browser opens the page, lets the script finish and returns the page behind it; a refused attempt is retried on a fresh exit.

curl -X POST https://app.quanticdata.io/api/v1/scraper/unlock \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/", "country": "us"}'

import requests

r = requests.post(
    "https://app.quanticdata.io/api/v1/scraper/unlock",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={"url": "https://example.com/", "country": "us"},
    timeout=130,
)
page = r.json()["payload"]
print(page["status"], page["blocked"], page["latency_ms"], page["cost"])
print(page["body"][:500])

const res = await fetch("https://app.quanticdata.io/api/v1/scraper/unlock", {
  method: "POST",
  headers: { Authorization: "Bearer YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({ url: "https://example.com/", country: "us" }),
});
const { payload: page } = await res.json();
console.log(page.status, page.blocked, page.latency_ms, page.cost);
console.log(page.body.slice(0, 500));

Read blocked in the answer rather than status: it is true when the page that came back is the check, whatever status the site used.

What the answer tells you

The canary of 11 November 2026 runs a fixed list of 27 protected targets, Imperva sites among them: 72 of 81 calls came back with the real page, with a median response of 4.1 s.

A call counts only when the answer is 2xx and carries the real page, not a challenge. The list, the method and every run are on the Web Unlocker status page.

• It is for pages anyone can open in a browser without signing in: prices, listings, reviews, search results, public profiles.
• Challenges that need no human input are handled by the browser tier. An interactive captcha that asks a person to click, pick images or type is not solved: the answer comes back with blocked: true and blockClass: "captcha", so your code can skip the page or try later.
• It does not log in for you and it does not create accounts. Pages behind a login stay behind it.
• Whether you may collect a page depends on the terms of the site and on the law that covers the data. A protection system does not change that, in either direction.