Asia-Pacific residential proxies

What is a residential proxy?

A residential proxy routes each request through the IP of a real household broadband line, as issued by the local ISP. Websites see a normal household IP in the target country, not a data center IP. This matters in Asia-Pacific, because many local sites show different prices, stock or results to foreign and data center visitors.

In Japan, home lines run on networks such as NTT FLET'S Hikari, SoftBank Hikari and au Hikari. In India, home broadband includes JioFiber, Airtel Xstream Fiber and ACT Fibernet. In Indonesia, IndiHome and Biznet are common home providers. A residential IP from these markets looks like a local household visitor. For definitions of terms like ASN and sticky session, see the glossary.

How do AsiaProxies residential proxies work?

You connect to one gateway, and the gateway forwards each request through a residential IP in the country you choose. AsiaProxies, a no-KYC Asia-Pacific residential proxy provider, uses a single entry point for all countries: gw.asiaproxies.com.

• HTTP and HTTPS: port 7777.
• SOCKS5: port 7778.
• Authentication: username and password from your dashboard.
• Rotation: a new IP on each request, or the same IP for a sticky session up to 60 minutes.

You pay per GB of traffic. The price per GB does not depend on the country. Traffic never expires, so a pack can last as long as you need.

How do I target a country, city or sticky session?

You set the country, city and session inside the proxy username. The username template is:

USERNAME-country-{cc}-city-{city}-session-{id}-ttl-{minutes}

• {cc} is the two-letter country code, for example jp, kr, in, id or vn.
• {city} is the city name as listed in your dashboard. Leave out the city part to get any city in the country.
• {id} is any short string you choose. Requests with the same session ID keep the same IP.
• {minutes} is the session length. Sessions last up to 60 minutes.

Leave out the session and ttl parts to get a new IP on every request. Your dashboard builds the exact username for each option. The setup guide has more examples in Node.js, Playwright and Scrapy.

# Username template: USERNAME-country-{cc}-city-{city}-session-{id}-ttl-{minutes}
# Example below: Japan (jp), Tokyo, session a1b2c3, 30 minutes
curl -x "http://gw.asiaproxies.com:7777" \
  -U "USERNAME-country-jp-city-tokyo-session-a1b2c3-ttl-30:PASSWORD" \
  https://ipinfo.io/json

# Same request over SOCKS5
curl --socks5-hostname "gw.asiaproxies.com:7778" \
  -U "USERNAME-country-jp-city-tokyo-session-a1b2c3-ttl-30:PASSWORD" \
  https://ipinfo.io/json

import requests

TEMPLATE = "USERNAME-country-{cc}-city-{city}-session-{id}-ttl-{minutes}"
PASSWORD = "PASSWORD"

# Sticky Indonesian IP in Jakarta for 10 minutes
user = TEMPLATE.format(cc="id", city="jakarta", id="shop01", minutes=10)
proxy = f"http://{user}:{PASSWORD}@gw.asiaproxies.com:7777"
proxies = {"http": proxy, "https": proxy}

r = requests.get("https://ipinfo.io/json", proxies=proxies, timeout=30)
print(r.json()["country"], r.json()["city"])

Should I use rotating or sticky residential IPs?

Use rotating IPs for many independent page loads, and sticky sessions for multi-step tasks. The table shows common choices.

Which Asia-Pacific countries can I target?

You can target every country of East, South-East and South Asia and Oceania listed below, except Iran and North Korea. The most requested markets have their own pages: Japan, South Korea, India, Indonesia, Vietnam, the Philippines, Thailand, Singapore, Australia and Hong Kong.

What are residential proxies used for in Asia-Pacific?

Teams use residential IPs to collect public data and check local content as a local user sees it.

• E-commerce price monitoring: public prices and stock on Shopee, Lazada, Tokopedia, Rakuten, Coupang and Flipkart. See the price monitoring guide.
• Local SEO: rankings on Google, Naver in Korea and Yahoo! JAPAN.
• Ad verification: check that ads appear in the right country and link to the right page.
• Geo-testing: check prices, language and content in each market before launch.

All use must follow the acceptable use policy. Bank, government and payment-portal sites are blocked, and SMTP is blocked.