Proxy Networks

Rola IP currently provides three main rotating proxy networks: Rotating Residential, Rotating Datacenter, and Mobile IP. All three networks can be used with the proxy connection details generated in the dashboard, and all support username parameters for country-level location and session control. Rotating Residential also supports state and city targeting.

Network Types

Type	Source	Main Strength	Best For
Rotating Residential	Real home broadband networks	Real-user environment, higher trust, broad compatibility	Account registration, social media, e-commerce, data collection
Rotating Datacenter	IDC / cloud provider networks	Lower cost, fast, suitable for bulk tasks	Low-risk scraping, bulk access, testing
Mobile IP	Real mobile carrier networks	Mobile network identity, high trust	Mobile apps, high-risk accounts, mobile testing

How to Connect

See Quick Start for the full configuration flow.

If you need to specify a location or keep a session for 1-120 minutes, combine the account name, location parameters, and sessiontime as described in Parameters. Rotating Residential supports country, state, and city; Rotating Datacenter and Mobile IP currently support country only.

Configuration Pages

Network	Configuration Page	Notes
Rotating Residential	Open Residential Settings	Best for real-user environments and higher-success workflows
Rotating Datacenter	Open Datacenter Settings	Best for low-risk, high-volume, cost-sensitive tasks
Mobile IP	Open Mobile IP Settings	Best for mobile workflows and stricter risk-control scenarios

TIP

The three configuration pages follow the same logic: choose or enter an account name, add the location parameters supported by the selected network and sessiontime when needed, then copy the generated proxy connection details into your client or code.

Selection Guide

• Choose Rotating Residential when you need a real-user environment.
• Choose Mobile IP when you need stronger mobile network trust.
• Choose Rotating Datacenter when the task is cost-sensitive and has low IP reputation requirements.
• Use country for country-level targeting on all three networks. Only Rotating Residential supports state and city.
• Use different sessionid values when running multiple independent exits; add sessiontime when a workflow needs to keep one session for 1-120 minutes.
• Append -f-1 when every request should rotate IP, such as test-country-us-f-1.

TIP

sessionid is the value after the underscore in the account name. For example, in test_1, the sessionid is 1. Different sessionid values are independent sessions and map to different IPs. sessiontime is measured in minutes and supports 1-120 minutes. -f-1 rotates IP on every request and is not recommended for workflows that need login-state continuity.