Residential proxies that connect through household IPs in the country and city you choose
Residential proxies route your traffic through IPs that internet providers give to homes, so sites see an ordinary visitor. You pay for the traffic you use, from $0.80 per GB, and either rotate the IP on every request or keep the same one.
Starting price
$0.80per GB
- 60 countries and 175 cities
- Rotate per request or keep an IP up to 120 min
- HTTP and SOCKS5
All three products draw from the same balance.
How does a residential proxy work?
A residential proxy sends your request to the target site through an IP that an internet provider assigned to a regular household. The site treats the connection as an ordinary person browsing from home, not as a server.
The flow has three steps. Your program sends the request to the gateway, a household IP that matches the conditions in your username (country, city, session) is picked, and the response from the site comes back to you along the same path.
YourProxy is a proxy service for residential, static residential and datacenter proxies that all run on one token and one balance. Pick a country and city to connect through an IP in that area.
Household IPs are easy for sites to accept as normal visits, so you get the same page a real visitor sees, even on sites that often show checks or change local results for server IPs. The proxy setup guide walks through the first connection step by step.
How is residential proxy pricing per GB calculated?
Residential proxies are charged by the traffic you actually send and receive, from $0.80 per GB. The basis is data volume, not the number of IPs or requests, so the cost follows the size of your job.
Traffic includes both the requests you send and the responses you receive. Besides the page HTML, every file a browser loads counts toward your GB: images, fonts, scripts and video segments. That is why opening a page in a browser uses far more data than code that fetches only the HTML.
- If you only need text and numbers, block image, font and video requests.
- Use plain HTTP requests that fetch only HTML or JSON where you can.
- Store pages you already have so they are not downloaded again.
- In headless browsers, use request interception to drop ads and tracking files.
To buy residential proxies, sign up to get your token and top up your balance from $20; you can start right away. Top-up bonuses and the per GB price are on the proxy pricing page.
What is the difference between rotating residential proxies and sticky sessions?
A rotating residential proxy uses a new IP for every request, while a sticky session keeps the same IP for up to 120 minutes. Add a session name to the username for a sticky session; leave it out and the IP rotates.
| Item | Rotate per request | Sticky session |
|---|---|---|
| When the IP changes | On every request | Kept up to 120 minutes for the same session name |
| Example username | user-country-us | user-country-us-session-shop1 |
| Best for | Bulk collection, search results, price comparison | Navigation after login, carts, multi step forms |
| Benefit | Requests spread evenly across many IPs | One flow continues as the same visitor |
You choose session names freely with letters and digits. Give different names such as shop1 and shop2 to hold several different IPs at the same time. If a job needs the same IP for a whole month, static residential proxies fit better.
How do I target a country and city with residential proxies?
With residential proxies you set the location by adding country-code and city-name to the username. You can currently choose from 60 countries and 175 cities.
The country code is two lowercase letters (jp for Japan, us for the United States). Write the city name in lowercase and replace spaces with underscores (new_york for New York). Leave the city out to connect through any IP in that country.
user-country-jp
user-country-us-city-new_york
user-country-us-city-new_york-session-cart7
user-type-mobile-country-gbIf you need a mobile carrier IP, add type-mobile to the username. The mobile option is available in 56 countries, which suits work where a phone connection is the reference, such as checking mobile app screens or mobile ad delivery.
The cities you can pick in each country are on the proxy country list.
What are residential proxies used for?
Residential proxies are used for jobs that need the exact page real visitors see in each area. They are most useful for collecting prices, search results, ads and product details from public web pages by country and city.
- Web scraping: collect public product, article and listing pages at scale.
- Price monitoring: check prices and stock that differ by country on a set schedule.
- SERP and SEO rank tracking: see your site and keyword positions in local search results.
- Ad verification: confirm local ads appear correctly and link to the right landing page.
- E-commerce: compare product ranges, shipping notes and discount text on foreign stores.
- Market research: gather public information such as local service pages and plans.
- AI training data: build datasets from text and tables on public web pages.
You can mix both modes in one job. Rotate on every request for search result lists, and add a session name to keep the same IP while you check a detail page across several steps. For Korean local pages, see the cities on the South Korea proxy page.
How do I connect to residential proxies?
Residential proxies connect as soon as you enter your username and account token with the single gateway gate.proxyour.com:7000. Both HTTP and SOCKS5 are supported, and there is no software to install.
The password field takes the account token you received at sign up. In the dashboard connection builder, pick a country, city and session and it creates the host:port:username:password format, an http address, a socks5 address and a curl test command.
curl -x http://user-country-us-city-new_york:YOUR_TOKEN@gate.proxyour.com:7000 https://ipinfo.io/json
curl -x socks5://user-country-jp:YOUR_TOKEN@gate.proxyour.com:7000 https://ipinfo.io/jsonWhen the country and city in the response match what you set, the connection is ready. The same values work in any tool that accepts an HTTP or SOCKS5 proxy, including Python requests, Node.js, Puppeteer, Playwright, Selenium, Scrapy, Postman, n8n, PHP, Go and Chrome. Examples for each tool are in the proxy setup guide.
How many GB of residential proxy traffic do I need?
Estimate the GB you need by multiplying the size of one page by the number of requests. The table below shows rough estimates based on typical sizes; real sizes vary a lot with how the site is built and which files you load.
| Example job | Size per page (typical estimate) | Requests | Usage (rough) |
|---|---|---|---|
| Product pages, HTML only | About 100KB | 10,000 | About 1GB |
| Price checks returned as JSON | About 20KB | 50,000 | About 1GB |
| Search result page HTML | About 200KB | 5,000 | About 1GB |
| Browser pages with images blocked | About 500KB | 2,000 | About 1GB |
| Store pages including images | About 2MB | 1,000 | About 2GB |
You get the exact figure by running a small batch first. Send about 100 requests, check the usage history in the dashboard to see the real size per page, and use that number to calculate the full job. Choose a top-up amount and bonus on the proxy pricing page.
How do I use residential proxies safely and lawfully?
Use residential proxies for public web data and lawful purposes, and follow the target site terms and the laws of each country. Keeping to this standard lets you run the same job reliably for a long time.
- Choose pages anyone can view as your collection target.
- Space out requests and adjust concurrency so sites are not overloaded.
- Check robots.txt and any data collection policy the site publishes.
- If collected data contains personal information, handle or delete it as the law requires.
- Define the purpose and retention period and store only what you need.
Your account token is both your login and your proxy password. The server stores only a hash of the token and its last 4 characters, so copy it or download it as a .txt file and keep it somewhere safe. Usage rules are set out in the terms of service.
Should I buy residential, static residential or datacenter proxies?
Residential proxies suit collection and local checks where the IP can change often, static residential proxies suit account work that needs one IP for a long time, and datacenter proxies suit fast, low cost bulk requests. All three run on the same token and balance, so you pick per job.
| Type | Billing basis | Start price | Best for |
|---|---|---|---|
| Residential | GB of traffic used | From $0.80 per GB | Scraping, price monitoring, SEO rank tracking |
| Static residential | Per IP (kept for a month) | From $3.00 per IP | Account management, logins, IP allowlists |
| Datacenter | Per IP | From $1.20 per IP | Bulk requests on lightly protected sites, monitoring |
If you are unsure, test one job on residential proxies first, then move sites with little blocking to datacenter IPs and account based work to static residential IPs. If you need the same household IP for a month, look at static residential proxies.
If speed and price come first, datacenter proxies are a good fit.
Inscrivez-vous avec un jeton et commencez dès $20.
Commencer