How we tested
We bought a residential package from each of 12 providers at the price listed on its website and ran every test through the same scripts. We tested between 5 and 8 October 2026. Bright Data and Byteful were not included because they require identity verification (KYC).
- Servers. Three Hetzner cloud servers in Germany, the US and Singapore. Each ran the same scripts on a fixed schedule (cron, UTC).
- Countries. 12 exit countries: US, DE, GB, FR, ES, BR, IN, PL, UA, TR, VN, ID.
- Providers. Decodo, Oxylabs, Evomi, SOAX, DataImpulse, Rayobyte, ProxyEmpire, Webshare, NodeMaven, IPRoyal, Floppydata, Geonode.
Tests
- Infrastructure test (Success Rate, Latency, Duplicate Rate). Each server sent 100 requests per provider and country through rotating residential proxies to a Cloudflare trace endpoint, at 08:00 and 20:00 UTC every day. Success Rate is the share of requests that returned a valid answer. Latency is the median and 90th percentile (P90) of response time on successful requests. Duplicate Rate is 1 minus unique IPs divided by successful requests. Confidence intervals use the Wilson 95% method.
- Target test (Target Success Rate). Amazon (US, DE, GB) and Wikipedia were requested at 11:00 and 23:00 UTC with a plain HTTP client that uses a Chrome TLS fingerprint and no JavaScript. A request counts as a success only when the real page came back, not a CAPTCHA or block page.
- Sticky session test (Sticky Session Stability). Each run opened 8 sticky sessions per provider and checked them every 30 seconds for 30 minutes. A session counts as stable if the IP never changed and at least 90% of checks were answered during the first 25 minutes.
- Time to first byte. On 7 October we measured TTFB with curl: 10 requests per provider, country and server.
- IP quality. We checked a sample of 300 unique IPs per provider (3,600 in total) with the Scamalytics API (fraud score, proxy detection) and an ASN check with IPinfo (residential or ISP = not flagged as datacenter and not on a hosting network).
- Cost per Successful Request. We recorded each provider's price per GB and read the traffic counter in each provider's dashboard on 8 October at 14:50 UTC. Cost per Successful Request = price per GB × GB used ÷ successful requests of all our tests up to that moment. We report it per 1,000 requests.
Limitations and disclosure
Disclosure. We operate Floppydata, one of the 12 providers in this test. We ran it through the same scripts, servers and schedule as the other 11 providers, and report its results, including the weaker ones, in the same way. Our Floppydata account was topped up by the company, but the price used in the cost calculation is the public price of $1.00/GB, the same for all users. Floppydata is the lowest in sticky stability (47.3%) and second-lowest in Success Rate (98.0%), and we say so in the key findings.
- Short period. The test covers four days (5–8 October 2026). Provider quality can change with pool size, time of day and load.
- Three test locations. All requests came from servers in Germany, the US and Singapore. Results from other locations or networks may differ.
- Plain HTTP client for targets. The Amazon and Wikipedia test used no JavaScript and no browser. Amazon results moved between about 28% and 83% from run to run for every provider, so they should be read as a comparison inside this test, not as an absolute success rate.
- One source for IP quality. Fraud Score and Proxy Detection Rate come from Scamalytics, and network names (ASN) and geolocation from IPinfo, on a sample of 300 IPs per provider. Another database would rate the same IPs differently.
- Prices as paid. Prices are what we paid for each package, which differ in size (from 2 GB to 50 GB), tariff and tax. ProxyEmpire's $8.47/GB includes tax ($7.00 without). Evomi's price is converted from EUR.
- Cost measured by counters. Cost per Successful Request uses each provider's own traffic counter, read on 8 October at 14:50 UTC. Counters may count traffic differently (1 GB can be 1,000 or 1,024 MB), which moves the result by a few percent.
- Sticky sessions need each provider's own format. We used the session format from each provider's documentation. A different parameter setup may give a different result. For Floppydata the format was corrected on 6 October, and earlier sessions are excluded.
- Not tested. Bright Data and Byteful were left out because they require identity verification. Mobile and datacenter proxies are not covered.
- Not a recommendation. The data compares providers on a specific set of tests. Choose by the task you run.
Raw data and reproducibility
The test used five Python scripts, one for each test: infrastructure (bench.py), targets (targets.py), sticky sessions (sticky.py), TTFB (ttfb.py) and IP quality (ipquality.py), plus analyze.py, which builds the results workbook from the raw CSV logs. The workbook contains the full per-server, per-country and per-run tables, confidence intervals and the method notes.
Because Floppydata is one of the tested providers, we publish the raw data, the scripts and the results workbook on GitHub, so anyone can check the numbers. The raw logs are anonymized: every exit IP address is replaced by a keyed hash. The same address always gets the same hash, so unique-IP counts, Duplicate Rate and sticky-session IP changes can be recomputed, but the addresses cannot be recovered. No credentials, API keys or server addresses are published.
- Repository. Floppydata/residential-proxy-benchmark-2026: data, scripts and the method in one place.
- README. What was tested, how the data was anonymized, column reference and how to recompute the results.
- Raw request logs. 87 CSV files, one row per request or check (about 636,000 rows), split by test server: us, de, sg.
- IP quality results. Per-provider aggregates only. Individual IPs and raw Scamalytics responses are not published.
- Scripts. The five test scripts and analyze.py. Running analyze.py on the published CSV files gives the same tables as the published workbook, except IP quality.
- Results workbook. results.xlsx with all tables, confidence intervals, per-run trends and method notes.
Code is under the MIT licence, data and workbook under CC BY 4.0. To run your own test you need your own proxy credentials and, for IP quality, your own Scamalytics and IPinfo access.