India proxies
India differs from its Asian neighbours in two ways, and both are in your favour. The pool here is large, so city targeting genuinely works rather than remaining a preference as it does in Singapore or Thailand. And language is not a trap: a large share of the Indian internet is in English, so the Accept-Language header does not spoil a collection the way it does in Japan, Korea or Thailand.
What we have in India
Prices are the same as in every other country we cover.
What Indian addresses get used for
Marketplace price monitoring
Flipkart, Amazon.in, Meesho, Myntra, Ajio, JioMart, Nykaa: stock and prices here depend on the delivery region more than they do in Europe.
Classifieds and second-hand
OLX India, Quikr, CarDekho and Cars24 for cars, 99acres and MagicBricks for property.
Local search and SEO
google.co.in and the local map pack: results diverge noticeably between cities, because the market is large and uneven.
Ad verification
Times of India, NDTV, Hindustan Times, Economic Times: campaigns bought for an Indian audience do not render for a foreign address.
What looks different from outside India
These serve an Indian visitor something other than what a foreign one sees, because of broadcast rights and local catalogues. We sell addresses rather than a way past detection.
Which type to take for an Indian job
Home connection addresses, billed per gigabyte. One of the largest pools in our catalogue.
Marketplaces, search results, regional differences
Consumer registration on datacenter hardware. Static and dedicated for the term.
Accounts, long sessions, anything that must not change address
Addresses in Indian datacenters, traffic unmetered, capacity inexpensive.
Volume collection where the target ignores address class
Cities people ask for here
Cities are set with the _city_ suffix, and India is the rare case where the pool is large enough for city targeting to work reliably rather than intermittently.
The setups people take here most often
- 01Residential with a cityStock and delivery in Indian retail depend on the region, and the city genuinely works here.
- 02Datacenter, MumbaiVolume collection: inexpensive capacity and the best connectivity in the country.
- 03Residential, country levelWhen regional differences are not needed and any Indian exit will do.
- 04Static ISPAccounts and long sessions: the address holds for the whole term.
Connection strings for India
The country code is IN, upper case. The city goes after it with _city_, hyphens instead of spaces, in the order country, city, session, lifetime.
Indian static addresses take no suffixes: the host is the IP from your dashboard, port 50100, SOCKS5 on 50101.
Indian exits, four ways
curl -x login_c_IN:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# Mumbai, held for fifteen minutes on session 42
curl -x login_c_IN_city_Mumbai_s_42_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# a second region in parallel, on its own session id
curl -x login_c_IN_city_Bangalore_s_43_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# an Indian static address: no suffixes
curl -x login:password@YOUR-IN-IP:50100 https://api.ipify.orgCity targeting genuinely works here
On most pages in this section the advice about cities is cautious: the pool is thin, the request fails, write a fallback. India is different, and it is worth using.
The country is enormous and so is its internet population, so the residential pool here is one of the largest in our catalogue. Mumbai, Delhi, Bangalore, Hyderabad, Chennai and Kolkata answer reliably rather than intermittently, and asking for a specific city does not turn into a lottery.
It is worth using because Indian retail really is regional: stock, delivery estimates and part of the offers depend on where you ask to deliver. Collecting from a single address gives you a slice of one region rather than a picture of the market.
The practical shape: several sticky sessions on different cities, one per region, with the city recorded in the data alongside the result. That multiplies traffic by the number of regions and adds no addresses at all.
Language is not the trap here that it is next door
A useful contrast if you are carrying over experience from Japan, Korea or Thailand.
In those countries an English version of a page is a separate thing, and receiving it instead of the local one means collecting the wrong data. In India English is widely used on the internet itself: a large share of commercial sites, publishers and marketplaces operate in English for the domestic audience, not only for foreigners.
The consequence is that en-IN, or even a plain en-US, does not create the contradiction that catches you in Tokyo or Seoul. Regional-language versions exist, but they are a supplement rather than the main layer.
That simplifies the setup by one problem, and the attention is better spent on the delivery region, which matters far more here than the language does.
What actually blocks you on Indian targets
The familiar split, and India sits closer to the friendly end than to the strict one.
The large marketplaces filter hosting ranges: expect a 403 from datacenter on catalogue pages and plan for residential.
Publishers, reference sites and classifieds serve datacenter addresses normally, and Indian datacenter capacity is inexpensive, so a large share of the work belongs there.
Streaming services check the country strictly and refuse outright, as in Japan.
Search results are reachable but rate limited per address: more addresses rather than a different type.
Which exits you get here, and how stable they are
The Indian pool in practical terms.
The main thing about it is size: it is large, so even dozens of parallel sticky sessions do not exhaust the useful part as quickly as in small countries. For volume jobs that is a noticeable advantage.
Line quality is uneven: fast in the large cities, slower away from them. On residential that occasionally shows up as spread in response times inside a single job, which is exactly why a thirty second timeout earns its keep here.
Mumbai is where submarine cables land and the country’s main connectivity sits, with Chennai second. A datacenter address in Mumbai gives the best routes both outward and domestically.
Choosing the type for an Indian target
The usual order, and here it ends at the first step more often than average.
- Start with datacenter in Mumbai. A large share of Indian targets do not look at address class, and the capacity is cheap.
- A 403 on the first request means hosting ranges are filtered. The large marketplaces usually land here and want residential.
- If you are measuring stock or delivery, take residential with a city rather than country level: it genuinely works here.
- A 429 after many requests is a per-address rate limit: more addresses, not a different type.
- Accounts belong on ISP: static, dedicated, Indian consumer registration.
What Indian sites check beyond the address
An Indian address opens the first gate, and after that things are simpler here than next door.
Language, as above, is a small problem: English works.
There is one timezone for the whole country, Asia/Kolkata, and it is offset by half an hour from the whole-hour values. A profile assembled out of habit from whole hours lands in the wrong zone, and this is the only country on our list where the mistake arises that way.
Then the usual: consent banners hide content, and a scraper that does not handle them captures an empty page under a successful status code.
What a month of Indian work costs
Three scenarios at our prices, so you have something to check a quote against.
- Price monitoring across Indian marketplaces, 60,000 listings a day with images blocked, roughly 90 KB per page. That is about 5.4 GB a day, around 162 GB a month: $162 on residential.
- Collecting six cities instead of one adds no addresses but multiplies the traffic by the number of regions. Decide in advance how many regions you actually need.
- If the targets are neutral, the same jobs on fifteen datacenter addresses cost $20.25 a month. In India that option works more often than in Europe.
The legal part, stated plainly
India has its own personal data protection legislation, separate from the European one and revised in recent years. Collecting data that identifies people in India is governed by it regardless of where your company sits or which address your traffic exits through.
This is general information rather than legal advice. Our terms require lawful use and we act on abuse reports. Where the answer carries commercial risk, ask a lawyer.
Verifying an Indian exit
Under a minute. Here it is the city that is worth confirming, because you will be using city targeting more than in other countries.
Three checks
# 1. is the exit Indian, and in which city
curl -s -x login_c_IN_city_Mumbai:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json
# 2. do two cities actually return different exits
curl -s -x login_c_IN_city_Mumbai_s_1:password@proxy.sotaproxy.com:10000 https://api.ipify.org; echo
curl -s -x login_c_IN_city_Bangalore_s_2:password@proxy.sotaproxy.com:10000 https://api.ipify.org; echo
# 3. does the sticky session hold
for i in 1 2 3; do
curl -s -x login_c_IN_s_42_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org; echo
doneQuestions people ask before buying Indian addresses
Is city targeting really reliable here?
Yes, and that is rare. The pool is large, the major cities answer consistently, and Indian retail genuinely is regional, so the city is a tool rather than a decoration.
Do I need to send an Indian language header?
Usually not. A large share of the Indian internet is in English for the domestic audience, so the language trap that catches you in Japan or Korea does not arise.
Which timezone should the profile use?
Asia/Kolkata. It is offset by half an hour from whole-hour values, and a profile built out of whole hours ends up in the wrong zone.
Do I need residential for Indian sites?
Less often than average. The large marketplaces filter hosting ranges, but publishers, classifieds and reference sites usually do not, and Indian datacenter is cheap.
Do Indian addresses cost more?
No. Prices are the same everywhere: residential from $1.00 per GB, datacenter from $1.15 per address per month, ISP from $1.90.
Why do response times vary so much?
Home line quality is uneven: fast in the large cities, slower away from them. Keep the client timeout at thirty seconds and do not shorten it.