Ban rate
Ban rate is how often a target site blocks your requests. Proxy Compare publishes no ban-rate figure for any of the 42 providers it tracks, read 5 Oct 2026: it depends on the target rather than the proxy and cannot be measured from outside. We record which targets a provider blocks.
Why it costs you money
A blocked request still moves bytes and still bills. At a thirty percent ban rate you pay for roughly three requests to get two, so your real cost per usable page is about half again your headline rate. It is also entirely target-specific, which is why no comparison table, including ours, can tell you what yours will be.
See it in the data
Related terms
- Success rateThe share of requests that get through. The number that decides everything, and the one no comparison table can give you.
- IP reputationHow a target site scores an address before serving it, based on what that address has done elsewhere.
- CAPTCHA rateHow often a target serves a challenge instead of the page. A softer signal than a ban and it costs the same bytes.
- Residential proxyAn IP address belonging to a real home internet connection, rented by the gigabyte. The hardest type to block and the most expensive.
- Success-only billingCompare successful-request billing policies, including chargeable errors, early cancellations and failed-request protection.
- Every term we define
Questions
What ban rate should I expect from a provider?
Proxy Compare publishes none for any of the 42 providers it tracks, read 5 Oct 2026. It depends on the target site rather than the proxy, it cannot be measured from outside, and every figure a vendor quotes is its own.
How do I measure it for my own job?
Run your own target inside the refund window and count. That is the only measurement that describes your work rather than somebody else's, and it is why the refund window is the real trial.
Do providers say which targets they block?
Some do, and this site records that answer as a checked fact rather than leaving the field blank. Where a provider names nothing, the page says so instead of implying there are no restrictions.