Frequently asked questions

A topped-up balance and one proxy user from your dashboard. Point any HTTP client at our gateway host and port and pass the proxy user's login and password with standard proxy authentication. The docs have copy-paste examples for five languages.

No. Everything speaks the standard HTTP proxy protocol, so curl, your browser, your scraping framework and your existing HTTP library work unchanged.

Yes. Give each job or teammate its own proxy user, so you can disable one without disturbing the rest and usage is attributable.

Append the cc key and a two-letter country code to your username. Germany is cc followed by de.

Yes, on premium residential. Add st with a state code and ct with a city code; a city always needs its state. The other products sell country targeting and return 400 AVO_TARGETING_NOT_SUPPORTED for a state or city key.

Add a session id of your choosing (1 to 32 letters and digits) and every request carrying it reuses the same exit address. Add a lifetime in whole minutes to set how long that may hold: up to 55 minutes on residential and mobile, 115 minutes on premium residential. It is a ceiling, so the address rotates at or before it. Change the id to get a different address immediately.

The gateway rejects the request with 400 AVO_BAD_TARGETING. The message does not repeat your username, so check the keys against the targeting page. A key you sent is never ignored.

By bytes through the gateway in both directions, aggregated per hour and per proxy user. Your dashboard shows the same counters your balance is drawn down by.

Requests stop with 403 AVO_QUOTA and resume within a couple of seconds of a top-up. Nothing renews unless you switch on auto top-up, and there is no overage bill.

Unused GB are refunded on request within 14 days of the top-up. GB already used are not refunded. If we take a product off sale, we move your GB to another product or refund them. Closing your account forfeits any remaining balance, so ask for a refund first.

Not yet. We will publish one when it is measured from the gateway's own health data. Until then, section 6 of the terms says what we promise.

One proxy user may hold up to 5,000 connections open at once, 2,000 on mobile, and the rate at which it opens new connections is capped as well. Clients that reuse connections do not reach either. Exceeding one returns 429 AVO_TOO_MANY_CONNECTIONS, which clears within the minute.

The request could not be completed. Retry it with a short backoff, and send us the details if one destination fails repeatedly.

Email us or use the contact form. Include the timestamp, the proxy user's login (never the password) and the exact error code.

Anything illegal where you are or where the destination is: intrusion, credential stuffing, fraud, spam, distributing malware, harassment, or attacking infrastructure. We terminate accounts that cross that line.

Only against systems you own or have written permission to test. Volume aimed at someone else's infrastructure is an attack.

We do not sell customer data. A small number of infrastructure partners process it for us under data-processing agreements, for hosting, payment processing and email delivery. We also disclose data when the law requires it. Our privacy page lists what we store and for how long.