• Rotating IPs
  • Global coverage

Rotating residential proxies, billed by the gigabyte

Residential proxies route your traffic through a large pool of household connections. You pay for the data you use, rotate or hold an address as the job requires, and target the countries you need.

From
TRY 350 / month
Plans
6
Protocols
HTTPHTTPSSOCKS5

Why it matters

What Residential Proxy gives you

  • Pay for what you use

    Plans from 5 GB to 300 GB. Small tests stay cheap; larger jobs get a lower price per GB.

  • Country, state and city targeting

    The pool is listed with geo-targeting down to state and city level, as described by the provider.

  • Rotating or sticky sessions

    Switch IPs every request for scale, or hold the same IP for a session when a login must persist.

  • HTTP(S) and SOCKS5

    Both are listed for the residential pool, so most tools and libraries connect without adapters.

Plans

Residential Proxy plans

Pick a billing period, then press Buy. The order page opens for that exact plan.

5 GB

TRY350/ month

≈ TRY 70 per GB

Buy
  • 5 GB

    TRY350/ month

    ≈ TRY 70 per GB

  • 10 GB

    TRY650/ month

    ≈ TRY 65 per GB

  • 50 GB

    TRY2,500/ month

    ≈ TRY 50 per GB

  • 100 GB

    TRY3,500/ month

    ≈ TRY 35 per GB

  • 200 GB

    TRY7,000/ month

    ≈ TRY 35 per GB

  • 300 GB

    TRY9,000/ month

    ≈ TRY 30 per GB

Buy buttons open the live order page. Prices are in Turkish lira (TRY), excluding taxes.

Open the full pricing page

Compare

How it compares with other proxy types

TypeIP sourceRotationProtocolsBillingBest for
IPv4 Datacenter ProxyHosting / datacenter rangesStatic (rotate in your own tool)HTTPSOCKS5MonthlyHigh-volume work on tolerant targets
ISP ProxyISP-registered ranges, hosted on serversStaticHTTPSOCKS51, 3, 6 or 12 monthsStable identities and account work
Residential ProxyHousehold ISP connectionsRotating or sticky sessionsHTTPHTTPSSOCKS5Per GB, monthlyGeo-targeted, low-block-rate crawling
Mobile ProxyMobile carrier SIM (4G/LTE)Static, IP changed on demandHTTPSOCKS51, 3 or 6 monthsSocial, apps and high-trust accounts
Rotating ProxyMobile carriers and household ISPsAutomatic, from a poolHTTPHTTPSGB packs, daily/weekly/monthlyScale without IP lists
IPv6 ProxyIPv6 subnet (/64)Static; rotate across the packHTTPHTTPSMonthlyWide distribution on IPv6-ready targets
  • Residential ProxyHTTPHTTPSSOCKS5
    IP source
    Household ISP connections
    Rotation
    Rotating or sticky sessions
    Billing
    Per GB, monthly
    Best for
    Geo-targeted, low-block-rate crawling
  • IPv4 Datacenter ProxyHTTPSOCKS5
    IP source
    Hosting / datacenter ranges
    Rotation
    Static (rotate in your own tool)
    Billing
    Monthly
    Best for
    High-volume work on tolerant targets
    Explore
  • ISP ProxyHTTPSOCKS5
    IP source
    ISP-registered ranges, hosted on servers
    Rotation
    Static
    Billing
    1, 3, 6 or 12 months
    Best for
    Stable identities and account work
    Explore
  • Mobile ProxyHTTPSOCKS5
    IP source
    Mobile carrier SIM (4G/LTE)
    Rotation
    Static, IP changed on demand
    Billing
    1, 3 or 6 months
    Best for
    Social, apps and high-trust accounts
    Explore
  • Rotating ProxyHTTPHTTPS
    IP source
    Mobile carriers and household ISPs
    Rotation
    Automatic, from a pool
    Billing
    GB packs, daily/weekly/monthly
    Best for
    Scale without IP lists
    Explore
  • IPv6 ProxyHTTPHTTPS
    IP source
    IPv6 subnet (/64)
    Rotation
    Static; rotate across the pack
    Billing
    Monthly
    Best for
    Wide distribution on IPv6-ready targets
    Explore
01

How residential proxies work

A residential proxy exits through an IP address assigned to a real household by a consumer ISP. Websites generally treat these addresses as ordinary visitors, so requests are less likely to be challenged than traffic from datacenter ranges.

The pool is large and shared, which is why billing is by data transferred rather than by IP. Each request can leave from a different address, or you can ask for a sticky session so consecutive requests share one IP for a while.

02

Estimating how many gigabytes you need

Traffic is counted in both directions, so heavy pages (images, video, scripts) consume more than API calls. Measure a sample: fetch 100 typical pages through the proxy, note the transferred size, then multiply by your planned volume and add a safety margin.

Blocking images and media in your scraper can cut usage by an order of magnitude. If your estimate is far above 300 GB, or traffic is steady every day, compare the unlimited-traffic plans on the rotating proxy page.

Use cases

Where it fits best

  • Geo-specific data collection

    Read prices, search results and ads as they appear to visitors in different countries.

  • Ad and SERP verification

    Confirm how campaigns and rankings look from many locations without travelling or using a VPN.

  • Large-scale public-data crawling

    Distribute requests across a broad pool to stay within each site’s per-IP limits.

Setup

Set up Residential Proxy

  1. Estimate your data volume

    Test a sample of pages and choose a GB plan with some headroom.

  2. Order the plan

    Press Buy to open the order page for that plan and complete payment.

  3. Build your gateway string

    From the customer panel, copy the endpoint and credentials, adding country or session parameters as documented there.

  4. Test geo and rotation

    Request an IP-information endpoint twice and confirm that the country and rotation behave as expected.

In depth

The details that decide the outcome

Cost model: price per gigabyte across the six plans

Because traffic is metered, the plan list is really a price curve, and the table makes it visible. The unit price falls from 70 TRY per GB at 5 GB to 30 TRY at 300 GB, less than half. The 100 GB and 200 GB plans cost the same per gigabyte, so the larger one only makes sense when you truly need the volume. The last column shows that one bigger plan is almost always cheaper than stacking smaller ones to reach the same allowance; the only tie is 200 GB against two 100 GB plans. All prices are Turkish lira, excluding taxes.

Your need rarely matches a plan exactly, so also test combinations below each tier. If you need 30 GB, three 10 GB plans cost 1,950 TRY against 2,500 TRY for the 50 GB plan; the 50 GB plan only becomes cheaper above about 38 GB (2,500 divided by 65). Stacking means separate orders, so check how credentials and usage counters appear in your customer panel, and ask sales if you want one combined allowance. Also remember each plan carries a 30-day usage period, so buy for the month you will actually use.

Worked example (illustrative): you track 80,000 product pages a month. Unoptimized, each page loads about 1.2 MB with images and scripts, so the job needs roughly 96 GB, and the 100 GB plan at 3,500 TRY leaves almost no margin. If you fetch only the HTML, or the JSON endpoint the page itself calls, at about 0.25 MB per page, the job drops to about 20 GB, which three 10 GB plans (1,950 TRY) cover with a comfortable margin. The optimization saves 1,550 TRY a month.

PlanPrice (TRY)Per GB (TRY)Same allowance from smaller plans (TRY)
5 GB35070.00Not applicable
10 GB65065.00700 (2 x 5 GB)
50 GB2,50050.003,250 (5 x 10 GB)
100 GB3,50035.005,000 (2 x 50 GB)
200 GB7,00035.007,000 (2 x 100 GB)
300 GB9,00030.0010,500 (3 x 100 GB)

Session design: rotating, sticky and what each costs you

Rotation trades continuity for spread. In rotating mode each request may leave from a different household address, which keeps any single IP under a site’s per-IP limits and suits stateless work such as search pages, product listings and public APIs. In sticky mode consecutive requests share one address for a period, which you need whenever the site binds state to the IP: logins, carts, multi-step checkouts and paginated results with server-side cursors. The customer panel documents how to request each mode and a country; this page deliberately uses no invented parameter syntax.

Keep each unit of work shorter than the session that carries it. A flow of 40 requests at one request every 3 seconds takes two minutes (illustrative) and must finish before the address changes. The maximum sticky duration is not published on this site, so measure it: open a session, request an IP-echo URL once a minute for ten minutes and record when the address changes. Design long jobs as many short sessions, each with its own cookie jar, and discard the cookies when you discard the session, because a session cookie that suddenly arrives from a new IP is a pattern many sites treat as suspicious.

WorkloadSession modeWhy
Search pages, listings, public APIsRotatingSpreads load so no IP nears a per-IP limit
Log in, then act on the accountStickyThe site ties the login to one address
Cart or multi-step checkout inspectionStickyCart state follows the IP and the cookie together
Prices or ads checked from many countriesRotating, one country per requestEach check should look like a separate visitor
Paginated results with a server-side cursorSticky for the whole seriesThe cursor may be bound to the first address

If a step fails twice inside a sticky session, end the session and start a new one rather than retrying from the same address indefinitely.

Verifying country, rotation and exit quality before a large run

Run a small acceptance test before spending gigabytes. Send 20 requests through the gateway to an HTTPS IP-echo endpoint and log the address each one returns. In rotating mode you expect close to 20 distinct addresses; in sticky mode, one. Paste a few of them into the IP information tool: the registry (RDAP) record and reverse DNS should point to a consumer ISP or telecom operator rather than a hosting company, and the registry country should be consistent with what you requested. A test like this transfers well under a megabyte, so it costs almost nothing on a GB plan.

Country targeting is the provider’s statement, and availability can vary by state and city, so verify the exact level you depend on. Test at least 50 requests per target location and count how many land where you asked; a few misses can be geolocation database lag rather than a pool fault. Check the surrounding signals too: send an Accept-Language header typical for that country and compare your browser profile’s time zone with the user-agent checker output. A German exit paired with an English-only locale and a Tokyo time zone is a mismatch that sites can read.

Measure quality as well as reachability. Record, for every request, the exit country, time to first byte and outcome (success, block or timeout). Household connections vary with the line and the route, so expect a wider latency spread than on static plans, and set client timeouts generously, for example 30 to 60 seconds as an illustration, retrying on a fresh IP rather than the same one. For the United States, Germany, Japan or any other country outside Turkey, the residential pool is the only source on this site, so run the acceptance test in each country you depend on.

Spending fewer gigabytes: bandwidth discipline and the unlimited break-even

Most savings come from not downloading what you do not use. Request the JSON or XHR endpoint behind a page instead of the rendered page, send Accept-Encoding with gzip or br so text is compressed on the wire, use conditional requests (If-None-Match or If-Modified-Since) for pages that rarely change, and cache anything fetched within the last day. In a headless browser, block images, fonts, media and third-party scripts at the request level. Log bytes per request in your own code so you can compare your total with the usage counter in the customer panel.

Unlimited residential plans trade a meter for a clock: 5,000 TRY a day, 20,000 TRY a week or 75,000 TRY a month. Using the cheapest GB rate, 30 TRY per GB on the 300 GB plan, as the yardstick, the daily plan breaks even at about 167 GB in a day, the weekly plan at about 667 GB in a week and the monthly plan at about 2,500 GB in a month. Below those volumes GB plans are cheaper, so unlimited only pays off for sustained heavy collection or one very large burst. They are on the rotating proxy page; protocol details are not published.

Residential traffic passes through real households, so scale responsibly: obey robots.txt and site terms, throttle requests, and collect only data you are entitled to use. How the pool’s addresses are sourced and what consent underlies them is not described on this site; if your organization needs that documentation for compliance or procurement, ask sales on WhatsApp before ordering. A challenge or block page is a signal to slow down or seek authorized access, such as an API or data license, not an invitation to escalate. Never use residential IPs for fraud, spam or credential stuffing.

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
Full page loads with images, video and third-party scripts, headless browsers, uncompressed responses and silent retries all count toward the total in both directions.
Fix
Block heavy resource types, call the underlying JSON endpoint, enable compression, log bytes per request and cap retries per URL.

Glossary

Terms you will meet

Gateway endpoint
A single host and port you connect to; the provider routes each connection to an exit address from its pool. It is also called a backconnect proxy.
Rotating session
A mode in which successive requests may leave from different addresses, spreading load across the pool.
Sticky session
A mode in which consecutive requests keep the same exit address for a period, used for logins and multi-step flows.
Geo-targeting
Asking the gateway for exit addresses in a particular country, state or city. Coverage at city level should be verified before a large order.
Metered traffic
Billing by the amount of data transferred, in both directions, rather than by the number of IPs or by time.
Exit IP
The public address a target site sees as the source of your request, as opposed to your own address or the address of the proxy entry point.

FAQ

Residential Proxy — frequently asked questions

What does 195+ countries mean?

It is the provider’s stated coverage of the residential pool. Availability can vary by city, so confirm unusual locations with sales before a large order.

Does unused data roll over?

The plans are listed with a 30-day usage period. Check the order page for the exact rules of the plan you pick.

Rotating or sticky — which should I use?

Rotating for large-scale fetching; sticky when a login, cart or multi-step flow needs the same IP throughout.

Can I use SOCKS5?

SOCKS5 is listed for the residential pool. If your tool needs SOCKS5 specifically, confirm with sales when ordering.

Are there unlimited residential plans?

Yes — daily, weekly and monthly unlimited-traffic plans exist; they are on the rotating proxy page.

How long does a sticky session last?

The maximum duration is not published on this site, and the documentation in the customer panel governs it. Measure it yourself by polling an IP-echo URL once a minute through one session, and ask sales for the documented limit before building a long flow around it.

Are failed requests and protocol overhead counted as traffic?

Metering rules for failed requests, TLS handshakes and tunnel overhead are not published. Run a controlled test on the smallest plan: send a known volume, compare your own byte count with the panel counter, and use the difference as a safety factor.

Is the 300 GB plan better value than buying 100 GB three times?

On the listed prices, yes: 9,000 TRY for 300 GB is 30 TRY per GB, while three 100 GB plans cost 10,500 TRY. The 300 GB plan only helps if you will actually use the allowance within its 30-day usage period.

Which countries can I reach besides Turkey?

Outside Turkey, the United States, Germany, the United Kingdom, France, Canada, the Netherlands, Italy, Spain, Japan, India and Brazil are served only from the residential pool, using the provider’s country targeting. Static ISP, mobile and gaming IPs are Turkey-based only. For city, carrier or ASN requirements, ask sales.

How many parallel connections can I run on one plan?

A concurrency limit is not published for GB plans. Because you pay for data rather than for IPs, parallelism is bounded mainly by connection speed and by what each target tolerates, so scale in steps and ask sales if you plan hundreds of simultaneous threads.

Not sure which plan fits?

Describe your use case and target countries and we will recommend a product — or tell you honestly when another type suits you better.

FromTRY 350/ month

Buy now