# Pardon Our Interruption: Meaning and Fix

> Pardon Our Interruption is the bot check of Imperva Advanced Bot Protection. Why a browser triggers it, what a visitor can try, and how a script gets the page.

[Home](https://quanticdata.io/) / [Web Unlocker](https://quanticdata.io/web-unlocker/) / Pardon Our Interruption

Block pages · Imperva

# "Pardon Our Interruption": what the message means

"Pardon Our Interruption" is the page that Imperva Advanced Bot Protection shows when something about a browser made a site think it was a bot. It often comes with status `200`, so it passes for a normal answer. A visitor clears it by letting the check run. A script gets the page with one Web Unlocker call.

[Start free](https://app.quanticdata.io/register?next=%2Funlock&utm_source=web-unlocker&utm_medium=website&utm_campaign=unlocker-guides&utm_content=pardon-our-interruption-start-1) · [The Imperva (Incapsula) guide](https://quanticdata.io/web-unlocker/bypass-imperva/)

- **88.9%**: calls answered with the real page across 27 protected targets, Imperva among them, canary of 11 November 2026
- **81**: calls, 3 runs, default settings
- **4.1 s**: median response across the run

- [What you are looking at](https://quanticdata.io/web-unlocker/pardon-our-interruption/#seen)
- [If you are a visitor](https://quanticdata.io/web-unlocker/pardon-our-interruption/#visitor)
- [If your script gets it](https://quanticdata.io/web-unlocker/pardon-our-interruption/#script)
- [Get the page](https://quanticdata.io/web-unlocker/pardon-our-interruption/#call)
- [Measured](https://quanticdata.io/web-unlocker/pardon-our-interruption/#measured)
- [Limits](https://quanticdata.io/web-unlocker/pardon-our-interruption/#limits)
- [FAQ](https://quanticdata.io/web-unlocker/pardon-our-interruption/#faq)

## What you are looking at

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

| Where to look | What it shows |
| --- | --- |
| Status code | Often `200`: the check is served as a normal answer. `403` on a flat refusal. |
| Text on the page | "Pardon Our Interruption. As you were browsing, something about your browser made us think you were a bot." |
| Reasons it lists | Moving through the site at super-human speed, cookies disabled in the browser, or a plugin that stops JavaScript from running. |
| Which system | Imperva Advanced Bot Protection, the bot layer of Imperva. |
| Cookie | `reese84`, written by the check script. `visid_incap_` and `incap_ses_`, followed by the id of the site, where Imperva's firewall runs too. |
| Response headers | `x-iinfo`, and `x-cdn: Imperva` or `x-cdn: Incapsula`, on sites delivered through Imperva. |
| Its sibling | "Request unsuccessful. Incapsula incident ID:" and a number. That one is a refusal by Imperva's firewall layer, not this check. |

![How to read the Pardon Our Interruption page: first the words Pardon Our Interruption with a 200 status, then a block page with three marked zones (status, words, the reese84 cookie), last a card that names the system as Imperva, the kind of block as a bot check served with status 200, the reese84 cookie, and what to do next: let the check run.](https://quanticdata.io/web-unlocker/pardon-our-interruption/diagram.webp?v=20261111b1)

*What the page shows, which system sent it, and what to do next.*

## If you are a visitor

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.

## If your script gets it

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](https://quanticdata.io/web-unlocker/bypass-imperva/).

## Get the page with one call

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:

```bash
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"}'
```

Python:

```python
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])
```

Node.js:

```javascript
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

| Field | What it says |
| --- | --- |
| `blocked` | `false` when the real page came back. `true` only when every attempt met the block; the block page is then in `body`. |
| `vendor` | The system the engine recognised on a blocked attempt. For this page: `imperva`. |
| `blockClass` | Usually `js_challenge` for the check that a browser clears, `captcha` when the page asks a person, and `access_denied` for the incident page. |
| `tier_served` | `tls` for a browser-grade request, `browser` when a real browser had to open the page. |
| `attempts`, `latency_ms` | How many tries the call took and how long it lasted. |
| `cost` | The bytes this call moved and what it was charged. |

## Measured, with a date

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](https://quanticdata.io/web-unlocker/status/).

## What it is for, and what it does not do

- 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.

## Pardon Our Interruption: questions people ask

### What does "Pardon Our Interruption" mean?

It is the bot check of Imperva Advanced Bot Protection, a service sites use to keep automated traffic out. Something about the browser session looked automated, usually blocked JavaScript, refused cookies or very fast browsing, and the site showed this page instead of the content until the check passes.

### Why do I get "Pardon Our Interruption" in Chrome, in Safari or on my iPhone?

The browser is rarely the cause; what it is allowed to do is. Content blockers, strict tracking prevention, private relays and VPNs can stop the check script or the cookie it writes. Allow cookies and scripts for the site, turn the relay or the VPN off for it, and reload.

### Does "Pardon Our Interruption" mean my account is flagged?

No. The check looks at the browser session and the connection, not at your account, and it appears before you sign in as well as after. Clearing it in one browser does not mark you in any way; failing it only means the page asks again.

### How do I fix "Pardon Our Interruption"?

Let the check run: cookies and JavaScript on, script blockers paused for the site, one tab at a time for a minute. If the page returns, try a private window or another network. When it follows you everywhere, the site's own support is the only one who can see why.

### Why does my scraper get status 200 and this page instead of data?

Because Imperva often serves its check with status 200, and an HTTP client cannot run the script that sets the reese84 cookie. Check the text of what came back, not the status. The Web Unlocker does that for you: the answer says blocked: true when the page is the check.

### Is "Pardon Our Interruption" the same as the Incapsula incident ID page?

No, though both come from Imperva. The incident page, Request unsuccessful with an Incapsula incident ID, is a refusal by the firewall layer before any script runs. Pardon Our Interruption is the bot layer asking the browser to prove itself. A site can show either, depending on which layer stopped the request.

## Send the URL that shows you this page

Create the free account, open Web Unlocker in the dashboard and paste the URL into the test box. The answer shows the status, the tier that served the page, the attempts and the cost of the call.

[Start free](https://app.quanticdata.io/register?next=%2Funlock&utm_source=web-unlocker&utm_medium=website&utm_campaign=unlocker-guides&utm_content=pardon-our-interruption-start-2) · [How the Web Unlocker works](https://quanticdata.io/web-unlocker/)

Block pages:

- [Block page dictionary](https://quanticdata.io/web-unlocker/block-pages/)
- ["Please enable JS and disable any ad blocker"](https://quanticdata.io/web-unlocker/please-enable-js-and-disable-any-ad-blocker/)
- ["Access Denied ... on this server"](https://quanticdata.io/web-unlocker/access-denied-on-this-server/)
- [Error 1015](https://quanticdata.io/web-unlocker/cloudflare-error-1015/)
- [Error 1020](https://quanticdata.io/web-unlocker/cloudflare-error-1020/)
- ["Just a moment..."](https://quanticdata.io/web-unlocker/cloudflare-just-a-moment/)
- [Press and hold CAPTCHA](https://quanticdata.io/web-unlocker/press-and-hold-captcha/)
- ["The requested URL was rejected"](https://quanticdata.io/web-unlocker/request-rejected-support-id/)
- [Cloudflare Turnstile](https://quanticdata.io/web-unlocker/cloudflare-turnstile/)
- [CAPTCHA when scraping](https://quanticdata.io/web-unlocker/captcha-when-scraping/)

Guides:

- [Imperva (Incapsula) guide](https://quanticdata.io/web-unlocker/bypass-imperva/)
- [Cloudflare](https://quanticdata.io/web-unlocker/bypass-cloudflare/)
- [DataDome](https://quanticdata.io/web-unlocker/bypass-datadome/)
- [Akamai Bot Manager](https://quanticdata.io/web-unlocker/bypass-akamai/)
- [PerimeterX (HUMAN)](https://quanticdata.io/web-unlocker/bypass-perimeterx/)
- [Kasada](https://quanticdata.io/web-unlocker/bypass-kasada/)
- [F5 BIG-IP and Shape](https://quanticdata.io/web-unlocker/bypass-f5/)
- [AWS WAF](https://quanticdata.io/web-unlocker/bypass-aws-waf/)

Also:

- [Web Unlocker](https://quanticdata.io/web-unlocker/)
- [Status and canary](https://quanticdata.io/web-unlocker/status/)
- [Residential proxies](https://quanticdata.io/residential-proxies/)
- [Mobile proxies](https://quanticdata.io/mobile-proxies/)

## References

By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData · Published 11 November 2026 · Updated 11 November 2026 · [Read as Markdown](https://quanticdata.io/web-unlocker/pardon-our-interruption/index.md)

- [Imperva docs: Cloud WAF error pages and codes](https://docs-cybersec.thalesgroup.com/bundle/cloud-application-security/page/error-codes.htm)
- [Imperva docs: CAPTCHA and challenge behavior](https://docs-cybersec.thalesgroup.com/bundle/cloud-application-security/page/captcha-challenges.htm)
- [Imperva docs: Advanced Bot Protection](https://docs-cybersec.thalesgroup.com/bundle/advanced-bot-protection/page/abp/94085.htm)
- [Web Unlocker in the QuanticData API docs: request, answer, errors and how to read a block (vendor and blockClass)](https://quanticdata.io/docs/#tag/Web-Unlocker)
- [Web Unlocker status: the canary list, the method and every run](https://quanticdata.io/web-unlocker/status/)

---

Source: https://quanticdata.io/web-unlocker/pardon-our-interruption/ · Site index for AI: https://quanticdata.io/llms.txt