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

# Premium Residential Proxies

> Full reference for FlameProxies premium residential proxies: a curated pool of clean, high-trust IPs for targets with strict anti-bot protection.

Premium residential proxies route your traffic through a curated pool of more than 15 million clean residential IPs. They're built for targets with strict anti-bot protection, where IP reputation decides whether a request gets through.

Premium residential uses the same gateway, ports, and parameters as [residential proxies](/proxies/residential). The only difference in your proxy line is `package-premium` instead of `package-standard`.

## At a glance

| | |
| - | - |
| Pool size | 15M+ clean IPs |
| Price | \$3/GB |
| Success rate | 99.9% |
| Gateway | `proxy.flameproxies.com` — port `8989` for HTTP, port `1080` for SOCKS5 |
| Package parameter | `package-premium` |
| Site restrictions | Payment providers and government websites are blocked |
| Usage limits | None on throughput, requests per second or minute, threads, or concurrent connections |
| Bandwidth expiry | Never |

## What makes premium IPs different

Most blocks and CAPTCHAs are triggered by IP reputation, not by what you actually do. Standard residential IPs come from a much larger, less filtered pool. Premium IPs are selected for their history:

* **Clean histories.** IPs haven't been flagged, recycled across thousands of users, or associated with abusive traffic.
* **No proxy-detection history.** Each IP is screened to make sure it has never been detected as a proxy by major fingerprinting databases.
* **Continuous monitoring.** We monitor IP reputation against third-party blacklists and our own detection signals. IPs that show signs of degraded trust are rotated out of the pool and replaced.

The result is IPs that pass trust checks on sites protected by services like Cloudflare, Akamai, and DataDome — checks that often trip up standard residential IPs.

## When to use premium

Switch a workload from residential to premium when you see:

* **Elevated CAPTCHA rates** on a target, even with realistic request pacing.
* **Frequent blocks** or inconsistent success across sessions.
* **High-stakes flows** — e-commerce checkouts, social platforms, and travel sites — where a failed request costs more than the difference in bandwidth price.

For everything else, [residential proxies](/proxies/residential) cost less and have no site restrictions.

<Warning>
  Premium residential proxies are blocked on payment providers and government websites. Use [residential proxies](/proxies/residential) for those targets.
</Warning>

## Connecting

### Rotating (no session)

Every request gets a new premium IP:

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

### Sticky sessions

Hold the same premium IP across requests for a number of minutes. This example keeps a UK IP for 20 minutes:

```text theme={null}
proxy.flameproxies.com:8989:<USERNAME>-package-premium-country-gb-session-c3d4-time-20:<PASSWORD>
```

```bash theme={null}
curl -x proxy.flameproxies.com:8989 -U "USERNAME-package-premium-country-gb-session-c3d4-time-20:PASSWORD" https://ipinfo.io/json
```

Session IDs follow the same rules as residential: letters and digits, no hyphens, and a new ID gets a new IP.

### SOCKS5

```bash theme={null}
curl --socks5-hostname proxy.flameproxies.com:1080 --proxy-user "USERNAME-package-premium-country-us:PASSWORD" https://ipinfo.io/json
```

## Full parameter reference

Premium residential supports the same parameters as residential:

| Parameter | Description | Values | Default | Required |
| - | - | - | - | - |
| `package` | Product | `premium` | — | 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-premium[-country-<cc>][-city-<city>][-pool-1|2][-mode-fast][-mode-udp][-session-<id>-time-<minutes>]
```

See [Residential proxies](/proxies/residential) for a detailed explanation of each parameter.

## Limits

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

## Next steps

<CardGroup cols={2}>
  <Card title="Residential proxies" icon="house-signal" href="/proxies/residential">
    The full parameter reference, and the lower-cost option for most targets.
  </Card>

  <Card title="CAPTCHA & block rates" icon="shield" href="/troubleshooting/captcha-block-rates">
    How to improve success rates on difficult targets.
  </Card>

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

  <Card title="Generate proxies with the API" icon="code" href="/api/proxies/generate">
    Create premium proxy lines programmatically.
  </Card>
</CardGroup>