Reliability
Scrapers need requests to complete before speed, targeting, or browser behavior matters.
Connection100HTTP reachability100Success rate75.8%
diagnostic evidenceISP static proxiesmethodology Canonical proxy scorecard v1
NSTProxy · ISP static proxies
Diagnostic only: Baseline gate evidence was not recorded for this publication.
Diagnostic publication. The gate or required dimensions are incomplete, so no Proxy Index score or rank is published.
1
Provider tested
7,510
Network checks
1
Worker region
7
Evidence families
Sample designLast 30 days
Single declared worker vantage region: us-east. Declared concurrency tiers: 6-20.
Metric coverage32/36 measured
Missing metrics are listed explicitly instead of implied.
Measurements from this immutable publication
Not fully benchmarkablepassed 4/6 baseline checks
- Connection
- Exit identity
- HTTP delivery
- ASN lookup
- Geo lookup
- Throughput
Workload success—
Not graded: Baseline gate evidence was not recorded for this publication.
Speed—
Not graded: Baseline gate evidence was not recorded for this publication.
Pool quality—
Not graded: Baseline gate evidence was not recorded for this publication.
Trust and sourcing—
Not graded: Baseline gate evidence was not recorded for this publication.
Session—
Not graded: Baseline gate evidence was not recorded for this publication.
Value—
Not graded: Baseline gate evidence was not recorded for this publication.
The evidence
The measurements behind the dimension grades above: what we ran and what it returned.
Attempt accounting
Checks passed5,690 of 7,510
Legacy publication · no versioned infrastructure-exclusion policy was recorded.
Speed
Latency and transfer speed determine queue depth, worker cost, and retry pressure.
Throughput score100Median latency63 msP95 latency5,844 msBrowser p95 latency585 ms
diagnostic evidencePool quality
Rotating proxy buyers need a pool that is broad enough and not concentrated on a few exits.
Exit identity score100Unique exit IP count8Repeat rate99%Pool churn rate0%
diagnostic evidenceTarget fit
HTTP 200 is not enough; buyers need to know whether representative pages return usable content.
Average target success rate99.2%Average semantic success rate98.7%Average block rate0%Average challenge rate0%
diagnostic evidenceBrowser readiness
Browser-based scraping depends on proxies surviving the same engine stack buyers use.
Browser engine success rate55.3%Browser p50 latency41 msBrowser p95 latency585 msCAPTCHA rate0%
diagnostic evidenceMetadata accuracy
Regional and network targeting breaks when provider metadata is stale or incorrect.
Country accuracy score99.6Region accuracyn/aCity accuracyn/aASN accuracy score99.6
diagnostic evidenceMetric coverage
32 of 36 tracked buyer metrics are measured in this report.
- MeasuredSuccess rate
- MeasuredBrowser engine success rate
- MeasuredBrowser p50 latency
- MeasuredBrowser p95 latency
- MeasuredP50 latency
- MeasuredP95 latency
- MeasuredVantage-region p50 latency
- MeasuredVantage-region p95 latency
Target test outcomes
What happened when this proxy handled representative scraping targets. This is direct evidence behind the workload success dimension, not a buying recommendation.
- Met test thresholdProduct pageObserved 99.3% success · 569 ms p95 latency · 0.0% blocked in this published sample.
- Met test thresholdJSON APIObserved 100.0% success · 407 ms p95 latency · 0.0% blocked in this published sample.
- Met test thresholdHeavy HTML pageObserved 97.9% success · 1,027 ms p95 latency · 0.0% blocked in this published sample.
- Met test thresholdCategory listingObserved 99.2% success · 540 ms p95 latency · 0.0% blocked in this published sample.
- Met test thresholdSearch resultsObserved 99.3% success · 594 ms p95 latency · 0.0% blocked in this published sample.
Recent time series
6 public trend series are available for this report.
- n/aASN accuracy30 data points
- 0%Block rate30 data points
- 28 ms–253 msBrowser p50 latency30 data points
- 139 ms–4,102 msBrowser p95 latency30 data points
- 0%–100%Browser engine success rate30 data points
- 0%CAPTCHA rate30 data points
How this issue was scored, and the fine print
Commercial contextCommercial relationships cannot alter measurements or rank. Any material provider relationship affecting this publication must be disclosed with the report.
Notes on this window
- Low proxy sample · The proxy sample is small; treat provider comparisons as directional.
- Proxy coverage not reported · Proxy coverage details are not present in this report payload.
- Region accuracy not reported · This report is scoped to global, but region accuracy is not measured in the public payload.
- Single vantage region · This report used one declared worker vantage region; treat regional comparisons as untested.
Ranking eligibilityDiagnostic only means the report remains outside the public rank and cannot support comparative placement claims. It observed 8 endpoints against a 5-endpoint minimum and 34 eligible runs against a 2-run minimum, at 100% confidence. Baseline gate evidence was not recorded for this publication.
What the published report carries
The published report carries the eligibility gate, buyer dimensions, metric definitions, sample design, per-page results, and the redaction policy. It withholds credentials, endpoint hosts, raw observations, and raw attempt errors.
Redacted fields: endpoint.id, endpoint.host, endpoint.port, endpoint.proxySourceId, endpoint.tags, proxy credentials, raw observations, raw attempt errors
Follow the evidence past this issue
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.