ProxiesScraping

Stop Comparing Proxy Prices: Calculate Cost Per Successful Request (2026)

SC
Data Scientist
Published
July 26, 2026
Updated
August 30, 2026
Reviewed by
Read Time
4 min read
€ per GB is an input; € per successful page is the decision

Open ten residential proxy homepages and you will see the same contest: who can print the lowest €/GB. Procurement spreadsheets lock onto that number. Pipelines then quietly burn money on retries, CAPTCHAs, and soft-blocked pages that still meter bandwidth.

Aethyn's pricing concept is different on purpose: transparent per-GB rates, two reputation tiers, and a bias toward success rate on your targets over vanity pool size. This article turns that into arithmetic you can put in a spreadsheet.

The sticker price is not the bill you pay

Residential traffic is billed by bytes. Failed attempts often still transfer challenge HTML, redirects, or partial bodies. Engineering time spent debugging a "cheap" pool is real cost too — but even on bandwidth alone, success rate multiplies the sticker.

Failed attempts still meter bytes
Challenge HTML is not free. Failed attempts still meter residential gigabytes.
Important

[!IMPORTANT] Define success as usable content. A HTTP 200 that is a CAPTCHA, consent wall, or empty shell is a failure for cost accounting. Status-code vanity metrics make bad pools look affordable.

A 200 with a CAPTCHA body is a failure
A 200 with a CAPTCHA body is a failure. Status-code vanity makes cheap pools look affordable.

The formula

From a real sample run on your targets:

  1. page_bytes — average response size of content-verified successes
  2. page_GB = page_bytes / 1e9
  3. sticker = € per GB (e.g. Premium €2.00, Elite €4.50 — see pricing)
  4. success_rate = content_ok / attempts (0–1)
  5. € per successful page ≈ (page_GB × sticker) / success_rate

A lighter form some teams use for ranking providers: effective €/GB ≈ sticker / success_rate. That ignores page weight but still ranks pools correctly when page size is similar across vendors.

Divide sticker by content-verified success rate
Divide sticker by content-verified success rate. Premium is €2.00/GB; Elite is €4.50/GB.

Worked example (illustrative)

Assume a catalog page averages 500 KB (0.0005 GB) of useful HTML when it succeeds.

PoolStickerSuccess rate€ / successful page
"Bargain" residential€1.50/GB50%(0.0005 × 1.50) / 0.50 = €0.00150
Aethyn Premium€2.00/GB90%(0.0005 × 2.00) / 0.90 ≈ €0.00111
Aethyn Elite€4.50/GB97%(0.0005 × 4.50) / 0.97 ≈ €0.00232

On this soft target, Premium wins on effective cost even though it is not the cheapest sticker — and the €1.50 pool loses because half the bandwidth buys garbage. On a hard retail domain where Premium falls to 60% and Elite holds 95%, redo the row: Elite often becomes the cheaper successful page despite €4.50/GB.

Pro Tip

[!TIP] Pro Tip: Compute the table per domain, not as one global average. A pipeline can look fine overall while one money site quietly doubles your effective cost.

How this maps to Aethyn's Premium vs Elite

QuestionAnswer
What are we optimizing?Cost per verified success, not lowest €/GB
When is Premium right?High volume, open/moderate targets — Premium at €2.00/GB
When is Elite right?Hard anti-bot, city/ISP needs, success-rate recovery — Elite at €4.50/GB
How do we decide?Trial both on the same URL sample; keep each source on the cheapest tier that holds

That is the same philosophy as the residential proxy pool size myth: we would rather be measured on reputation, consented sourcing, and success you can verify than on an unaudited IP count. Benchmarks and market context: 2026 proxy benchmarks, statistics 2026.

Keep each source on the cheapest tier that holds
Keep each source on the cheapest tier that holds. Premium for volume; Elite when success-rate recovery pays for itself.

What to exclude from the spreadsheet (or add deliberately)

  • Retries — if your client retries three times on 403, bandwidth multiplies; fold retry policy into measured success_rate or into total GB
  • Headless browsers — Playwright pages weigh more than requests HTML; measure the stack you will run in production
  • Human time — a pool that needs constant session babysitting loses even if €/success looks fine on paper
  • Opaque "contact sales" pricing — if you cannot plug a number into the formula, you cannot forecast. Transparent per-GB is a feature.

A 30-minute measurement protocol

  1. Pick 3–5 representative URLs (easy, medium, hard)
  2. Send a few hundred requests through the candidate pool with Python Requests or Playwright as you will in prod
  3. Mark content-verified successes; record GB from the dashboard meter
  4. Plug into the formula; compare Premium vs Elite vs any incumbent
  5. Route each host to the winning tier

Use the provider checklist for sourcing and support questions the formula does not cover.

The takeaway

€/GB is an input. € per successful page is the decision. Aethyn publishes clear Premium and Elite rates so you can run that math without a sales call — then prove it on your own targets.

Compare Premium & Elite pricing

FAQ

Common questions about this article

Why is the lowest price per GB a bad way to buy residential proxies?
Because failed, challenged, and soft-blocked responses still consume bandwidth (and engineering time) without delivering usable data. A €1/GB pool at 50% true success can cost more per good page than a €4.50/GB pool at 95% success. Compare cost per successful, content-verified request — not the marketing sticker.
What is the formula for effective proxy cost?
Estimate average bytes per successful page from a real sample, convert to GB, multiply by your €/GB rate, then divide by success rate (content-verified successes ÷ attempts). Equivalently: effective € per success ≈ (page_GB × €/GB) ÷ success_rate. Always define success as the page content you need — a 200 with a CAPTCHA body is a failure.
How do Aethyn Premium and Elite fit this model?
Premium starts at €2.00/GB for high-volume, cost-sensitive collection on open and moderately defended targets. Elite is €4.50/GB for harder exits where reputation and city/ISP targeting lift success rate. Run both on a sample of your domains; keep each source on the cheapest tier that sustains its success rate.
Does a 200 OK count as success for cost calculations?
No. Soft blocks return 200 with challenge pages, empty shells, or geo-wrong content. If you count those as successes, your effective cost looks artificially low while your dataset (or SERP report) is poisoned. Assert on expected selectors, page weight floors, or known content markers.
How does this relate to pool-size marketing?
Headline IP counts do not appear in the cost formula. Concurrent quality where you need it, and measured success on your targets, do. That is why we refuse to lead with a vanity pool number — see our pool-size myth article — and ask you to measure instead.
Share this article

Guides, integrations & docs

Continue reading

Measure effective cost on your targets

Transparent €2.00/GB Premium and €4.50/GB Elite. Run a free trial, count content-verified successes, and pick the tier that wins on cost per success — not sticker price.

Back to all articles