Reliability
Scrapers need requests to complete before speed, targeting, or browser behavior matters.
Connection100HTTP reachability100Success rate47.4%
measuredA score appears only when every dimension with a positive weight has comparable evidence. Saved on this device.
Speed 94.7 · Workload 26.4.
The report has enough execution coverage for publication review.
Single declared worker vantage region: us-east. Declared concurrency tiers: 6-20.
Missing metrics are listed explicitly instead of implied.
2 providers · ranked by proxy index score · click a row to open the full record
Strong baseline proxy health for scraping transport
The proxy selection performed well on canonical connection, identity, HTTP reachability, geo, and ASN checks.
Leads the cohort on geo-accuracy (99.6%) and ASN grade A, 0.2 points clear of Bart ISP.
Open NSTProxy's page →Six buyer dimensions, each built only from measurements with real spread — not the commodity plumbing checks. Grades are 0–100; a dash means we do not yet score that dimension for this line.
Mean of overall request success rate and browser-engine success rate (whichever are present), scaled to 0-100.
Success rate 0.47 ratio · Browser engine success rate 0.05 ratio
P95 latency banded 100 at <=200ms falling linearly to 0 at >=2000ms, averaged with throughput MB/s graded as min(100, throughput_mbps * 10) when present.
P95 latency 392 ms · Throughput 113.08 Mbps
Mean of pool-freshness signals scaled to 0-100: exit-IP entropy (higher better), the inverse of repeat rate, and the inverse of top-exit-IP share. Requires observed exit IPs.
Unique exit IP count 10 count · Repeat rate 0.99 ratio · Top exit IP share 0.10 ratio · Exit IP entropy 1 score
Not graded — IP enrichment (usage type and reputation risk) is not available for this sample.
Not graded — No sticky-session persistence attempts were run for this sample.
Not graded — No pricing snapshot was available to compute cost per successful request or GB.
The measurements behind the dimension grades above — what we ran and what it returned.
Scrapers need requests to complete before speed, targeting, or browser behavior matters.
Latency and transfer speed determine queue depth, worker cost, and retry pressure.
Rotating proxy buyers need a pool that is broad enough and not concentrated on a few exits.
HTTP 200 is not enough; buyers need to know whether representative pages return usable content.
Browser-based scraping depends on proxies surviving the same engine stack buyers use.
Regional and network targeting breaks when provider metadata is stale or incorrect.
29 of 36 tracked buyer metrics are measured in this public payload.
How the line handled representative scraping targets — direct evidence behind the workload success dimension.
6 public trend series are available for this report.
The public report exposes the eligibility gate, buyer dimensions, metric definitions, sample design, target-class rollups, and redaction policy. It does not expose credentials, endpoint hosts, raw observations, or raw attempt errors.
Redacted fields: endpoint.id, endpoint.host, endpoint.port, endpoint.proxySourceId, endpoint.tags, proxy credentials, raw observations, raw attempt errors
This issue is one window on the field. Open a provider's standing record for the full history, or read the methodology behind every number.