ISP Proxies for Automation and Residential Proxies for Automation: Two More Inputs for the Pipeline

A pipeline does not care what a proxy is called; it cares about the shape of the input. NeonProxies lines give it a single endpoint and a rotation call. ISP proxies for automation give it a block of fixed IPv4 addresses that will still be the same addresses next month, which is what a whitelist, a long-lived session store or a scheduled monitor wants. Residential proxies for automation give it a generated list of host, port, username and password lines, one per exit, drawn from real homes in 190+ countries and metered by the GB, which is what a fan-out crawler wants. Both are now sold from the same dashboard and the same balance as the mobile lines, and the rest of this page is written for the person who will wire them in: the formats, the limits, the prices, the session rules and the failure modes worth coding around.

Static ISP addresses: fixed inputs from $2.10 per IP per month

Each static ISP proxy is one IPv4 registered to a real network and served from a rack in Virginia. It does not rotate, which for automation is the feature rather than the limitation: a whitelist entry, a cookie jar or a monitor keyed on exit address keeps working for the whole term. Orders are blocks of ten or more for one, three, six or twelve months, with one login type for the block.

• Term: 1, 3, 6 or 12 months
• Login: username and password / IP whitelist / SOCKS5
• One login per order
• Order size: 10 IPs and up

Buy static ISP proxies

Residential data: generated lists at $2 per GB

Residential data is bought by the GB and turned into proxy lists on demand. Each list is scoped to a country and optionally a state, city or ASN, set to rotate per request or hold an address for up to 30 minutes, and emitted as plain host:port:username:password lines your loader can split on colons. A shared 4G and 5G mobile pool sits beside it with the same list format and the same session rules.

Buy residential data Dedicated mobile lines

The shape of each input

A static ISP order resolves to N fixed addresses, N being ten or more, all sharing one authentication method. Treat it as a static array: load it once, round-robin or pin as the job dictates, and expect it not to change until the term ends. If you authenticate by IP whitelist, your workers' own addresses are the credential and the proxy lines carry no secret at all, which is convenient for containers that should not hold passwords. Username and password or SOCKS5 are the alternatives, and switching the method regenerates credentials for the entire block, so treat a switch as a deploy.

A residential order resolves to a data balance, and lists are derived from it. Generate a list with the parameters a run needs, count of lines included, and feed it to the worker pool; generate another list with different parameters for the next run. Nothing is consumed by generating. Only bytes through the proxies are metered, so an idle list is free and a list that was wrong costs nothing to throw away.

The mobile pool resolves the same way as residential, with targeting limited to country, state and city, no ASN, and a price of $10 per GB on shared 4G and 5G addresses. It is a pool input, not a line: the address a sticky session holds for 30 minutes is shared with other users, which is fine for a verification sweep and wrong for an account that needs one identity, where a NeonProxies line belongs.

Sticky versus rotating, as a worker sees it

A rotating list sends every request from a fresh home address. For stateless fetches, parsers and checks that is ideal: no session to carry, no address to get tired. A sticky list holds one address for up to 30 minutes, which is the mode for anything with a login, a cart, a multi-step form or a token bound to the client address. Decide per list, not per order; the same GB balance serves both.

Design around the 30-minute ceiling. A sticky worker that needs a longer session should expect the address to change at the boundary and either re-authenticate or finish within the window. If the job needs an address that holds for days rather than minutes, that is not a residential problem; it is a static ISP problem, or a dedicated NeonProxies line problem.

Targeting is a list parameter. Country is mandatory; state, city and ASN are optional narrowing, and narrower targets have fewer homes behind them, so a worker hammering one small city will see more repeats than one spread across a country. Spread the load across a few scopes when uniqueness matters.

Prices, as constants

Static ISP lines are priced per IP per month. AT&T Native is $4 per IP per month. AT&T Fresh, Comcast Native, Frontier Native and RCN Fresh in the United States, DTAG Fresh in the United Kingdom and Orange Fresh in France are each $2.40 per IP per month. T-Mobile Legacy is $2.10 per IP per month. Telus Fresh in Canada is listed but sold out as of this writing. Native means long-held on the carrier, Fresh means newer to the proxy market, Legacy means the budget row.

The minimum block is ten addresses for one month, so the smallest ISP order totals $21 on T-Mobile Legacy, $24 on a $2.40 line and $40 on AT&T Native. Terms are 1, 3, 6 or 12 months, paid at order time at the per-month rate. Residential data is $2 per GB with no tiers, and mobile pool data is $10 per GB with no tiers; a cost estimator can be one multiplication.

For contrast, a dedicated NeonProxies 4G line is $5 a day or $68 a month and a 5G line is $7 a day or $82 a month, each with unlimited data and a rotation endpoint. When a job's bytes per identity grow past a few GB a month, the line is the cheaper constant.

• ISP: $2.10 (T-Mobile Legacy), $2.40 (six lines), $4 (AT&T Native) per IP per month
• ISP block: 10 IPs minimum, terms 1 / 3 / 6 / 12 months, one login per block
• Residential: $2 per GB, target country + state / city / ASN, sticky up to 30 min
• Mobile pool: $10 per GB, target country + state / city, shared 4G and 5G

Lifecycle: order, renew, top up, tear down

Orders are placed on the Buy Proxy page of the NeonProxies dashboard, which has three tabs, Mobile, Residential and ISP, and they are paid from the account balance. The order appears on My Proxies immediately, and the Telegram bot exposes the same catalogue for anyone who would rather type than click. There is no approval step.

ISP orders have a term and an end. Auto-renew, when on, pays the next month from balance; when off, a reminder goes out three days before the end so a scheduler is not surprised by a dead block. Extending adds months at the price paid. Removing an ISP order early kills every address immediately and refunds nothing, so make the term match the job's expected lifetime.

Residential and mobile pool orders have no end. Top up manually, or set auto top-up and an amount, and the dashboard adds data whenever less than a tenth remains, which is the setting for anything that runs unattended. Remove a GB order within seven days and the unused GB are returned to balance; after seven days the data simply stays available.

Failure modes worth coding around

Credential rotation on the ISP block. If someone switches the login type from My Proxies, every address in the block gets new credentials at that moment and workers holding the old ones start failing authentication together. Keep the proxy config in one place and treat a login switch as a planned change.

Data exhaustion on a residential order. Without auto top-up, a crawler that runs out of GB stops mid-run. Either enable auto top-up or have the job check remaining data before a large batch.

Term expiry on an ISP block without auto-renew. The reminder arrives three days out; a job that reads the expiry date from the dashboard and alerts on it is safer than relying on an inbox.

Wrong tool for the identity. Pooled addresses, residential or mobile, are shared and change at the sticky boundary. An account that must look like one device for weeks does not belong on them; it belongs on a dedicated NeonProxies line with its own rotation endpoint.

Combining the three inputs

A common layout runs all three off one balance. Dedicated lines carry the accounts and anything that must present a steady mobile identity. A static ISP block carries the fixed-exit jobs: the whitelisted dashboards, the monitors, the hourly checks that should always come from the same place. Residential data carries the fan-out: the broad crawls, the geo checks, the verification sweeps that want a different home on every request. The mobile pool fills in when a sweep needs cellular exits across many cities for an hour.

Because the three share one account, one Buy Proxy page and one My Proxies list, there is nothing to reconcile across vendors and one place to read usage and expiry.

// faq: isp and residential proxies for automation