Feature availability
One table, generated from one config file. Every feature page in these docs renders its availability strip from the same source, so this page and those strips cannot disagree.
Targeting
| Feature | Residential | Rotating ISP | Rotating DC |
|---|---|---|---|
| Country | ✓ | ✓ | ✓ |
| State & region | ✓ | — | — |
| City | ✓ | — | — |
| ZIP code | ✓ | — | — |
| ASN & carrier | ✓ | — | — |
| Device OS | ✓ | — | — |
| IP version | ✓ | — | — |
Sessions
| Feature | Residential | Rotating ISP | Rotating DC |
|---|---|---|---|
| Rotating (new IP per request) | ✓ | ✓ | ✓ |
| Sticky sessions | ✓ | ✓ | ✓ |
| Strict sticky sessions | ✓ | — | — |
| Session duration | ✓ | — | — |
Protocols
| Feature | Residential | Rotating ISP | Rotating DC |
|---|---|---|---|
| HTTP & HTTPS | ✓ | ✓ | ✓ |
| SOCKS5 | ✓ | — | — |
| SOCKS5 UDP | ✓ | — | — |
| HTTP/3 (QUIC) | ✓ | — | — |
| STUN | ✓ | — | — |
Access
| Feature | Residential | Rotating ISP | Rotating DC |
|---|---|---|---|
| IP whitelisting | ✓ | ✓ | ✓ |
| Sub-accounts | ✓ | ✓ | ✓ |
Reading this table
Section titled “Reading this table”Residential supports everything. Rotating ISP and Rotating DC support country targeting, sessions, and HTTP.
Sending an unsupported option is not an error. It is ignored, and you get a normal exit for that product. If you were relying on it to narrow your traffic, the response will not tell you it was dropped, so check this table before building on an option.
Was this page helpful?
Thanks. That helps us fix it.