Documentation

Rotating Residential Proxies

Use Rotating Residential proxies from the Thunderproxy dashboard via configurable proxy strings or exported proxy lists.

Export pages

Rotating Residential gives you access to a residential proxy pool through dashboard-generated connection settings. You do not receive a fixed set of assigned IPs. Instead, you configure how traffic should be routed — location, rotation mode, sessions, and protocol — and use the output in your tools.

This page covers what the product provides, how to choose between access methods, and how to troubleshoot common issues.

What you get

When you purchase a Rotating Residential subscription, the dashboard gives you:

  • One set of subscription credentials (username and password).
  • A gateway host and port for HTTP or SOCKS5 where available.
  • Controls to set geotargeting, rotating or sticky sessions, and other routing options.
  • Two equal ways to use that access: Quick Access (live proxy string) and Export (generated proxy-list lines).

Unlike Static ISP, where each row in the proxy table is a dedicated IP with its own username suffix, Rotating Residential routes requests through a shared pool based on the settings encoded in your username or exported lines.

Each plan includes a bandwidth allowance valid for a fixed period. All proxy traffic counts against that allowance. When you purchase a new plan, you receive new credentials — renewing or scaling an existing plan keeps the same credentials when possible.

Open the subscription

  1. Open the Thunderproxy dashboard.
  2. Go to Subscriptions.
  3. Open your Rotating Residential subscription.

The page shows usage, renewal controls, Quick Access, and Export.

Choose your access method

Both paths use the same subscription credentials and routing rules. Pick the one that fits your workflow.

MethodBest for
Quick AccessSingle-app setup, manual copy-paste, testing with cURL, or tools that accept one proxy string.
Export (Proxy list)Browser profiles, scrapers, or workers that need many lines at once — for example separate sticky session usernames.

Changing settings in one area does not invalidate the other. You can copy a proxy string from Quick Access and export a file with different geotargeting at the same time, as long as the subscription is active.

Quick Access

Use the Quick Access card for live connection settings.

The default tab is User:Pass unless IP authentication is already configured. In this tab you can:

  • Choose geotargeting.
  • Choose rotating or sticky mode.
  • Copy username, password, host, and port.
  • Copy a full proxy string.
  • Copy an example cURL command.
  • Reset the proxy password if needed.

Geotargeting

If geotargeting is available for your subscription, use the location controls at the top of the card.

Rotating Residential can support:

  • Any country (worldwide).
  • A specific country.
  • State and city targeting where available.

The dashboard regenerates the username preview as you change location settings. Copy the updated username after choosing the location you want.

Rotating vs sticky sessions

ModeUse when
RotatingYou want each request to use a different IP from the pool.
StickyYou want one or more stable sessions for a longer flow.

When you choose Sticky, set the number of sessions you want. The dashboard generates usernames with -sid- session IDs. Different session IDs can be used concurrently in separate apps, workers, or browser profiles.

Sticky sessions on residential peers are best-effort. We keep the same IP while that peer stays online, but real home connections can go offline before a TTL ends. TTL sets the maximum time we try to keep a sticky session before rotating; it is not a guarantee that the same IP stays available for the full period. If the current peer drops, traffic is routed to another available IP.

Copy connection details

In Authorisation, copy these fields into your tool:

  • Username
  • Password
  • Host
  • Port

The dashboard also shows a full proxy string:

http://username:password@host:port

Use Show more formats if your app needs:

  • user:pass@host:port
  • host:port:user:pass
FormatWhen to use
URI (http://user:pass@host:port)Apps that accept a single proxy URL.
user:pass@host:portTools that split host and credentials differently.
host:port:user:passLegacy scrapers and some automation clients.

See Proxy String Formats for format examples and common import mistakes.

Test with cURL

The dashboard includes an example cURL command. Copy it and run it in a terminal to confirm that the proxy works before adding it to your application.

Use the example as a known-good test because it is generated from the currently selected host, port, username, password, and protocol.

See Test a Proxy with cURL for manual user:pass and IP-auth test commands.

IP authentication

If your subscription supports IP authentication, the IP Auth tab appears in Quick Access.

Use it to add trusted IP addresses. After saving, requests from trusted IPs can use the generated connection settings without entering user:pass credentials in tools that support IP-auth flows.

With sticky sessions and IP Auth, you can connect from a trusted IP using the gateway host and port without username and password. Geotargeting and session settings are kept in the cloud. Use Rotate IP or the rotate URL when you need to change the current sticky address.

Export

Use the Export card when you need a file of generated proxy lines.

Open the Proxy list tab, choose location, rotation, session count, protocol when available, format, and file extension, then click Download.

Exported lines are generated from the same subscription access as Quick Access. Each line encodes the routing options you selected at export time. Store the export with the settings you used when you need reproducible jobs.

The API link tab provides a URL your software can call to load proxies from Thunderproxy. Changes in the dashboard sync to the API every few moments.

When to re-export

Re-export after:

  • Changing country, state, or city.
  • Switching between rotating and sticky mode.
  • Changing the number of sticky sessions.
  • Switching protocol between HTTP and SOCKS5.
  • Changing export format.

See Activity and Renewals for how subscription status affects exported lists.

Protocol

HTTP is the default. If SOCKS5 gateway is available on your subscription, the dashboard shows a protocol selector in Quick Access and Export.

Switching protocol updates the shown port and proxy string. Copy or export again after changing protocol.

See HTTP vs SOCKS5 Proxies before changing protocol in an app or imported list.

Activity, renewals, and bandwidth

Proxy access works only while the subscription is active and has remaining bandwidth.

  • An expired subscription or zero remaining data can stop authentication even if copied credentials are still formatted correctly.
  • Renewing usually keeps the same credentials — you do not need to reconfigure tools unless you change settings or reset the password.
  • Unused bandwidth expires when the subscription period ends.

Enable automatic renewal in the dashboard if you want uninterrupted access.

Troubleshooting

  • If authentication fails, copy the password again from the dashboard.
  • If targeting fails, switch geotargeting back to any location and test again.
  • If a sticky session stops behaving as expected, generate a fresh sticky username or use Rotate IP.
  • If the proxy works in the dashboard cURL example but fails in your app, compare the app's proxy format with the dashboard formats.
  • If usage is exhausted or the subscription is expired, proxy access stops even if exported lines still look valid.
  • Re-export the proxy list and retry with a fresh line after changing settings.

For detailed checks, see Authentication Failed, Location Targeting, Sticky Sessions, and Exported List Not Working.

For subscription status checks via API, see Account API and Activity and Renewals.