CLI · Tools
buyproxy test
Generate a proxy and prove it works — shows the exit IP, location, network and latency.
Usage
$ buyproxy test [product] [-c US] [--plan <id>]test is the quickest way to check your bandwidth, your plan and a target country are all working. It generates one HTTP proxy, opens a tunnel through it and asks a public IP-information service who it sees — so you find out about a problem before a long job does.
Options
| Option | What it does |
|---|---|
| [product] | Which plan to test, by product key or part of its name. |
| --plan <id> | A specific plan id. |
| -c, --country <XX> | Test an exit in this country (two-letter code). |
Plus the global options (--json, --key, --no-color, --help).
How it works
- Picks a plan the same way
generatedoes and generates one HTTP proxy (SOCKS5 isn't tested). - Connects to the proxy, authenticates with its credentials, and tunnels to
ipinfo.io. - Requests
https://ipinfo.io/json*through the proxy* and times the whole round trip. - Prints what the outside world saw.
That request is a few kilobytes of your bandwidth, and it's the only thing sent to a third party — to the IP-information service, from the proxy's address.
Examples
Test the default plan
$ buyproxy test╭─ Proxy check ───────────────────────────────────────╮
│ Exit IP 203.0.113.42 │
│ Location Austin, Texas, US │
│ Network AS7922 Comcast Cable Communications, LLC │
│ Latency 842 ms │
│ Product Core Residential │
╰─────────────────────────────────────────────────────╯Test Japan on Premium
$ buyproxy test premium -c JPHealth check in a script
$ buyproxy test --json | jq -e '.ok'Exits non-zero if the proxy fails, so it works in cron jobs and CI.
JSON output
{
"ok": true,
"latencyMs": 842,
"body": { "ip": "203.0.113.42", "city": "Austin", "region": "Texas", "country": "US", "org": "AS7922 Comcast Cable Communications, LLC" }
}On failure ok is false and error explains why.
Troubleshooting
| You see | How to fix it |
|---|---|
| The proxy didn't answer: proxy rejected the credentials (407) | Generate again; if it persists, check buyproxy whoami that you're using the right account. |
| The proxy didn't answer: timed out | Check you have bandwidth left (buyproxy balance) and that the product supports the country you asked for. |
| You don't have any bandwidth yet. | Top up with buyproxy topup first. |
Tips
A latency over ~1.5 s is shown in amber — normal for some residential routes, worth knowing before a latency-sensitive job.
Run it right after a top-up to confirm the new bandwidth is live.
Related commands
Was this page helpful?