Rotating proxies hand out a new exit address automatically, so you do not manage lists of IPs yourself. Choose a rotating mobile pool for high-trust traffic or an unlimited residential pool for steady, heavy volume.
With static proxies you hold a list of IPs and decide when to switch. A rotating proxy moves that logic to the provider: your client connects to a single gateway and the exit address changes automatically.
For rotating mobile plans, the provider states that the IP changes automatically, but its descriptions differ on the exact timing (per request in some wording, about once a minute in another). If rotation timing is critical to your workflow, confirm it with sales before ordering.
02
Mobile or residential for rotation?
Rotating mobile pools come from carrier networks and tend to carry the highest trust, but they are Turkey-based, metered by GB, and slower. They suit social and app traffic where trust matters most.
Unlimited residential plans trade metering for time: you pay for a day, a week or a month and send as much traffic as the link carries. They suit continuous crawling and monitoring across many countries, where counting gigabytes would be the main constraint.
Use cases
Where it fits best
Continuous crawling
Run steady, high-volume collection without watching a data meter on the unlimited residential plans.
High-trust social and app traffic
Use rotating mobile IPs when a carrier address is the most believable option.
Short, intense projects
Buy a single day or week of unlimited residential access for a burst of work.
Setup
Set up Rotating Proxy
01
Choose mobile or residential
Pick by trust needs, geography and whether you want GB-metered or time-based billing.
02
Order the plan
Press Buy for the plan size or time period you need.
03
Connect to the gateway
Enter the endpoint and credentials from the panel; no IP lists to maintain.
04
Check rotation behavior
Send several requests to an IP-check endpoint and confirm how often the exit address changes.
A rotating proxy is a gateway: you connect to one fixed host and port, authenticate, and the provider forwards your traffic out through a member of its pool. What changes between exits is the connection, not your configuration. For HTTPS, your client sends a CONNECT request and the gateway builds a tunnel; everything inside that tunnel, including many individual HTTP requests, leaves from one exit address because the gateway cannot see inside the encrypted stream. In most gateway designs, therefore, the unit that rotates is the TCP connection.
This matters for the provider’s mobile descriptions, which disagree: one wording says the address changes per request, another says about once a minute. The two behave very differently in practice. With a per-connection design, a client that opens a fresh connection per request sees a new address each time, while a client reusing a keep-alive connection sees one address for many requests; with a time-window design, the address holds for the window whatever your client does. Treat the exact interval as unconfirmed and ask sales on WhatsApp before building a workflow around it.
Only the rotating mobile interval is in question; the unlimited residential plans are listed with both sticky and rotating sessions.
02
Measuring rotation yourself before you commit volume
You can settle the question empirically with a small pack. Using the 5 GB rotating mobile pack (a one-time purchase of 540 TRY), request an IP-echo endpoint through the gateway about once a second for three minutes, logging the returned address and a timestamp. Run the loop twice: once opening a new connection for every request, and once reusing a single keep-alive connection. Each probe costs a few kilobytes even with a fresh TLS handshake, so 180 probes use roughly one megabyte of the pack (an illustrative estimate).
A table can only summarize, so run the test at the time of day you will actually work: carrier networks vary in load, and a single quiet-hour run proves little. Repeats are normal. The pool is finite, so the same address can return later, and you should not assume uniqueness unless you de-duplicate on your side. Keep the log, because it is the most useful evidence to show sales if the behavior differs from what you were told or from what the provider’s materials suggest.
What the log shows
Likely design
What it means for you
New address on every new connection, one address on a reused connection
Per-connection rotation
Disable keep-alive when you want a fresh address; reuse connections when you want to hold one.
Both runs hold an address for about a minute, then change
Time-window rotation
Plan flows to finish inside the window; bursts will share one address.
The address changes only some of the time
Mixed or pool-dependent behavior
Log for longer, then ask sales to explain the pattern you observed.
The address never changes during the test
Sticky behavior or a configuration problem
Check the endpoint and credentials, then report it to sales with your log.
03
Cost model: one-time packs, unlimited plans and break-even volume
The table converts each rotating mobile plan to a per-GB rate. Compare unlimited with packs: stacking 10 GB packs at 990 TRY costs 99 TRY per GB, so 5,500 TRY buys about 55 GB, and above that monthly volume unlimited is cheaper. A single 100 GB pack costs 7,100 TRY, which is 1,600 TRY more than the monthly unlimited plan, so unlimited is cheaper if you would use that data within a month. The pack could win only if its data stays usable for months; this site does not say how long a pack remains valid.
Unlimited does not mean unlimited throughput. At the lowest listed speed, 15 Mbps, a fully saturated link moves about 6.75 GB per hour, or roughly 162 GB in 24 hours; at the top listed speed, 75 Mbps, the ceiling is about 33.75 GB per hour. Real use sits far below these ceilings, but the arithmetic shows two things: a 5 GB pack can disappear in under an hour of heavy transfer at the low end, and an unlimited plan is bounded by the link long before it is bounded by a data meter.
Unlimited rotating residential is priced by time: 5,000 TRY per day, 20,000 TRY per week or 75,000 TRY per month, which is 5,000, about 2,857 and 2,500 TRY per day respectively. The residential GB plans fall from 70 TRY per GB at 5 GB to 30 TRY per GB at 300 GB (9,000 TRY). At 30 TRY per GB, one day of unlimited breaks even at roughly 167 GB, a week at about 667 GB and a month at 2,500 GB; below those volumes the GB plans are cheaper, though each GB plan tops out at 300 GB.
Rotating mobile plan
Price (TRY)
Billing
Per GB (TRY)
5 GB
540
One-time
108
10 GB
990
One-time
99
100 GB
7,100
One-time
71
Unlimited
5,500
Monthly
Cheaper than stacked 10 GB packs above about 55 GB per month
Prices are in Turkish lira, excluding taxes, as listed on the order pages. Unlimited plans may carry fair-use terms that are not published here, so ask sales.
04
Sessions, retries and concurrency for rotating traffic
Decide per task whether identity should persist. Stateless fetches, such as public product or search result pages, tolerate a new address on every connection. Multi-step flows such as login, cart and checkout break when the exit changes mid-flow, because the server sees one session cookie arriving from different networks. The unlimited residential plans are listed with sticky sessions, which is the tool for this case. The method for requesting one is provider-specific and not described on this site, so use what your panel or sales give you instead of guessing a syntax.
Design retries around connections, not addresses. When a request fails with a 429, a 403 or a timeout, close the connection and retry on a new one after a short randomized delay, for example one to three seconds growing with each attempt (illustrative). Under a per-connection design this lets the gateway give you a different exit. Cap retries per URL, since every retry on a metered mobile pack spends data. Keep concurrency modest: dozens of parallel connections, not hundreds, especially on mobile links listed at 15 to 75 Mbps, where congestion shows up as timeouts rather than errors.
Log every request with its status, byte count and exit address, so you can see which part of a job consumes data and which targets cause failures. Watch for pages that pull heavy assets: blocking images, fonts and video in a headless browser commonly reduces transfer by a large factor. Mobile exits sit on carrier networks, where many real subscribers commonly share addresses through carrier-grade NAT, so abusive traffic can harm other people’s connections as well as your own standing; use these pools only for lawful work within each site’s terms, and respect the rate limits those sites publish.
Before you order
Buyer’s checklist
0 / 6
Troubleshooting
When something does not work
The five symptoms we see most often, what usually causes them and the quickest fix.
Likely cause
Your client reuses one keep-alive connection, and the rotation unit is the connection or a time window rather than the request.
Fix
Close the connection after each request or open a new session per request, then log the exit IP for three minutes to see the real interval. If it never changes, send your log to sales.
Likely cause
The exit address changed in the middle of the flow, so the site saw one session coming from two networks.
Fix
Use a sticky session on the residential plans, finish the flow on a single connection, or confirm the mobile rotation interval with sales and complete each flow inside it.
Likely cause
Pages pull images, scripts and video, retries and TLS handshakes add overhead, and traffic is typically metered in both directions.
Fix
Block images, fonts and video, cache repeat fetches, cap retries, and keep your own byte counter, since this site does not describe how remaining data is displayed for rotating packs.
Likely cause
Credentials with special characters were pasted into a URL without encoding, or SOCKS5 was tried on a plan where only HTTP and HTTPS are confirmed.
Fix
Percent-encode the password, use an http:// proxy URL for rotating mobile, and ask sales to confirm SOCKS5 before using it on unlimited residential.
Likely cause
Too many concurrent connections for a mobile link listed at 15 to 75 Mbps, or a congested exit.
Fix
Reduce concurrency to a few dozen connections, raise timeouts, retry on a new connection with backoff, and test at the hours you will really work.
Glossary
Terms you will meet
Gateway endpoint
The single host and port you connect to; the provider routes each connection to an exit in its pool. Providers also call this a backconnect proxy.
Sticky session
A mode that keeps the same exit address for a period so multi-step flows are not interrupted. It is listed for the unlimited residential plans.
Rotation interval
The rule that decides when the exit changes, for example on every new connection or after a time window. For rotating mobile plans it is not confirmed on this site.
Keep-alive
An HTTP feature that reuses one TCP connection for many requests. With per-connection rotation, it means many requests share one exit address.
Carrier-grade NAT (CGNAT)
A carrier technique that lets many subscribers share a small set of public IPv4 addresses. It is why mobile exits are shared with real users.
Exit IP
The public address a target sees for your request. On rotating plans it can change between connections, so log it with every result.
FAQ
Rotating Proxy — frequently asked questions
How often do the IPs rotate?
Rotation is automatic. For rotating mobile plans, the provider’s descriptions differ on the timing, so confirm the interval with sales if it matters. Residential plans support rotating and sticky sessions.
What is the difference from the residential GB plans?
GB plans meter data on a monthly allowance. The unlimited plans here meter time (day, week or month) instead of gigabytes.
Can I pay month by month on rotating mobile?
The 5, 10 and 100 GB packs are one-time purchases. The unlimited rotating mobile plan is billed monthly.
Which protocols work?
HTTP and HTTPS are confirmed for rotating mobile. For unlimited residential, protocol details are not published, so ask sales to confirm SOCKS5 support if you need it.
Can I target a country?
Residential plans list global geo-targeting. Rotating mobile is Turkey-based.
Can I top up a rotating mobile pack when the data runs out?
The 5, 10 and 100 GB packs are one-time purchases, so when one is used up you order another from its order page. Whether leftover data from an old pack carries over is not documented on this site, so assume it does not and ask sales if it matters.
Does unlimited rotating mobile mean unlimited speed?
No. Traffic is not metered, but the link is: the listed speed is 15 to 75 Mbps, so a fully saturated link at the low end moves roughly 162 GB in 24 hours. Fair-use terms are not published on this site, so ask sales on WhatsApp about them before building a heavy workload on the plan.
How many parallel connections can I open?
Concurrency limits are not published for any rotating plan. Start with a few dozen connections, watch for timeouts, and ask sales on WhatsApp whether a per-plan limit applies before you scale. On mobile plans the listed speed range is the practical ceiling, and extra connections mostly add congestion.
Will I ever get the same IP twice?
Yes, it can happen. Pools are finite, and nothing on this site promises that every exit will be unique. If your job must not reuse an address, keep a set of recently seen exits in your own client and retry on a new connection when you see a repeat.
Is the 5 GB pack enough to evaluate the service?
For a rotation test, yes: a three-minute probe loop uses about a megabyte (illustrative). For your own target, measure the average page size first; at 1 MB per page (illustrative), 5 GB is roughly 5,000 page loads. The pack is a one-time purchase of 540 TRY.