GitHub →

I buy proxies. I test them.
I publish what happens.

Bought 6 top residential proxies, ran the same script against the same 20 sites, 2,400 requests each in ~4 hours per provider. 24 hours of testing to find:

Lowest latencyBest for concurrent scrapesCheapest cost per successful requestHighest success rate
See the report (Sep 2026) →Read the latest review

Mobile, ISP, datacenter, and the API tiers come next.

What's the latest proxy report?

24 hours of testing. Six residential proxy providers, one after another.

Four hours per provider on a stable 100 Mbps line. Same script, same 20 sites, no parallel runs so nothing shares bandwidth. Each row shows reliability, speed, cost, and the highest concurrency the provider survives. Open Review or Report on any row for the details. Full protocol: tests page →

#ProviderSuccessTimeoutp50 latencyCost / 1kCeilingDetails
01decodo76.9%0.1%1,191 ms$0.63c8Review · Report
02dataimpulse76.8%2.8%2,114 ms$0.15c16Review · Report
03oxylabs72.4%0.3%1,180 ms$0.86c8Review · Report
04webshare71.7%0.5%1,242 ms$0.51c8Review · Report
05shifter70.1%4.5%2,402 ms$0.33c8Review · Report
06byteful69.3%1.4%961 ms$0.46c8Review · Report

Ran on Sep 15-16, 2026

What all tests did I do?

Seven tests. Same script for every provider.

Every headline number on this site comes from one of these. Full protocol: how I am testing proxies →

01

Concurrency

How the network holds as parallel sessions ramp: 1 → 4 → 8 → 16.

metric: max concurrency clean
02

IP rotation

How often IPs actually change across the pool.

metric: unique IPs per 1k
03

Sticky sessions

Does a sticky session actually hold the same IP over time?

metric: session hold rate
04

IP pool

Country and ASN distribution. Uniqueness and repetition.

metric: ASN + country spread
05

Geography

Does a proxy tagged as US actually egress from the US?

metric: geo match %
06

Latency

Connect + response time under load. p50 and p95.

metric: ms per request
07

Reliability

Success, block, and timeout across the full 20-site set.

metric: success / block / timeout %
What's coming soon

Use-case-based tests.

Stress-testing proxies in popular real-world use cases, across all types of proxies. Full timeline: roadmap →

SERP trackingPrice monitoringE-commerce (Amazon)JS-heavy scrapingAds monitoring
Muninder Adavelli
Why I am doing this

Because "millions of IPs" tells you nothing.

I've been using proxies for scraping and SEO work for years. Every provider says the same things: millions of IPs, fast, high success rate, rotating residential. None of those tell you what happens when you actually put eight concurrent sessions through the network on a site behind PerimeterX.

So I started testing them myself. What began as a script to check if a provider could handle my SERP scraper turned into twenty sites and roughly 2,400 requests per provider, a ranking that moves month to month. proxy.report is where I publish what I find. Read the full story →

Latest activity

What's changed lately.

Each entry ships as a git commit. See the full changelog →

Reviews

  • Oxylabs review

    residential run with the highest per-request cost of the six

    2026-09-18
  • Shifter review

    sticky-session model; steady c8 with a 4.5% timeout rate

    2026-09-18
  • Decodo review

    fastest of the six with the lowest timeout rate

    2026-09-18
  • Byteful review

    snappiest median latency, ceiling at c8

    2026-09-18
  • Webshare review

    mid-pack success, cheap enough to justify a look

    2026-09-18
  • DataImpulse review

    cheapest per-request cost, tied for top success

    2026-09-17

Latest posts & research

FAQ

Questions I've had to answer.

Is this site paid by proxy providers? +

Some providers are affiliate partners. Some aren't. Rankings come from the same test data everything else uses. If a provider I earn from loses on the numbers, they lose on the page. Every provider page tells you whether I make money if you buy through it. See the full affiliate log.

How fresh is the data? +

I re-run the full 20-site test monthly. Every review cites the specific run it was written against. When numbers change, the review and the changelog both update.

Why only residential proxies right now? +

I started with residential because my first use case was SERP tracking. Mobile, ISP, datacenter, scraping APIs, and SERP APIs are all coming. Each provider page will grow a new report tab as the data lands.

Can I re-run these tests myself? +

The test scripts are being cleaned up for public release. Once they're on GitHub, you can run the same script against the same sites and check whatever I've written.

What providers are being tested next? +

See the roadmap. Short answer: more providers, more proxy types, and use-case-specific essays.