> ## Documentation Index
> Fetch the complete documentation index at: https://developers.flameproxies.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Residential Proxies

> Full reference for FlameProxies residential proxies. Covers how routing works, rotating and sticky sessions, geo-targeting, pools, modes, every username parameter, and limits.

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, with targeting available down to city level. See [Locations](/proxies/locations) for every country and city.

## At a glance

| | |
| - | - |
| Pool size | 84M+ IPs |
| Price | \$0.50/GB for 1–999 GB, \$0.45/GB from 1,000 GB |
| Success rate | 99.9% |
| Gateway | `proxy.flameproxies.com` — port `8989` for HTTP, port `1080` for SOCKS5 |
| Package parameter | `package-standard` |
| Site restrictions | None. No sites or ports are blocked on our side. |
| Usage limits | None on throughput, requests per second or minute, threads, or concurrent connections |
| Bandwidth expiry | Never |

## 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, city, 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.

```bash theme={null}
curl -x proxy.flameproxies.com:8989 -U "USERNAME-package-standard-country-us:PASSWORD" https://ipinfo.io/json
```

Each time you run this, you'll get a different IP.

<Tip>
  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.
</Tip>

### Sticky sessions (held IP)

When you include `session-<id>-time-<minutes>`, the gateway holds the same IP for every request with that session ID, for up to the number of minutes you set.

```bash theme={null}
curl -x proxy.flameproxies.com:8989 -U "USERNAME-package-standard-country-us-session-a1b2-time-30:PASSWORD" https://ipinfo.io/json
```

Run this several times and you'll see the same IP.

**Session rules:**

* `session` and `time` are used together: `session-<id>-time-<minutes>`.
* You choose the session ID. Use letters and digits, like `a1b2`. Don't use hyphens — they separate parameters.
* `time` is the session length in 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 and city. These parameters limit which IPs are eligible for your requests.

| Parameter | Description | Format | Example |
| - | - | - | - |
| `country` | Country filter | ISO 3166-1 alpha-2 code, lowercase | `country-us`, `country-gb` |
| `city` | City within the country | City name, lowercase, no spaces | `city-newyorkcity` |

Use `city` together with `country`. For example, to target New York:

```bash theme={null}
curl -x proxy.flameproxies.com:8989 -U "USERNAME-package-standard-country-us-city-newyorkcity:PASSWORD" https://ipinfo.io/json
```

<Warning>
  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.
</Warning>

## Pools

The residential network is split into sub-pools with different performance characteristics. By default, the gateway draws from the whole network.

| Parameter | Description |
| - | - |
| *(none)* | Use the whole network. This is the default. |
| `pool-1` | Use only sub-pool 1. |
| `pool-2` | Use only sub-pool 2. |

If a target performs poorly, try each pool and compare success rates and speed.

```bash theme={null}
curl -x proxy.flameproxies.com:8989 -U "USERNAME-package-standard-country-us-pool-2:PASSWORD" https://ipinfo.io/json
```

## Modes

Modes change how the gateway handles your connection. You can combine them.

| Parameter | Description |
| - | - |
| `mode-fast` | Route through the peer with the lowest latency available. Fast mode doesn't cost extra bandwidth. |
| `mode-udp` | Enable UDP traffic. UDP is carried over SOCKS5, so connect on port `1080` with a client that supports SOCKS5 UDP. |

**Example: fast mode in the United States:**

```bash theme={null}
curl -x proxy.flameproxies.com:8989 -U "USERNAME-package-standard-country-us-mode-fast:PASSWORD" https://ipinfo.io/json
```

## Full parameter reference

Here's every parameter available for residential proxies:

| Parameter | Description | Values | Default | Required |
| - | - | - | - | - |
| `package` | Product | `standard` | — | Yes |
| `country` | Country filter | ISO 3166-1 alpha-2 code, lowercase | Any country | No |
| `city` | City filter | City name, lowercase, no spaces | Any city | No (needs `country`) |
| `pool` | Sub-pool | `1`, `2` | Whole network | No |
| `mode` | Connection mode | `fast`, `udp` (you can use both) | Off | No |
| `session` | Sticky session ID | Letters and digits | None (rotating) | No |
| `time` | Session length | Minutes | — | Yes, with `session` |

**Username format:**

```text theme={null}
<USERNAME>-package-standard[-country-<cc>][-city-<city>][-pool-1|2][-mode-fast][-mode-udp][-session-<id>-time-<minutes>]
```

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:**

```text theme={null}
proxy.flameproxies.com:8989:<USERNAME>-package-standard-country-us:<PASSWORD>
```

**Sticky session in New York for 30 minutes:**

```text theme={null}
proxy.flameproxies.com:8989:<USERNAME>-package-standard-country-us-city-newyorkcity-session-a1b2-time-30:<PASSWORD>
```

**Germany, sub-pool 2, fast mode:**

```text theme={null}
proxy.flameproxies.com:8989:<USERNAME>-package-standard-country-de-pool-2-mode-fast:<PASSWORD>
```

**SOCKS5 with UDP, as a URL:**

```text theme={null}
socks5://<USERNAME>-package-standard-country-us-mode-udp:<PASSWORD>@proxy.flameproxies.com:1080
```

## Limits

| Constraint | Value |
| - | - |
| Throughput | Unlimited |
| Requests per second or minute | Unlimited |
| Threads and concurrent connections | Unlimited |
| Blocked sites | None |
| Blocked ports | None |
| Bandwidth expiry | Never |

## Next steps

<CardGroup cols={2}>
  <Card title="Premium residential proxies" icon="shield-check" href="/proxies/premium-residential">
    Clean, high-trust IPs for strict anti-bot targets.
  </Card>

  <Card title="Locations" icon="globe" href="/proxies/locations">
    Every country and city you can target.
  </Card>

  <Card title="Authentication" icon="key" href="/getting-started/authentication">
    Credentials, protocols, and output formats.
  </Card>

  <Card title="Python examples" icon="python" href="/examples/python">
    Working Python code for residential proxies.
  </Card>
</CardGroup>