Limits and quotas
Concurrency ceilings, timeouts and account limits.
| Limit | Value | Adjustable |
|---|---|---|
| Concurrent connections (residential) | unlimited | — |
| Concurrent connections (mobile, ISP) | unlimited | — |
| Concurrent connections (shared datacenter) | 250 per sub-user | Yes, on request |
| Request timeout | 180 s | Yes, per request via -timeout- |
| Sticky session duration | 120 minutes | No |
| Proxy users per account | 500 | Yes, on request |
| API requests | 600 / minute / key | Yes, on enterprise plans |
| Whitelist entries | 50 per sub-user | Yes, on request |
| Max request body | 100 MB | No |
Per-request timeouts
The gateway waits 180 seconds by default before giving up on a target. Slow targets sometimes justify that; most workloads are better served failing fast and retrying on a different exit.
text
wp-acc4821-country-us-timeout-15 # give up after 15 secondsTraffic ceilings you set yourself
Account and sub-user limits are the safety net against a runaway loop. Set both a daily and a monthly figure, and an alert threshold below the hard stop, so you hear about it before service cuts out.
- Daily GB — resets at 00:00 UTC.
- Monthly GB — resets on your billing anniversary, not the first of the month.
- Spend limit — a currency ceiling across every product, useful when you are mixing bandwidth and per-IP billing.
- Alert thresholds — email or webhook at 50%, 75% and 90% by default.
Hitting a limit is not a suspension
Requests return 402 while the limit is exceeded, and resume the moment the window rolls over or you raise the ceiling. Nothing is deleted and no credentials are revoked.
Something inaccurate?Tell support