# ISP proxies

ISP proxies are **static residential IPs** sourced from ISP-owned subnets — they look residential to target sites but are hosted on premium datacenter infrastructure, so they're fast like datacenter and trusted like residential.

Unlike Residential and Mobile, ISP proxies are **not** delivered through a gateway. After purchase, you get a list of static IPs that you address directly.

## At a glance

|                    |                                                                                  |
| ------------------ | -------------------------------------------------------------------------------- |
| **Delivery model** | Per-IP list, `ip:port:user:pass`                                                 |
| **Billing**        | Per IP, per month                                                                |
| **Pool size**      | The IPs you purchased — fixed, dedicated to your account                         |
| **IP stability**   | Permanent — same IP across reboots, weeks, months                                |
| **Geo targeting**  | Country (and city in select markets) — **chosen at order time, not per request** |
| **Rotation**       | Client-side — you pick the next IP from your list                                |
| **Speed**          | High (1 Gbps+ per IP)                                                            |
| **Protocols**      | HTTP, HTTPS, SOCKS5                                                              |
| **Authentication** | User+password (per-IP credentials) or IP whitelist                               |
| **KYC required**   | Yes                                                                              |

## Credential format

Each IP in your list is delivered in the standard four-tuple:

```
ip:port:user:pass
```

Example:

```
198.51.100.42:8000:helo_s1a2b3c4d5e:PASSWORD
198.51.100.43:8000:helo_s1a2b3c4d5e:PASSWORD
198.51.100.44:8000:helo_s1a2b3c4d5e:PASSWORD
```

Same user/password across the whole batch you ordered — the IP+port pair is what distinguishes them. Full reference: [Proxy list format](/products/overview-2/proxy-list-format.md).

> The `helo_` prefix in the username is **not** the [gateway grammar](/getting-started/username-format.md) — ISP usernames carry no `-type-` / `-region-` segments. They are just user identifiers.

## When to use ISP

* **Account-bound workflows** — login flows where the site binds anti-bot signals to IP for hours/days
* **Sneaker / drop / ticket purchases** — speed + residential reputation
* **Long-running monitors** — checkers that must stay on the same IP for stability
* **High-bandwidth scraping** where residential per-GB billing gets expensive
* **Geo-locked services** where IP and city must remain consistent

If you need to rotate IPs aggressively per request, residential is a better fit. ISP shines when stability is the requirement.

## Five-second example

```bash
curl -x http://helo_s1a2b3c4d5e:PASSWORD@198.51.100.42:8000 \
     https://ipv4.icanhazip.com
```

(Substitute one of the IPs from your list.)

## On this page

* [Quick start](/products/overview-2/quick-start.md) — order, download list, first request
* [Proxy list format](/products/overview-2/proxy-list-format.md) — the four-tuple in detail
* [Authentication](/products/overview-2/authentication.md) — password vs IP whitelist
* [Locations](/products/overview-2/locations.md) — country and city coverage at order time
* [Protocols](/products/overview-2/protocols.md) — HTTP / HTTPS / SOCKS5
* [Client-side rotation](/products/overview-2/rotation.md) — patterns for picking the next IP
* [IP management](/products/overview-2/ip-management.md) — replace dead IPs, refresh batches
* [Error definitions](/products/overview-2/error-definitions.md) — what each status code means
* [Statistics](/products/overview-2/statistics.md) — per-IP usage and the API


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helodata.com/products/overview-2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.