Use case
Check availability
from a US vantage point.
Probe your own sites and endpoints from outside your network, over a US datacenter route. Status code and timing in one cURL line.
$0.75/GB · US exits · new IP per connection · checked 6 Nov 2026
Example
Status and timing for each URL.
Five public sites through the datacenter tier on 6 November 2026 all answered 200, with total times from 0.6 to 1.6 seconds from our UK test machine.
for u in https://example.com https://github.com https://www.wikipedia.org; do curl -s -o /dev/null -x 'http://YOUR_KEY:[email protected]:3128' \ -w "$u %{http_code} total=%{time_total}s connect=%{time_connect}s\n" "$u" done # https://example.com 200 total=0.64s connect=0.14s # https://github.com 200 total=1.38s connect=0.13s
Good for
Where this earns its place.
Cheap checks you can run from a cron job.
Reachability
Is your site up for visitors outside your own network and your own region?
Redirects and errors
What status does a US client see after your CDN and WAF?
Cost
A probe is a few KB. Reuse one connection per check run to keep it near the size of the page itself.
Limits
Read the numbers with care.
A proxy check is not a measurement of your server alone.
Timing includes the proxy
Total time covers your machine, the proxy and the target. Compare runs to each other, not to a ping.
Not a monitor
There is no scheduling, alerting or history here. Run it from your own cron or monitoring tool.
Datacenter origin
A site that treats datacenter addresses differently will treat the probe differently too.
Answers
A few things worth knowing.
How much does a check cost?+
A new HTTPS connection costs about 4 KB in handshake on top of the page itself. See the calculator.
Does the probe use a new IP each time?+
Each new connection does. That suits a check from many origins. For a steady origin, send the checks on one connection.
Probe from outside.
Same balance as your other proxy tiers. Change the password to datacenter.