Rotating DC
Rotating DC exits come from datacenter ranges. They are the lowest-cost bandwidth we sell and the fastest to connect, and they are also the easiest for a target to identify as automated traffic.
| Billing | By bandwidth |
| Targeting | Country |
| Sessions | Rotating and sticky |
| Protocols | HTTP and HTTPS |
Take your exact username, password, host and port from Rotating DC → Proxy Access in the dashboard.
Connecting
Section titled “Connecting”curl -x USERNAME:PASSWORD@YOUR_HOST:YOUR_PORT https://checkip.amazonaws.comCountry targeting
Section titled “Country targeting”curl -x USERNAME:PASSWORD-country-DE@YOUR_HOST:YOUR_PORT https://checkip.amazonaws.comWhere it fits
Section titled “Where it fits”Rotating DC suits high-volume work against targets with no bot protection: public APIs, your own services, sites that do not check who is asking.
Against anything that inspects traffic, datacenter ranges are the first thing flagged. If you are seeing blocks, the fix is Residential rather than more retries.
What is available here
Section titled “What is available here”Country targeting and sessions. State, city, ZIP, ASN, device OS, IP version, SOCKS5 and the UDP protocols are Residential features.
See Feature availability for the full table.
Was this page helpful?
Thanks. That helps us fix it.