Skip to main content
Residential proxies route your traffic through real home internet connections. The IPs belong to genuine ISP subscribers, which makes them difficult for websites to detect and block. The FlameProxies residential pool includes over 84 million IPs. You can target a region, a country, a city, a network operator by ASN, or a device operating system. See Locations for every country and city.

​
At a glance

​
How residential routing works

When you send a request through FlameProxies, the gateway selects an IP from the residential pool that matches your parameters (country or region, city, ASN, OS, pool, and mode). Your request is sent through that IP to the target website, and the response comes back to you. The target website sees the residential IP, not yours. Because these IPs are assigned by real ISPs to real households, most anti-bot systems treat them as legitimate traffic. You control which IPs are eligible with location and pool parameters, and how long you keep the same IP with session parameters.

​
Session types

There are two ways to use residential proxies: rotating (new IP every request) and sticky sessions (the same IP across multiple requests).

​
Rotating (no session)

When you don’t include a session parameter, every request gets a new IP. This is the simplest mode, and it works well for high-volume scraping where you don’t need IP continuity.
Each time you run this, you’ll get a different IP.
An HTTPS request travels through a tunnel that’s opened once per connection, so every request on that connection uses the same IP. If your HTTP client reuses connections (keep-alive), open a new connection for each request when you need a new IP every time.

​
Sticky sessions (held IP)

When you include a session parameter, the gateway holds the same IP for every request with that session ID. Add time-<minutes> to cap how long it holds that IP.
Run this several times and you’ll see the same IP. Session rules:
  • You choose the session ID. Use letters and digits, like a1b2. Don’t use hyphens — they separate parameters.
  • time is optional. Add it to set how many minutes the session holds its IP: session-<id>-time-<minutes>.
  • To get a new IP before the time is up, use a new session ID.
  • To run several sticky sessions in parallel, give each one its own session ID.

​
Geo-targeting

You can target residential IPs by country, by region, or down to a city. These parameters limit which IPs are eligible for your requests. Use city together with country. Target either a country or a region, not both. For example, to target New York:
The more specific your targeting, the smaller the eligible pool. If you target a small city, there may be fewer available IPs, which can affect speed and availability. Start broad and narrow down as needed.

​
Region targeting

A region exits from a group of countries instead of one country. It’s a good middle ground when any country in an area works, and it leaves a much larger pool than a single country. Each region is weighted toward its largest markets, so most traffic exits from the first few countries listed below.
Germany, United Kingdom, France, Italy, Spain, Netherlands, Poland, Sweden, Belgium, Austria, Switzerland, Portugal, Ireland, Denmark, Finland, Norway, Czech Republic, Romania, Greece, Hungary, Slovakia, Bulgaria, Croatia, Slovenia, Lithuania, Latvia, Estonia, Luxembourg, Cyprus, Malta.
United States, Canada, Mexico.
United States, United Kingdom, Germany, Canada, France, Australia, Netherlands, Switzerland, Sweden, Ireland, Norway, Denmark, Belgium, Austria, New Zealand.
Japan, South Korea, India, Singapore, Indonesia, Thailand, Vietnam, Philippines, Malaysia, Hong Kong, Taiwan, Pakistan, Bangladesh, China, Sri Lanka, Nepal, Cambodia, Macau, Mongolia, Laos, Brunei.
Brazil, Mexico, Argentina, Colombia, Chile, Peru, Ecuador, Venezuela, Dominican Republic, Guatemala, Uruguay, Paraguay, Bolivia, Costa Rica, Panama, Honduras, El Salvador, Nicaragua, Puerto Rico.
Add a session to make it sticky. Every request then exits from the same country, on the same IP:

​
ASN targeting

Target the IPs of one network operator with its autonomous system number.
Check the org field in the response to confirm which network the IP belongs to. Add a session to hold one IP across requests:

​
OS targeting

Target IPs whose device runs a particular operating system.
OS targeting combines with country, region, and sessions:
Region, ASN, and OS targeting are available on residential proxies (package-standard) only. Premium residential supports country and city targeting.

​
Pools

The residential network is split into sub-pools with different performance characteristics. By default, the gateway draws from the whole network. If a target performs poorly, try each pool and compare success rates and speed.

​
Modes

Modes change how the gateway handles your connection. You can combine them. Example: fast mode in the United States:

​
Full parameter reference

Here’s every parameter available for residential proxies: Username format:
Parameters are separated by hyphens. Write them in the order shown above, which is the order the dashboard generates.

​
Example configurations

Basic rotating proxy, United States:
Sticky session in New York for 30 minutes:
Germany, sub-pool 2, fast mode:
Sticky session across Europe, same country and IP on every request:
One network operator, by ASN:
Windows devices in the United States:
SOCKS5 with UDP, as a URL:

​
Limits

​
Next steps

Premium residential proxies

Clean, high-trust IPs for strict anti-bot targets.

Locations

Every country and city you can target.

Authentication

Credentials, protocols, and output formats.

Python examples

Working Python code for residential proxies.