Limits & best practices

Limits at a glance#

Limit	Value
API requests	60 per minute per API key
Manual mobile rotations	at least 10 s apart, per proxy
Rotation link calls	30 per minute per link and source IP
Automatic rotation interval	2–60 minutes, or off
Sticky residential session	1–30 minutes
Residential endpoints per API call	1,000
Residential traffic validity	90 days from purchase
Mobile proxies per order	1–50
Static ISP IPs per order	1–250
Active API keys	10 per account
Bandwidth (mobile, static)	unlimited

There is no hard cap on concurrent connections per proxy. The practical limit is the link itself, which is why the guidance below matters.

Concurrency#

Product	Sensible concurrency	Why
Mobile 4G/5G	5–20 connections per proxy	One radio link shared by all your connections. More threads mean slower responses, not more throughput.
Static ISP	20–100 per IP	Gigabit uplink; the limit is usually the target site's tolerance for one IP.
Rotating residential	50–500 per account	Each request goes to a different peer. Scale with the number of targets, not per IP.

Start low, measure the median response time, and increase concurrency until it starts to climb.

Timeouts#

Connect timeout: 10 s. Mobile and residential connections take longer to establish than data-centre ones.
Read timeout: 30–60 s for pages, longer for downloads.
API calls: 30 s; rotation calls up to 45 s (the response waits for the new IP).

Retries#

Error	Retry?
`407` from the gateway	No — fix credentials, renew the proxy or correct the residential flags.
`402` from the residential gateway	No — top up traffic.
`502` / `504` from the gateway, connection reset	Yes, after 1–5 s. On residential, the retry automatically uses another IP.
`429` / `403` from the target site	Slow down. On mobile, rotate; on residential, the next request already has a new IP.
API `429`	Wait `Retry-After` seconds.
API `5xx`	Exponential backoff, 3–5 attempts.

Being a good citizen of the target site#

Blocks are triggered by behaviour far more often than by IP type:

respect robots.txt where your use case allows and keep request rates per site reasonable;
reuse cookies and sessions like a real browser would instead of starting cold on every request;
send consistent headers — a desktop Chrome User-Agent with a mobile carrier IP is fine, but a missing Accept-Language is not;
cache what you have already fetched.

Troubleshooting checklist#

Test the line with cURL from the same machine: curl -v -x http://user:pass@host:port https://api.ipify.org.
407? Check credentials, the proxy's expiry date, the IP whitelist, and residential flag spelling.
Timeouts on a mobile proxy? Check the status page for the country's gateway, then rotate once — a modem on a congested cell gets a fresh session.
Slow residential responses? Try -country-eu or a larger city; small cities have fewer peers online.
Still stuck? Open a ticket with the proxy id or the residential username, the target URL and the UTC time of a failed request.

Acceptable use#

Proxuno proxies may not be used for: attacks of any kind (DDoS, credential stuffing, brute force, vulnerability scanning of systems you do not own), spam or bulk unsolicited messaging, fraud, payment testing with stolen cards, distribution of malware, access to child sexual abuse material, or any activity that is illegal in the country of the exit IP or in your own. Outbound SMTP on port 25 is blocked on every gateway.

Abuse reports are sent to [email protected]. We investigate each report using proxy traffic metadata only — timestamps, source and destination addresses, byte counts — which we keep for 30 days. We never record the content of your traffic. Confirmed abuse leads to suspension and, for strictly forbidden uses, termination without refund. The full text is in the Acceptable use policy.