Monthly Proxy Performance Report
Anonymous, voluntarily contributed response-time observations from the standard targets in the Proxy Region Speed Test. No proxy address, port, username, password or custom target is retained in this report.
Destination figures await the publication threshold
Tables are published only after at least 20 contributed runs and 120 default-target observations. These display thresholds do not establish statistical reliability, proxy diversity or coverage over time.
How the monthly report is built
Eligible runs only
A visitor chooses whether to contribute. Only the six standard destinations are counted; edited and custom targets are excluded.
Identity is discarded
The aggregate keeps destination labels, protocol totals, bounded latency bands and response counts. Proxy hosts, ports, credentials, request identities and session data are not copied into it.
Threshold before publication
Results stay hidden until both display thresholds are reached. Requests without a qualifying response have no latency sample; the median is reported as a band rather than an exact time.
What these figures do not prove
A qualifying response completes without a transfer error, returns HTTP 200–499 and has a positive measured request time. This includes HTTP 403, 404 and 429; it does not demonstrate usable website access.
Region names identify the six default destination URLs; their actual serving location is not verified. DNS, CDN and anycast routing can change where a request is served.
Counts may include repeated tests of the same proxy. Proxy diversity and exact per-run dates are not retained. Results describe the observed routes, targets and month; they do not guarantee future speed, uptime, website access or the performance of a specific BuyProxies package.
Use the same proxy, protocol, timeout and destination list across several runs before making a routing decision.